I give my clients a simple process to create 'strong' passwords out of normal words or phrases (preferably 10+ chars) that makes them easy to remember.
I hate it when people recommend using weird passwords with numbers, special characters, first letter of various words and what not.
Use a fucking sentence. Much easier to remember, a hell of a lot of variation even if you don't mix anything in and if you do the better, but how would the brute-force attacker know in the first place?
OMG what shall I use as password? = (2*26+4)^33 = 4.9 × 10^57 (4 for,.!?)
do6&3(dNu(/ = advanced, but (2*26+10+20)^11 = 1.1 × 10^21
I doubt people would use as many special characters as 20, but I just picked a number. The point goes through quite well anyway.
And which of those passwords are the easiest to remember?
The whole idea of using it is: 1) You may not know in advance that you're going to do something where you would had wanted to keep the old version or need a backup. 2) It don't waste space as much as taking a whole damn copy of your files every time they are ever changed does.
.. maybe he could have had the time machine backup in an HFS+/HFSX image on a network mounted ZFS disk pool and have that one take snapshots every now and then. Handy for going back when time machine fails;D
He don't need it. But say he code some project and there's not much reason to keep a copy of the state from two weeks ago, but he _COULD_ see it if he wanted to.
It's not up to you to decide what he want to do with his data or why.
He wanted it for some reason (or maybe he didn't, but he still think it was bad that it was lost, if nothing else just because it happened.)
Sure he could had done it twice, but it probably wasn't _THAT_ important. Just disturbing that it was lost.
He probably don't want to take manual historical data backups, that's why he use time machine in the first place... He could do it on a raid array but that wouldn't had helped if time machine fucked up or some program decided to delete the data.
To take a backup copy of the time machine disk every now and then would probably be the best.
If you do not think that gives Google veto power over evil additional restrictions on the distribution of GPL software, you did not think very hard.
But they obviously don't want to.
More restrictions = Less popular software = Less consumer data for Google = !profit
Less restrictions = Everyone decides to use it = More consumer data for Google = Profit.
Sure it would be better for you, but not for Google. As long as all the crap the manufacturers do isn't enough to put you and "everyone else" from buying the phone in the first place. By then both Google and the phone manufacturer would think different(tm.)
I wonder how Symbian and MeeGo will be here. I doubt MeeGo will be open enough for my likening, but I can hope.
Slashdot Mirror
It's the standard for Apple retards.
Not that there are any vendor lock-in, no way sir, you're still free as ever. God bless Apple. Damn Apple-thread-trolls.
Apple is perfect, I really wanted my computer expensive, crappy speced, ...
Steve Jobs will still make great news out of it once they switch! :D
"One more thing! Starting (Shipping?) today, the iPhone will feature a standard micro-USB connector! Bla bla bla."
actually there is an older mini usb and a newer micro usb
But mini isn't micro. So I don't get the point ..
Oh boho how socialistic of them.
Stupid!
("Tea party ftw!" :D)
/ Scandinavian acting like an american.
I haven't heard of a 5-band phone
Nokia N8:
GSM/EDGE 850/900/1800/1900
WCDMA 850/900/1700/1900/2100
Exactly, what a complete bullshit.
700 AT&T LTE
850 AT&T
1710-1755 T-Mobile AWS-1
1900 AT&T, T-Mobile
2110-2155 T-Mobile HSPA
iPhone US: 850 & 1900.
iPhone Int.: 900, 1800, 2100.
Nokia N8: SM/EDGE 850/900/1800/1900, WCDMA 850/900/1700/1900/2100
Of course it can be done, and maybe even with the iPhone if they wanted to (unless Apple antenna designers suck .. :D)
You're all wrong. And no, I don't.
I just have wilder imagination (and reading skills?) than you do.
Ninten_HOE_'d, not Nintendo.
And not as in Nintendo-coded.
Directions/moves would be, well, directions/moves.
B, A can be interpreted in whatever way you like ..
duh ..
Assuming you just mean data of the account and not sniffing for account logins those two aren't necessarily comparable.
Your password may lock up loads of other data sources. Your (non e-mail) data may not.
I give my clients a simple process to create 'strong' passwords out of normal words or phrases (preferably 10+ chars) that makes them easy to remember.
And it probably still suck.
See: http://it.slashdot.org/comments.pl?sid=1864202&cid=34198438
Heck, if brute forced their fucking name would be better than most passwords any stupid scheme could come up with.
That may not be the best idea for other reasons, so make take someone else name =P
"Homer", no. :D
Force people to use 15-20+ characters and they will come up with something easy to remember _AND_ effective.
Or well, a hungry hobo I see. Makes sense :D
Hush, he's a security expert.
"Example: Tru57no1" = über ninja strength, recommended by NASA! Seen on TV!
even a single *wierd* character can defeat that,
Short answer: No.
I hate it when people recommend using weird passwords with numbers, special characters, first letter of various words and what not.
Use a fucking sentence. Much easier to remember, a hell of a lot of variation even if you don't mix anything in and if you do the better, but how would the brute-force attacker know in the first place?
OMG what shall I use as password? = (2*26+4)^33 = 4.9 × 10^57 (4 for ,.!?)
do6&3(dNu(/ = advanced, but (2*26+10+20)^11 = 1.1 × 10^21
I doubt people would use as many special characters as 20, but I just picked a number. The point goes through quite well anyway.
And which of those passwords are the easiest to remember?
The whole idea of using it is:
1) You may not know in advance that you're going to do something where you would had wanted to keep the old version or need a backup.
2) It don't waste space as much as taking a whole damn copy of your files every time they are ever changed does.
Stupid.
.. maybe he could have had the time machine backup in an HFS+/HFSX image on a network mounted ZFS disk pool and have that one take snapshots every now and then. Handy for going back when time machine fails ;D
He don't need it. But say he code some project and there's not much reason to keep a copy of the state from two weeks ago, but he _COULD_ see it if he wanted to.
It's not up to you to decide what he want to do with his data or why.
He wanted it for some reason (or maybe he didn't, but he still think it was bad that it was lost, if nothing else just because it happened.)
"I heard you liked backups so I .."?
Sure he could had done it twice, but it probably wasn't _THAT_ important. Just disturbing that it was lost.
He probably don't want to take manual historical data backups, that's why he use time machine in the first place ... He could do it on a raid array but that wouldn't had helped if time machine fucked up or some program decided to delete the data.
To take a backup copy of the time machine disk every now and then would probably be the best.
It's not a one-state backup. It's regular snapshots for all time backwards.
So no, he may not have lost his current state of the data, but he lost the history of his data.
His mac was his current backup backup.
belly ups?
"I Nintenhoe'd that shit!"?
Up, up, down, down, left, right, left, right, B, A
If you do not think that gives Google veto power over evil additional restrictions on the distribution of GPL software, you did not think very hard.
But they obviously don't want to.
More restrictions = Less popular software = Less consumer data for Google = !profit
Less restrictions = Everyone decides to use it = More consumer data for Google = Profit.
Sure it would be better for you, but not for Google. As long as all the crap the manufacturers do isn't enough to put you and "everyone else" from buying the phone in the first place. By then both Google and the phone manufacturer would think different(tm.)
I wonder how Symbian and MeeGo will be here. I doubt MeeGo will be open enough for my likening, but I can hope.
WebOS2 maybe is?
Yeah, I wanted to add a "or buy an open phone instead" comment.
Guess the Nexus One come closest. Don't know how open the N8 and such is.
So prior art is a valid counter-claim?
First shots of the natives:
http://www.markpeterhughes.com/photos/20070600LMAcrossAmerica/SDtoIN/08WI_1_CheeseHeads.JPG