So Microsoft Research reinvents Band-in-a-Box which has been around for years and already lets you feed it an MP3 and it'll tell you the chord changes. Then you can use that to have Band-in-a-Box generate a song in any style you choose. Nothing new here. Move along.
SecureCRT uses tabs in a window for each session you have open. You can open a new tab with a "sftp>" prompt and enter sftp commands, although I think that using filezilla or a file manager like you mention is much easier.
The best part about SecureCRT is that you can install the lrzsz package on your Linux boxes and then use sz and rz commands in the remote session to send and receive files to/from your local computer. No need to mess around with scp, sftp, or opening other windows or tabs. It's very nice, and far easier and faster to use than other methods.
It seems that nobody remembers the transition between KDE 1 and KDE 2.
Nobody, indeed. Had the KDE team remembered the transition and how hard it was for users, then they (hopefully) would made the effort not to repeat that mistake. Instead, history repeats itself. Here's hoping the KDE team learns their lesson this time.
Even accepting your price that's a cost of about 12.7 cents per gigabyte and you can get 800GB native LTO-4 tapes for about $50, which comes out to about 6.3 cents per gigabyte.
You're conveniently ignoring the cost of the tape drive. The cheapest LTO-4 drive on Newegg is $2230. That makes a tape backup solution much more expensive per TB than hard drives, at least until you have a *lot* of tapes.
and #2 if you let someone enter ' pass123 ' but you silently store 'pass123' then the user will have no idea why their clever password doesn't work.
You're assuming that when they enter they enter their password at another time that the same trim was not made. As long as the app is consistent in how it accepts the input then the password will always work. Another option for the programmer would be to not allow the input field to accept spaces at all. If a space is typed, don't accept the keypress and don't display an asterisk to show a character being input. I used just such an application about 20 to 25 years ago but I can't recall what it is. Surely you have used applications with fields that only accept a limited subset of characters, such as fields only allowing you to input numbers.
The better question is, why care if they type spaces before or after their password? You can store a string of spaces just as easily as printable characters...
State Sen. Cecil Staton, who wrote the bill, said the measure is designed to keep the Internet safe for children.
The Internet isn't safe for children. That's why parents should do their job and know what their kids are doing online not using the government to create a nanny-state.
That is so damn wrong. I hope you never design user interfaces. Consistency is key, and changing a user's password, especially transparently, totally wrecks consistency and user expectation.
Hey buddy, you've missed the whole point. The system shouldn't limit what characters to accept for a password in the first place.
For example if Puffs sold "Puffs brand Kleenex" and not "Puffs brand facial tissue" would they lose? Until it is tested the trademark is iffy but so far Kleenex doesn't go nuts about people using it as a generic term since they see it as to their advantage.
Trademark law goes back very far and there is a lot of existing case law. Since there is no other manufacturer of facial tissue using the term Kleenex other than the trademark holder, it's safe to assume that the claim to the trademark is strong and that any challengers would lose. Netbook is a very new term and I would bet that many people do not know what a netbook is. I read Slashdot regularly and I didn't know what a netbook was until I read this article. I had seen the term before and assumed, in regular Slashdot fashion, that it was a misspelling of notebook and had not been corrected by an editor.
I'm not sure what your point is. If you input "bdf[10 spaces]" or "bdf[1 space]" and your password library trims spaces, they will both be converted to "bdf". As long as the homegrown password library trims spaces after accepting input then your password will always be stored as "bdf" no matter which of the first two instances you entered.
Apparently, Slashdot likes to mock me and transmorph my upper password from "bdf[10 spaces]" to "bdf[1 space]".
Your browser is doing that. It collapses multiple spaces into one, which is why we have the HTML entity. Your spaces are there if you view the source to your message.
So, how would you handle "_____x_____" (where the underscores represent spaces)? What error message would you display that didn't result in a response of "but I did type at least 8 characters"?
If you want a answer to that, you'd have to ask the person who created the broken password system that doesn't allow spaces at the beginning and end of a password. We have no information to infer that the application in question required at least eight characters.
Both Windows and Linux do not have this limitation with spaces before and after password. They will both accept spaces with no complaints. If I were writing a custom application with my own password management, I'd either use an existing password library that doesn't have the limitation or, as a last result, roll my own that accepts any characters for passwords.
It appears to me that the broken application that the original poster refers to is using their own password storage mechanism. It would not be hard to strip spaces from the password when it is taken from the user and then used to store the password or compare against the stored password. Ideally, the program should allow the user to enter any characters they want for the password. My initial reply was made because it shows the programmer has proven to be lazy and is making the user do what the computer should be doing instead.
Frankly, I would treat a password field this way and assume that a user meant to send it exactly as you received it. Any other route leads to madness.
I agree 100%. If the computer system was dictating what they can and cannot put in their password then there is something wrong with how they are dealing with passwords.
Why the hell would you want to change a user's password from what they entered?
Here's the question you should be asking: Why should the user do something that the computer can do for them?
So I'm the Luser and type "pink ponies " for my new password. Your software silently changes it to "pink ponies"
And when you enter your password again to log in, "pink ponies " is changed to "pink ponies", compared against the stored "pink ponies" and successfully authenticates you. There is no problem.
Some of the bad gas mileage on those large vehicles is weight and drag coefficient.
Some, but not all. The real problem is that car companies aren't legally required to to engineer light trucks to get the same gas mileage as cars. Therefore, they don't put the engineering effort into it and an entire class of vehicles has poor gas mileage.
Those "tastes and desires" were SHAPED by the automotive industry.
As they are for all vehicles.
Every time you saw a TV ad that showed a Jeep bounding up the side of a mountain, or a Land Rover dodging fallen trees and boulders, or a Yukon parked in the middle of the wilderness,
Or a minivan filled with kids, or a sports car zipping along through tight mountain curves, or a small four-cylinder car driving through city streets...
the industry was trying to convince you that THIS was what YOU needed.
That's called marketing. Industry does that with everything, from vehicles to cell phones to toilet paper and groceries.
Different people have different tastes. A truck may appeal to one person more than another for any number of reasons aside from advertising. My point was if a small pickup truck can be built to get the same gas mileage as a small four-door car, would you still look down on the person driving the truck just because it's a truck and you don't think they need it? We should encourage the automotive industry to make fuel-efficient vehicles, not just berate people who choose to purchase a certain type of vehicle despite our personal opinions of whether we think they need it or not.
So instead of encouraging car companies to produce trucks and SUVs that get good gas mileage, you advocate that people should change their tastes and desires? That's advocating treating the symptom and not the problem. The question you should be asking is why are the car companies still making trucks and SUVs that only get 12 mpg.
Slashdot Mirror
So Microsoft Research reinvents Band-in-a-Box which has been around for years and already lets you feed it an MP3 and it'll tell you the chord changes. Then you can use that to have Band-in-a-Box generate a song in any style you choose. Nothing new here. Move along.
The Police one is awesome, even if the instruments do sound like cheap general MIDI sounds.
SecureCRT uses tabs in a window for each session you have open. You can open a new tab with a "sftp>" prompt and enter sftp commands, although I think that using filezilla or a file manager like you mention is much easier.
The best part about SecureCRT is that you can install the lrzsz package on your Linux boxes and then use sz and rz commands in the remote session to send and receive files to/from your local computer. No need to mess around with scp, sftp, or opening other windows or tabs. It's very nice, and far easier and faster to use than other methods.
Nobody, indeed. Had the KDE team remembered the transition and how hard it was for users, then they (hopefully) would made the effort not to repeat that mistake. Instead, history repeats itself. Here's hoping the KDE team learns their lesson this time.
For what it's worth, Windows Update on XP does that.
Just imagine if the Chinese government used all this effort on something that was actually productive.
Then that should be a clue that the KDE developers need to still be fixing bugs in 3.5.
You're conveniently ignoring the cost of the tape drive. The cheapest LTO-4 drive on Newegg is $2230. That makes a tape backup solution much more expensive per TB than hard drives, at least until you have a *lot* of tapes.
This isn't slashdot?
You're assuming that when they enter they enter their password at another time that the same trim was not made. As long as the app is consistent in how it accepts the input then the password will always work. Another option for the programmer would be to not allow the input field to accept spaces at all. If a space is typed, don't accept the keypress and don't display an asterisk to show a character being input. I used just such an application about 20 to 25 years ago but I can't recall what it is. Surely you have used applications with fields that only accept a limited subset of characters, such as fields only allowing you to input numbers.
An equally valid question.
From the article:
The Internet isn't safe for children. That's why parents should do their job and know what their kids are doing online not using the government to create a nanny-state.
Hey buddy, you've missed the whole point. The system shouldn't limit what characters to accept for a password in the first place.
If they roll their own password system then I guess they'd be dumb enough to use different sanitizing functions.
Trademark law goes back very far and there is a lot of existing case law. Since there is no other manufacturer of facial tissue using the term Kleenex other than the trademark holder, it's safe to assume that the claim to the trademark is strong and that any challengers would lose. Netbook is a very new term and I would bet that many people do not know what a netbook is. I read Slashdot regularly and I didn't know what a netbook was until I read this article. I had seen the term before and assumed, in regular Slashdot fashion, that it was a misspelling of notebook and had not been corrected by an editor.
Standard disclaimer: I'm not a lawyer.
I'm not sure what your point is. If you input "bdf[10 spaces]" or "bdf[1 space]" and your password library trims spaces, they will both be converted to "bdf". As long as the homegrown password library trims spaces after accepting input then your password will always be stored as "bdf" no matter which of the first two instances you entered.
Your browser is doing that. It collapses multiple spaces into one, which is why we have the HTML entity. Your spaces are there if you view the source to your message.
If you want a answer to that, you'd have to ask the person who created the broken password system that doesn't allow spaces at the beginning and end of a password. We have no information to infer that the application in question required at least eight characters.
Both Windows and Linux do not have this limitation with spaces before and after password. They will both accept spaces with no complaints. If I were writing a custom application with my own password management, I'd either use an existing password library that doesn't have the limitation or, as a last result, roll my own that accepts any characters for passwords.
It appears to me that the broken application that the original poster refers to is using their own password storage mechanism. It would not be hard to strip spaces from the password when it is taken from the user and then used to store the password or compare against the stored password. Ideally, the program should allow the user to enter any characters they want for the password. My initial reply was made because it shows the programmer has proven to be lazy and is making the user do what the computer should be doing instead.
I agree 100%. If the computer system was dictating what they can and cannot put in their password then there is something wrong with how they are dealing with passwords.
As long as your password system interprets things in the same way, what is the problem?
Or easier than fixing their broken, homegrown password system that can't handle storing spaces.
Here's the question you should be asking: Why should the user do something that the computer can do for them?
And when you enter your password again to log in, "pink ponies " is changed to "pink ponies", compared against the stored "pink ponies" and successfully authenticates you. There is no problem.
The real WTF is why the application didn't just trim the spaces off the password once it was entered. And we call users stupid...
Here's the print version of the article: http://www.extremetech.com/print_article2/0,1217,a%253D235406,00.asp
Some, but not all. The real problem is that car companies aren't legally required to to engineer light trucks to get the same gas mileage as cars. Therefore, they don't put the engineering effort into it and an entire class of vehicles has poor gas mileage.
As they are for all vehicles.
Or a minivan filled with kids, or a sports car zipping along through tight mountain curves, or a small four-cylinder car driving through city streets...
That's called marketing. Industry does that with everything, from vehicles to cell phones to toilet paper and groceries.
Different people have different tastes. A truck may appeal to one person more than another for any number of reasons aside from advertising. My point was if a small pickup truck can be built to get the same gas mileage as a small four-door car, would you still look down on the person driving the truck just because it's a truck and you don't think they need it? We should encourage the automotive industry to make fuel-efficient vehicles, not just berate people who choose to purchase a certain type of vehicle despite our personal opinions of whether we think they need it or not.
So instead of encouraging car companies to produce trucks and SUVs that get good gas mileage, you advocate that people should change their tastes and desires? That's advocating treating the symptom and not the problem. The question you should be asking is why are the car companies still making trucks and SUVs that only get 12 mpg.