Forgot your password?

typodupeerror

Comment: Re:over the top but! (Score 1) 74

And the other side of that coin is finding it and reporting it. Then checking back x time later. Where they did nothing then say, why were you looking again?

How about:

1) To find out if the data was pulled down yet.
2) To be even nicer guys by waiting until the data WAS pulled down to run the story that would give tens of thousands of identity thieves a valuable present.

Comment: Re:Try to do something right (Score 2) 74

Or you know... people could start writing decent secure code to begin with... :)

Did you ever write a program? Did it work the first time, doing exactly what it was supposed/specified to do?

Took a lot of debugging and error correction, didn't it? Even if you are a programming expert.

Now write a program where "what it's supposed to do" includes "not get cracked and used by any malware, known or unknown, past or future".

Think you'll get THAT right the first time? Even if you are a security expert?

Comment: Re:Legislation? (Score 1) 3

by crankyspice (#43772183) Attached to: Accountability / bug submission for services providers?

My fear is that we're getting away from the "market forces" that used to work. Netflix couldn't care less if they lose me, the Windows Media Center folks with the same problem, or the thousands(?) of Apple TV users with the same error message who haven't dug as deep into troubleshooting. With 30 million subscribers, 2,500 of us is a rounding error.

Maybe I'm showing my age, but I remember when there were but a handful of Linux users (I've had a Linux shell account since '93), and we were perpetually in danger of being steamrolled by the Big Corporations who could change things on a whim (Winmodems... Microsoft's SMB protocol...) and shut us out.

This isn't quite that, but it's similar. (It's also 2:45 a.m. and I'm not sure I can express myself as coherently as I need to right now...)

After a bit of brainstorming / research, I put up this Google Doc draft, that more clearly outlines what I'm talking about...

Comment: Typos! ARRRRGH! (Score 1) 315

Correcting typos:

Spun out of Internal Revenue in 1886.
Shot and killed the son and sniped and killed the (nursing at the time) wife over a FIVE dollar tax matter, not a five hundred buck bill.

(ATF is also noted for throwing a pregnant woman against a wall - she later miscarried - and stomping a kitten to death just to drive home how powerless a raid target was to make them responsible for their actions. Shooting the family dogs at the start of a raid, for the raiders' convenience, is routine.)

Comment: Why not jackboots? ATF is also under treasury. (Score 2) 315

When will the IRS start issuing jack boots to all agents?

Why not jackboots? ATF and Secret Service are also part of Treasury.

ATF has been the classic "jackbooted thugs" for most of their existence - ever since they got spun out of Internal Revenue in . They're "the revenuers" that enforced alcohol taxes with machine guns even before they and the FBI burned down a church camp in Waco over a $200 tax bill and shot a man's son and wife on Ruby Ridge over a $500 claim, inspiring the original NRA "Jackbooted Thugs" ad.

Secret Service has a history of incarcerating people and holding them incommunicado if they think they might be possibly be a threat to a high government official. (I knew one '60s radical who BECAME a '60s radical, a nice Jewish girl who, when still underage, was playing spy/counterspy with a friend in Grosse Point using their new toy CB walkie-talkies, totally unaware that JFK was passing through the Detroit area on his way to speak at a university graduation ceremony 50 miles away. Scooped off the street, thrown in a cell overnight, no mention of why, no phone call, no notice to parents, ...) They also harassed someone who, during the Vietnam protests, wrote "Piss on JFK" on a postcard. Reason given: "If enough people pissed on him it would kill him."

Why should the IRS be left without appropriate footwear?

Comment: They're just getting a head start on Obamacare. (Score 3, Insightful) 315

I was expecting the CDC to pull this stunt, but the IRS?

They're just getting a head start on Obamacare - which they will be administering.

Ten million people's medical records? They now have a mandate to have EVERYBODY's.

Comment: Re:The reason that supercapacitors are not already (Score 1) 282

by Ungrounded Lightning (#43770193) Attached to: Charge Your Cellphone In 20 Seconds (Eventually)

In the vacuum tube era they'd get stacked up to tens of thousands of volts, and they went even higher for particle accelerators (which are a big fancy vacuum tube when you get right down to it).

There's no inherent limit to how many capacitors you can put in series.

Yes, the "balancing tricks" do cause a LOT of leakage. Series caps are more for storage times measured in seconds or fractions thereof than weeks.

Comment: Re:He's right (Score 1) 364

by networkBoy (#43761863) Attached to: Bloomberg To HS Grads: Be a Plumber

Actually I think that the first 2 years of high school should focus on things you will need to survive: money management, how financing works and why revolving credit is not a good thing; reading and writing.
The second 2 years should allow either continued academic *or* tradescraft. fo you go the tradescraft route you'll get two years focused on only the stuff you need for a particular field. Plumbing: math and geometry (drain slopes), chemistry (solvents and glues, interaction with metals), and of course hands on.
-nbr

Comment: Fans? (Score 0) 322

The second experiment added some Linux laptops that ping-flooded to generate lots of network activity. The second experiment showed a clear increase in plant "damage" /lack of development.

Were the laptops located so that their fans wouldn't be blowing hot air past the seeds, heating them and sucking the moisture out of them?

+ - Accountability / bug submission for services providers? 3

Submitted by crankyspice
crankyspice writes "Thinking on the topic of consumer frustration and our increasing reliance on tech. Currently brainstorming a solution to corporations providing IaaS/SaaS/PaaS type services with no way to bring technical issues to their developers' attention (customer support drones reading from scripts who don't even know what an RFC is — not the solution). (In the past, when your POTS line went out, Ma Bell rolled a truck; when your cable went out, Time Warner rolled a truck... What do you do when you've "cut the cord" and suddenly Hulu stops working with your WiFi-equipped Panasonic DVD player?)

Thinking something akin to a DMCA Registered Agent system, where if a tech company provides an email address that at least ties in to their bug tracking system, they get a safe harbor for interoperability liability or something... (At the moment, one-sided terms of service provisions mandate ~$10,000 arbitration, limit damages to what was spent on the service ($8/month?), and eliminate the ability to bring class action suits, so the service providers have basically immunized themselves from liability anyway; not sure how to handle that...)

As our world becomes increasingly complex and interconnected, accountability and reliability are becoming more and more critical. It's soon going to be essential that there be a mechanism where the providers of services can at least be made aware that their stuff is broken...

Two situations I've had recently highlighted this (and caused hair pulling); both ultimately minor in the grand scheme of things, but both point to harrowing futures:
  1. Sending a PDF to fax via email was failing from my iPad. TrustFax.com (an eFax service) just wasn't seeing the attachments. The script-reading customer service drones kept saying (once I got past the stock answers about how I had to send a message to @trustfax.com, etc., which I was obviously doing since their system was reporting back to me a specific issue — no attachments found) they didn't support Apple, didn't support the iPad, etc., but I knew it had to be a problem on their end, as I'd sent PDFs from Pages on my iPad before and they'd been picked up and sent successfully by that service. Turns out the issue was with a longer filename; Pages and/or Mail on the iPad uses RFC 2231 sect. 3 multi-line encoding for parameter values, and TrustFax's email-to-fax system evidently wasn't written to support that standard. A relatively simple fix, once / if the developers are aware of it, but how to get it to their attention?
  2. My AppleTV won't play Netflix. Just reports "Netflix is currently unavailable." Apple says it's a Netflix problem. Netflix, after swearing up and down it was because my Apple TV "couldn't connect to Netflix" (demonstrably not true) finally pointed the finger at Apple. Finally I ran 'tcpdump' on my DD-WRT router and fed the results into Wireshark to see what was going on: api.netflix.com (actually an Amazon AWS instance) is reporting "X-Neftlix-Error-Cause: Error from API Backend." Seems like a Netflix problem to me, but it could be that Netflix isn't properly handling bad input from the Apple-supplied application. Customer support drones on both sides are useless, so how do I get this into the hands of someone who can look at it, see what's broken, and put it in for a bug fix?

If you were going to design simple, effective legislation to address this lack of accountability / access to developers' attention, what would it look like? (From a consumer's perspective, and/or from the other side of the corporate firewall.) Is legislation the answer? Can corporations be shamed/spotlighted into voluntarily agreeing to some sort of industry-specified "best practices" when it comes to these issues?

I'm ready to agitate, but I don't want to go off half-cocked without considering, well, those aspects I haven't yet considered! Hence, I'm Asking Slashdot... :)"

I would much rather have men ask why I have no statue, than why I have one. -- Marcus Procius Cato

Working...