Pretending that "mother's maiden name" is a secret is phenomenally stupid in the first place.
If one more source of mothers' maiden names crops up, that's not the problem.
Incidentally, it's funny that this comes up in a discussion related to Iceland. Icelander don't have family names and women are not renamed when they marry.
I feel differently. To me, turning autorun on (err, I mean not turning it off) means that you give the disc permission to...well, autorun. That's it. So, ordinarily, whether something happens in response to you double clicking an executable on a cd or in response to you inserting a cd while autorun is enabled has no bearing on whether that something is allowed.
However, in the case of audio CD's (or things being marketed as such), something subtly different is going on. The thing that happens when you insert the CD under autorun is not the same thing that happens when you normally use audio CD's. What happens is unexpected. Therefore, you couldn't have authorised it to happen. The user's expectations matter.
In the real world, of course, we turn off autorun anyway, but I think it's needlessly submissive to say that anything that happens when we insert a CD under autorun happens with our permission.
You lack imagination. If you're going to fantasize about a spammer getting his comeuppance, picture his face covered in tattoos with the subject lines from his spam. Especially "ADD THREE INCHES TO YOUR PENIS!!!!!!!" right on the forehead.
Depending on what card you're using, you may need more than a soft boot to clear it.
A couple of times after a crash and a soft reboot, X has started, set the video mode, and for a moment before it paints the screen for the first time, I saw what was displayed before the crash (minus a few lines at the top of the screen, which were garbled).
This is with a GeForce 2 and nvidia drivers.
I wonder if anyone can come up with a use for that. A filesystem in video ram could survive a crash, but so would a filesystem on disk. Maybe some application that needs more speed could use this?
That's going to take 2^filename.length checks for file existance. Filesystems are smart enough not to have to read from disk every time, but what if it's an NFS/SMB mount? It isn't even possible to pipeline the network queries, since the app would wait to find out that letter.txt doesn't exist before checking for letter.txT.
But the real problem is this: You have letter.txt and Letter.txt. The user asks for Letter.TXT. Which file does the application choose?
A real case-preserving filesystem is needed to make sure letter.txt and Letter.txt don't exist at the same time.
That's one valid position to take, but I think another one makes more sense:
I should be able to buy the right to listen to music seperately from any physical medium. I think some of the friction between consumers and publishers comes from the fact that the current model just isn't intrinsically sensible. A 0 or 1 directly from a CD is the same as a 0 or 1 from CD via the net. It's illogical to assign some artificial distinction to bits based on their pedigree and people feel that doing so is wrong. It just doesn't make sense, and people get upset over that.
I acknowledge the publisher's right not to make sense, but I do think it hurts them.
Most of what you're seeing is not really hypocrisy at all. First of all, the anti-legislation posts (on DMCA etc.) and the pro-legislation posts (on spam etc.) are largely from separate groups of people.
Some people belong to both groups, but that's not necessarily hypocrisy either. It can be if you oppose legislation in general or wherever technological measures could be used instead. But people may have other criteria such as being against legislation that's bad for them and for legislation that's good for them. Nothing wrong with that.
You picked an awful example. Microsoft makes a lot of products and not one of them is commonly called simply "Microsoft". But there are many companies whose products are commonly called by the company's name and the company name, in the role of a product name, is pluralised. If I told you I owned two Ferraris, would you correct me? What would you have me say? "I own two Ferrari cars"?
It amazes me that people who call Mnchen Munich can get all high an mighty when someone dares say "Legos".
It's OK to change words--in all or some forms--when you import them into your language, to make them blend in better. There's absolutely nothing wrong with that and it's done all the time. Wouldn't it be simpler if Lego behaved like most other nouns? So why complicate matters?
Agreed on the component reuse. Writing a less capable version of something that the desktop provides is silly.
But in the particular case of open/save dialogs, I'd like to get rid of them altogether with XDS (Direct Save)
The application's UI includes a draggable icon representing the document. You drag it to an open file manager window and the file gets saved where you drop the icon.
This is especially nice if the file manager works like the MacOS Finder, where you can hover over a folder icon while dragging something to open that folder (pressing space opens it before the timeout).
I read about this being a general way to save files on Acorn Archimedes machines before x86's even had a GUI, so the idea isn't new.
A lot of slashdotters are Americans. They're used to writing mph for miles per hour, and when they find themselves in metric land, they naturally just substitute a "k" for the "m".
As for km/h being the only correct form, that depends on your outlook. You could argue that "k" per hour is vague and, if anything, should refer to kilos (kilograms) per hour. You could also argue that no-one is actually going to be confused about what kph means, and that being anal-rententive about correctness is all fine and dandy in physics papers, but not really necessary in newspaper articles and on you speedometer.
You could even argue that "kph", "mph", and "km/h" are all wrong because of the "h". The only correct unit is m/s (with any suitable prefix) and one wrong guy telling another slightly more wrong guy that he's wrong is a hypocrite.
"kph" annoys me somewhat (ok, a lot), but I it's really not about correctness. It's about convention.
I don't see a big difference between this and normal tagging, except we get more data out of it. I don't think researchers will be calling the animals while they're off duty:-)
Very few people are in a position where they can't even trust a bank. For anyone else, a box in a bank vault seems an appropriate place to store passwords. I imagine some banks can even enforce restrictions on who can access the box. Then you could stipulate, when you rent the box, that whoever is the CTO of your company at any given time is the only one who can access it.
Alternatively, you can arrange it so that you need n people from a group of m to decrypt a file (either all your important files, or just a file containing a normal private key and passphrase you can use to decrypt all the other files).
I think PGP has support for this, but even if it doesn't, you can still do it by having everybody know some of the characters in the password, but not the whole thing.
For many people, there's no reason to have binaries in one's home directory, but for some there's a very good reason. That's where we develop binaries.
Sometimes we even run some of those binaries as root, or package and distribute them.
There's no need for panic, but there is a need for humility and caution.
Here in the americas we have a lot of land and the long term affects of pollution are diluted. We have more space...
Hmm.
Iceland has about 7 people per square mile. Mongolia has 4, and the U.S. has 81. And yes, The U.S. figure includes Alaska.
As an Icelander, I can tell you that we love praise from foreigners (hell, we love it when we find a foreigner who knows Iceland exists), but all this "native" talk? Yes, Iceland is run by "native people". So is France.
And can you point me to those coal supplies? I ran out of geothermal energy and need to heat my igloo.
It's OK and expected for the computer not to do anything useful with bad input (a physical object in this case). It's not OK for it to become unable to function and process valid input as a result. Remember the Yorktown? Entering 0 into that field was an error, but the application software should have survived it. Failing that, the application software could have gone beserk, but the operating system should have survived that.
It seems to me that you're not just saying that Apple can be forgiven for this, but that it wasn't a mistake.
Your parent post and mine are not talking about how things are, only about how things should be. We can agree that invalid input should not destroy a system, even though we all know it's very hard to design such reliable systems.
In my effort to continue to spread this meme, I'd like to inject a couple of points.
The two big problems with this are the likelihood of misidentification and the fact that you can't just get a new fingerprint if somebody gains the ability to buy stuff with yours. (I feel the tracking problem is less severe because people are already tracking us with credit/debit card numbers and the world hasn't ended)
The identification problem is a very hard. As our pal Schneier likes to point out, a system that answers the question "is this person who they say they are" with impressive accuracy isn't necessarily any good at answering the question "who is this person". The accuracy drops fast as the number of people in the system increases. But don't throw out this system just yet. Is the base accuracy high enough, or can we keep the population low enough for the error rate to be acceptable? When Phil in L.A. is scanned at the supermarket, do we really need to consider Joe in N.Y. as a possible match(*)? Can we weed out more people with other checks before the fingerprint match is performed? I don't know the error rate of the best fingerprint matchers, but I need to know that, and the population size, and do the math if I'm going to reject a fingerprint id system on grounds of the misidentification risk.
The other big problem is devastating to your ability to use a biometric id system, but not to anything else. A stored reading can be marked as compromised in the system so an attacker can't use it any more. You won't be able to use it either, but you haven't lost anything you had before the system was put in place (unless some pea-brain decides that this shall be the only way to pay). You haven't even lost everything you gained when the system was implemented. You now have a choice to dictate that only a debit card + a finger print is enough to make a puchase with your account, which is safer than the credit card alone, although no more convenient.
Please, truly consider the benefits and liabilities of any new system and the system it replaces. At the very least, it'll make for more stimulating discussion than an endless stream of "this is bound to fail catastrophically" posts.
* And when Joe travels to L.A., we know where he is because we tracked his ticket purchase;->
Slashdot Mirror
Yes, and its antonym, "uncopyrightable", is the longest word in the English language without repeated letters.
If one more source of mothers' maiden names crops up, that's not the problem.
Incidentally, it's funny that this comes up in a discussion related to Iceland. Icelander don't have family names and women are not renamed when they marry.
However, in the case of audio CD's (or things being marketed as such), something subtly different is going on. The thing that happens when you insert the CD under autorun is not the same thing that happens when you normally use audio CD's. What happens is unexpected. Therefore, you couldn't have authorised it to happen. The user's expectations matter.
In the real world, of course, we turn off autorun anyway, but I think it's needlessly submissive to say that anything that happens when we insert a CD under autorun happens with our permission.
You lack imagination. If you're going to fantasize about a spammer getting his comeuppance, picture his face covered in tattoos with the subject lines from his spam. Especially "ADD THREE INCHES TO YOUR PENIS!!!!!!!" right on the forehead.
nethack
LVM is the Logical Volume Manager, so that's even worse. You could be running LVM and LVM on the same machine (and LVM's and LVM in the LVM's!)
A couple of times after a crash and a soft reboot, X has started, set the video mode, and for a moment before it paints the screen for the first time, I saw what was displayed before the crash (minus a few lines at the top of the screen, which were garbled).
This is with a GeForce 2 and nvidia drivers.
I wonder if anyone can come up with a use for that. A filesystem in video ram could survive a crash, but so would a filesystem on disk. Maybe some application that needs more speed could use this?
But the real problem is this: You have letter.txt and Letter.txt. The user asks for Letter.TXT. Which file does the application choose?
A real case-preserving filesystem is needed to make sure letter.txt and Letter.txt don't exist at the same time.
I should be able to buy the right to listen to music seperately from any physical medium. I think some of the friction between consumers and publishers comes from the fact that the current model just isn't intrinsically sensible. A 0 or 1 directly from a CD is the same as a 0 or 1 from CD via the net. It's illogical to assign some artificial distinction to bits based on their pedigree and people feel that doing so is wrong. It just doesn't make sense, and people get upset over that.
I acknowledge the publisher's right not to make sense, but I do think it hurts them.
Some people belong to both groups, but that's not necessarily hypocrisy either. It can be if you oppose legislation in general or wherever technological measures could be used instead. But people may have other criteria such as being against legislation that's bad for them and for legislation that's good for them. Nothing wrong with that.
Source quench sounds like a wonderful DOS tool, which is probably why a couple of netfilter guides I've read recommend you drop those packets.
You picked an awful example. Microsoft makes a lot of products and not one of them is commonly called simply "Microsoft". But there are many companies whose products are commonly called by the company's name and the company name, in the role of a product name, is pluralised. If I told you I owned two Ferraris, would you correct me? What would you have me say? "I own two Ferrari cars"?
It's OK to change words--in all or some forms--when you import them into your language, to make them blend in better. There's absolutely nothing wrong with that and it's done all the time. Wouldn't it be simpler if Lego behaved like most other nouns? So why complicate matters?
I thought terrorism involved... well, terror.
But in the particular case of open/save dialogs, I'd like to get rid of them altogether with XDS (Direct Save)
The application's UI includes a draggable icon representing the document. You drag it to an open file manager window and the file gets saved where you drop the icon.
This is especially nice if the file manager works like the MacOS Finder, where you can hover over a folder icon while dragging something to open that folder (pressing space opens it before the timeout).
I read about this being a general way to save files on Acorn Archimedes machines before x86's even had a GUI, so the idea isn't new.
Anyway, wouldn't two dashes and a linebreak be a better way to clearly separate your sig from your posts? Its as close to standard as you can get.
As for km/h being the only correct form, that depends on your outlook. You could argue that "k" per hour is vague and, if anything, should refer to kilos (kilograms) per hour. You could also argue that no-one is actually going to be confused about what kph means, and that being anal-rententive about correctness is all fine and dandy in physics papers, but not really necessary in newspaper articles and on you speedometer.
You could even argue that "kph", "mph", and "km/h" are all wrong because of the "h". The only correct unit is m/s (with any suitable prefix) and one wrong guy telling another slightly more wrong guy that he's wrong is a hypocrite.
"kph" annoys me somewhat (ok, a lot), but I it's really not about correctness. It's about convention.
I don't see a big difference between this and normal tagging, except we get more data out of it. I don't think researchers will be calling the animals while they're off duty :-)
Alternatively, you can arrange it so that you need n people from a group of m to decrypt a file (either all your important files, or just a file containing a normal private key and passphrase you can use to decrypt all the other files).
I think PGP has support for this, but even if it doesn't, you can still do it by having everybody know some of the characters in the password, but not the whole thing.
Sometimes we even run some of those binaries as root, or package and distribute them.
There's no need for panic, but there is a need for humility and caution.
The R&D costs of this project are borne by Daimler/Chrysler, Norsk Hydro R&D, and Shell Hydrogen.
Hmm.
Iceland has about 7 people per square mile. Mongolia has 4, and the U.S. has 81. And yes, The U.S. figure includes Alaska.
As an Icelander, I can tell you that we love praise from foreigners (hell, we love it when we find a foreigner who knows Iceland exists), but all this "native" talk? Yes, Iceland is run by "native people". So is France.
And can you point me to those coal supplies? I ran out of geothermal energy and need to heat my igloo.
Or maybe IHBT, IHL, IWHAND?
It seems to me that you're not just saying that Apple can be forgiven for this, but that it wasn't a mistake.
Your parent post and mine are not talking about how things are, only about how things should be. We can agree that invalid input should not destroy a system, even though we all know it's very hard to design such reliable systems.
The two big problems with this are the likelihood of misidentification and the fact that you can't just get a new fingerprint if somebody gains the ability to buy stuff with yours. (I feel the tracking problem is less severe because people are already tracking us with credit/debit card numbers and the world hasn't ended)
The identification problem is a very hard. As our pal Schneier likes to point out, a system that answers the question "is this person who they say they are" with impressive accuracy isn't necessarily any good at answering the question "who is this person". The accuracy drops fast as the number of people in the system increases. But don't throw out this system just yet. Is the base accuracy high enough, or can we keep the population low enough for the error rate to be acceptable? When Phil in L.A. is scanned at the supermarket, do we really need to consider Joe in N.Y. as a possible match(*)? Can we weed out more people with other checks before the fingerprint match is performed? I don't know the error rate of the best fingerprint matchers, but I need to know that, and the population size, and do the math if I'm going to reject a fingerprint id system on grounds of the misidentification risk.
The other big problem is devastating to your ability to use a biometric id system, but not to anything else. A stored reading can be marked as compromised in the system so an attacker can't use it any more. You won't be able to use it either, but you haven't lost anything you had before the system was put in place (unless some pea-brain decides that this shall be the only way to pay). You haven't even lost everything you gained when the system was implemented. You now have a choice to dictate that only a debit card + a finger print is enough to make a puchase with your account, which is safer than the credit card alone, although no more convenient.
Please, truly consider the benefits and liabilities of any new system and the system it replaces. At the very least, it'll make for more stimulating discussion than an endless stream of "this is bound to fail catastrophically" posts.
* And when Joe travels to L.A., we know where he is because we tracked his ticket purchase ;->