I submit that "definitely" is the most commonly misspelled word here. Or perhaps "schedule" or "tomorrow."
Careful; at some point a post about the most-often misspelled words will cause new words to displace the very words the post was about, a kind of quantum effect.
If Google could infer why I am searching instead of just what I am searching, it would be able to do a much better job.
And, as with people, when it gets it wrong it's worse than if it was just a dumb but obedient tool. That's the problem I have with anything that presents itself as a mind-reader: when it doesn't read my mind, I have to read its mind to predict what it will do in response to my input.
In the end it makes things more complex. I'd rather have a tool whose response doesn't depend on what it thinks about me. It's the same with salesmen: don't get in my way when I know what I want to do.
"Slashdot Death Ray is made of tens of thousands of geeks, most mounted on platforms approximately one to two feet high, and approximately 18 inches on each edge. Each geek focuses HTTP requests to a single web server at a distance ranging from tens to thousands of miles away. A web site is kept visible at all times on the geeks' computers and serves as mounting point for the URL of Slashdot Death Ray targets. The whole system is mounted on a large rock sphere. The goal of this summary is to show the results of the targeted website when the Slashdot Death Ray is used."
"If you're innocent, you have nothing to worry about."
I'm not worried about possible crime I will commit against myself, it's crime that someone else will commit against me by misusing data the government has about me.
If you want someone to check your ID when you sign your card, please hand it to the cashier with your credit card.
Ignoring whatever security benefit this actually provides, I think these people want the cashier to ask for ID when it's not handed over, as in when someone other than the cardholder is trying to use it.
If I were running the credit card companies, I would hold the vendors responsible for any loss due to fraud that was a result of their NOT checking signatures and ID's. THAT would put a stop to that.
Or maybe put a stop to that credit card company, if another one runs the numbers and determines that it's cheaper to pay for uncaught fraud than require retailers to check signatures.
It could be worse, when companies like UPS started doing this, the quality and resolution was *terrible*. [...] The resulting signature was so funny, I kept it. (Before you flame me for posting my signature, look at the actual image).
If you squint your eyes just right you can make it out! Bad idea to post your signature, Mr.;,!.'',_!.
They used "Wood's Metal", which is a solder-like alloy of tin, lead, cadmium, and bismuth. All of which are toxic. Lead and cadmium cause heavy-metal poisoning, and the body won't clear either of them.
Well, now that they've made themselves unable to replicate, they better make machines to do so!
"A number of smart folks have speculated that Google might leverage its computational resources to create some kind of massive online application delivery platform. I'm so smart that my speculation that they are wrong is probably correct. Er but it's still just more speculation."
Some people find powers of 2 appealing -- imagine driving route 256 -- how cool would that be?
When I have to pick a somewhat arbitrary value for something in a program, I have trouble choosing something other than a power of two. It becomes a problem when the nearest powers of two are relatively far apart. I guess I have a superstition that powers of two will be more efficient or less-likely to cause problems.
Whatever makes 1111111111 interesting is probably the same thing that makes people think that the series of random bits 111111 is less random than 101001 or 011001 etc.
(by that time, we will all have at least 64-bit systems, but still a cause for concern, read the link)
The number of bits a CPU can natively operate on data has little relevance on the problems due to representing dates with too few bits. It all depends on the programming interface and storage format. If you use an outdated (hah) API on a 256-bit CPU, you'll still have a YnK problem.
So you conclude that IE is broken because it looks terrible in IE and good in Firefox? Don't assume that all HTML code is valid and standards-compliant, and that something looking good in Firefox is proof that it's compliant HTML and that what you see in Firefox is correct.
My hands always shake when I'm using p2p apps, out of fear of the RIAA finding me out. It's hard to trade the latest music and movies. Not any more! Take that, RIAA!
Correct; unsigned values can only be positive (good), but signed values can also be negative (bad). This is just an example of a negative signed Java applet.
Slashdot Mirror
I submit that "definitely" is the most commonly misspelled word here. Or perhaps "schedule" or "tomorrow."
Careful; at some point a post about the most-often misspelled words will cause new words to displace the very words the post was about, a kind of quantum effect.
Your dog is insecure. Shame on your parents for not teaching you best practices!
Unfortunately, there seems to be a back door which opens at least one port reliably: firehydrant.
check [ ] to just use a pair of tin cans with string between them (atoms may be compromised)
check [ ] to install self compiled open source VoiP software without backdoors.
check [ ] to compile source with compiler (note: compiler might insert backdoor)
check [ ] to compile source by hand
...pleanty of other mediums to play in.
Watch out, those mediums can bring back the dead too!
If Google could infer why I am searching instead of just what I am searching, it would be able to do a much better job.
And, as with people, when it gets it wrong it's worse than if it was just a dumb but obedient tool. That's the problem I have with anything that presents itself as a mind-reader: when it doesn't read my mind, I have to read its mind to predict what it will do in response to my input.
In the end it makes things more complex. I'd rather have a tool whose response doesn't depend on what it thinks about me. It's the same with salesmen: don't get in my way when I know what I want to do.
So you can enjoy the Blue Screen of Death!
Like duhhh, not a color screen! Problem solved.
Here's a related article I just submitted:
"Slashdot Death Ray is made of tens of thousands of geeks, most mounted on platforms approximately one to two feet high, and approximately 18 inches on each edge. Each geek focuses HTTP requests to a single web server at a distance ranging from tens to thousands of miles away. A web site is kept visible at all times on the geeks' computers and serves as mounting point for the URL of Slashdot Death Ray targets. The whole system is mounted on a large rock sphere. The goal of this summary is to show the results of the targeted website when the Slashdot Death Ray is used."
"If you're innocent, you have nothing to worry about."
I'm not worried about possible crime I will commit against myself, it's crime that someone else will commit against me by misusing data the government has about me.
If you want someone to check your ID when you sign your card, please hand it to the cashier with your credit card.
Ignoring whatever security benefit this actually provides, I think these people want the cashier to ask for ID when it's not handed over, as in when someone other than the cardholder is trying to use it.
If I were running the credit card companies, I would hold the vendors responsible for any loss due to fraud that was a result of their NOT checking signatures and ID's.
THAT would put a stop to that.
Or maybe put a stop to that credit card company, if another one runs the numbers and determines that it's cheaper to pay for uncaught fraud than require retailers to check signatures.
It could be worse, when companies like UPS started doing this, the quality and resolution was *terrible*. [...] The resulting signature was so funny, I kept it. (Before you flame me for posting my signature, look at the actual image).
If you squint your eyes just right you can make it out! Bad idea to post your signature, Mr. ;,!.'',_!.
They used "Wood's Metal", which is a solder-like alloy of tin, lead, cadmium, and bismuth. All of which are toxic. Lead and cadmium cause heavy-metal poisoning, and the body won't clear either of them.
Well, now that they've made themselves unable to replicate, they better make machines to do so!
Revised article summary:
"A number of smart folks have speculated that Google might leverage its computational resources to create some kind of massive online application delivery platform. I'm so smart that my speculation that they are wrong is probably correct. Er but it's still just more speculation."
[...] MS should have the standard Longhorn with fewer features, and come out market Longerhorn as the premium.
Oh great, then everyone will get SPAM selling herbal remedies that lengthen your MS Longhorn for less than Microsoft charges.
Some people find powers of 2 appealing -- imagine driving route 256 -- how cool would that be?
When I have to pick a somewhat arbitrary value for something in a program, I have trouble choosing something other than a power of two. It becomes a problem when the nearest powers of two are relatively far apart. I guess I have a superstition that powers of two will be more efficient or less-likely to cause problems.
Whatever makes 1111111111 interesting is probably the same thing that makes people think that the series of random bits 111111 is less random than 101001 or 011001 etc.
(by that time, we will all have at least 64-bit systems, but still a cause for concern, read the link)
The number of bits a CPU can natively operate on data has little relevance on the problems due to representing dates with too few bits. It all depends on the programming interface and storage format. If you use an outdated (hah) API on a 256-bit CPU, you'll still have a YnK problem.
They were at a loss to explain the comparatively low demand for digits 2, 3, 4, 5, 6, 7, 8, 9, and 0.
So you conclude that IE is broken because it looks terrible in IE and good in Firefox? Don't assume that all HTML code is valid and standards-compliant, and that something looking good in Firefox is proof that it's compliant HTML and that what you see in Firefox is correct.
And since the open source community won't patent their stuff, MS is free to steal the ideas that worked.
*cough*OpenOffice*cough
You mean Firefox is going to have these features removed??
My hands always shake when I'm using p2p apps, out of fear of the RIAA finding me out. It's hard to trade the latest music and movies. Not any more! Take that, RIAA!
What happens when you go to your bank's website and get redirected to an identical-looking website that steals your information?
Is making a bookmark of the correct URL too much to ask?
Hey man, I finally found you! Reply to me here on Slashdot rather than trying voicemail again.
Correct; unsigned values can only be positive (good), but signed values can also be negative (bad). This is just an example of a negative signed Java applet.