Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Dewhat? (Score 4, Funny) 150

When I was in the USAF I had great fun telling users that they could have a wireless keyboard & mouse just as soon as they found FIPS 140-2 compliant ones. I then told them that not only do none exist to our knowledge, but none are planned. The main problem being once you put serious encryption in there(as 140-2 requires), you're looking at a keyboard/mouse that are closer to smartphones than keyboards. IE a AA won't last a few months, you'll need to charge it like you do your smartphone. AES encryption also isn't intended for 8-16 bits at a time, so it's not really efficient there.

That's easy to solve. Since the keyboard and mouse are very likely near a PC, just run a charging cable to one of it's USB ports and never disconnect it. Then you can get rid of the battery completely. Problem solved. Then you've got a nice battery-less, always charged wireless keyboard and mouse. Tada!

Comment Re:Not unexpected. (Score 1) 141

It uses the EXACT same part (down to the model number), and we're wondering why Kawasaki hasn't done a recall on theirs.

Because often the specification isn't bad, but the manufacturing process had a defect that only affected a specific run or a batch. It is quite possible that even with the same part number that one batch sold was defective while another was not.

Usually, this can be attributed to production lines using materials to their absolute limit (stamps, presses, drill bits, etc) to try and maximize profit. Occasionally one goes just enough out of spec to slip by QA, but then is corrected in the next batch after the worn production parts are replaced.

Comment One solution (Score 2) 137

Well, from what I've seen, the content producers are about to feel a world of hurt. Having a son of my own, and watching what he and his friends do, one of the many things I've noticed about the up and coming next generation is that they don't watch TV AT ALL. Not a single minute. I guess the content producers will finally get what they deserve, but it will just take another 5-10 years before they feel the pain they have caused themselves.

Comment Re:Tempting (Score 1) 181

Well, it is mostly needed for three things:
1) Addressable memory in 32-bit browsers. The threading approach means all tabs must not take more than a total of 4GB of memory, and this is quickly becoming a problem.
2) One tab crashing them all. Yes, firefox crashes on me often enough that it is annoying. Yes, the tabs come back when you relaunch, but then I get bombarded with login requests to all the sites I have open that require logins to view.
3) There is something shared between the threads that the firefox team can't seem to rid themselves of. One tab can, and often does considerably slow down, or make other tabs stutter. So bad that watching HTML5 video in firefox is nearly useless except if you only have 1 tab open, and even then it is a worse experience than in IE or Chrome.

Comment Re:Laywer fight (Score 1) 357

So if someone who is paralyzed and didn't buy a wheelchair should also have the right to park their car in the movie theater since that's the only way they can get in there. I'm sorry you didn't buy a non-google glass pair of glasses, but that is your fault.

Comment WHy net neutrality doesn't work (Score 1) 243

You are totally correct here. ISPs should only be allowed to be content producers, or content distributors, IF they relinquish all their monopoly statuses with local municipalities. Comcast, Time Warner, etc should be taken to court under anti-monopoly laws in the US. As they are guaranteed monopolies and their behavior is definitely harming consumers and they are trying to leverage their monopoly in one sector to give them an unfair advantage in a different sector, this seems a rather simple case, but well... lobbying... money... corruption... self-serving politicians... yeah.

Slashdot Top Deals

Sentient plasmoids are a gas.

Working...