Actually, you know what? No. It's way too slow, and hitting "previous" now does nothing. So nevermind, not that good. It should probably be done elsewhere.
Almost, but the really important feature for me is the hit-count for search results. So I may just look at hacking it into Migemo. Shouldn't be too hard since it has to know how many results there are for the highlighting thing. Thanks.
I like Flock, largely because of Flickr integration and the Interestingness media bar, that's pretty addictive.
The main thing that keeps me from using Flock or Firefox full-time is the in-page search. Safari just blows everything away on that, and I don't think it would be terribly hard to add to FF/Flock. Add a total match count, and highlight all by default, and I'm there.
Flock has come quite a way in the last year though, I'll have to give them that, it's not quite as "slap you in the face with every social network ever" as I seem to recall it being, and it's relatively easy to switch from one network view to the next.
It's still way too unstable for me day to day, but it's tempting enough to keep trying anyway. 4.0.66 lasted a week before I fired it this morning.
My main problems are with multi-head related (it really doesn't work very well from my and others experience, especially non-Xinerama multihead), but it keeps improving.
Good work KDE Team
Palm shows no signs of having Flash on their phones either AFAIK. Which bums me out kind of, but since they work with YouTube in a similar fashion to iPhones, it's not as bad as I guess it could be.
Thank you, you said it much more succinctly than I had been. There's a balance to everything. If the security admins are doing their jobs, the compromise of 1 desktop user password shouldn't be the end of the world for a company. They get access to a very limited set of data that that user has access to, and that's it. The attacker shouldn't be able to drop hash tables of passwords, shouldn't be able to copy the companies database backups, etc.
Sensible 2 factor access control can also be a very good thing. "password plus USB token" for instance is pretty straightforward, mostly brainless from the user's perspective, etc.
We're on the same team. I'm anti-over-complicated passwords that change every 4 days. I do agree that they need to change occasionally due to keyloggers, but 60 or 90 days is probably fine from an 80/20 standpoint.
What I was getting at with Security Noobs is that they get a little responsibility and change the password policy to 14 character mixed-case alphanumeric with a minimum of 1 number and 2 "special characters", and have the password change often. I think that's a huge mistake that leads to sticky notes and users mailing their password to their GMail account.
At first, we used a pretty strict password policy at work...+8 characters, numbers, symbols, capitols etc. all required. YOu have to change your password every month.
This is a security DISASTER! Everybody will set their password to like "jason1!" the first month, then "jason2@" the next month", then "jason3#" the next month and so on. Finally I changed the policy. Now a user can request a password that never changes, so long as it meets *MY* requirements...
I've found a lot of Security Noobs do this, and it's friggin annoying. It leads to people emailing their password to themselves, putting it on sticky notes, business cards, etc.
A policy of a password that changes and meets requirements is a Good Thing, but 30 days is too quick, and if every password has to look 1337, no one will ever remember them. Yes, passwords can be trivially cracked on good hardware and administrator access to a Domain Controller. You know what? Lock down that Admin access and don't let 80% of your company be Domain/Local admins.
I stumbled my way into getting on Sprint's global cellular outage/resolution mailing list.
It's staggering. Especially when you pull out all the little issues and just focus on total service outages for entire markets. I couldn't believe how much they're down in certain markets. Always seems fine to me, but then again, I'm not on the phone "Five-Nines" of the time.
I think that has a lot to do with it, if you're looking for hosting for some site, 5-nines is really necessary, or close to, with kick-em-in-the-teeth if they don't deliver SLA's, since that site needs to be up all the time and can be hit by anyone, anytime. My cellphone? Not so much. It needs to work when I need it to work, and if there's a 3 minute outage sometime during my day, I probably won't ever notice it.
Hah yeah, nah, I'm not easily intimidated by developers, but I really didn't want to appear as some wackjob stalker. I should have camphone'd our vanity plates next to each other though. Ah well.
I saw his Jeep at my local supermarket a few weeks ago and was going to head back in and find him, or stick around until he headed out and offer him a 6-pack...Something.
I didn't want to look like that much a fanboy dorkass though, and wisely let it go. Would have been nice to thank the guy though I guess.
I don't see how PGP would have helped. The idea is that you encrypt with the RECIPIENT's Public Key, then the recipient decrypts with his Private Key.
The sender cannot encrypt with his OWN keys because only the sender will have the sender's Private Key. It would not have helped here, since assuming the recipient (intended or otherwise) had their Public Key published, the sender would have encrypted against Reporter's public key and Reporter would have decrypted it with his private key.
The only thing that would have worked is if they put everything they send in an encrypted file and attach that, with an agreed-upon passphrase to open that file. That's pretty much something no lawyer I've met would ever be willing to do, or they'd use the same passphrase for everyone.
Study after study shows that people 16-25 years of age are such a vanishingly small percentage of the music listening public, that any backlash is likely to go totally unnoticed. If they were actually targeting the core fanbase demographic of most artists, it might be more of an issue.
Your dry realism is welcome in this "get in quick with the 'what court is open at midnight' joke and then split" world we're living in. I actually thought before posting "well, Night Court was an arraignment court and not a civil court of the type used for such moronic patent suits", but then decided to post anyway.
You're right, I should have found a popular 80's show about an all-night patent and trademark court, but I just couldn't be bothered to look hard enough.
Oh I'm sorry, you're right. I keep getting the US govt and Russian govt mixed up. I have to remember, it's MY government that wants to see behind all the locked doors.
Slashdot Mirror
Actually, you know what? No. It's way too slow, and hitting "previous" now does nothing. So nevermind, not that good. It should probably be done elsewhere.
Almost, but the really important feature for me is the hit-count for search results. So I may just look at hacking it into Migemo. Shouldn't be too hard since it has to know how many results there are for the highlighting thing. Thanks.
Bastard slashdot. New Rule. People who start a thread should have mod points for that thread.
I like Flock, largely because of Flickr integration and the Interestingness media bar, that's pretty addictive.
The main thing that keeps me from using Flock or Firefox full-time is the in-page search. Safari just blows everything away on that, and I don't think it would be terribly hard to add to FF/Flock. Add a total match count, and highlight all by default, and I'm there.
Flock has come quite a way in the last year though, I'll have to give them that, it's not quite as "slap you in the face with every social network ever" as I seem to recall it being, and it's relatively easy to switch from one network view to the next.
It's still way too unstable for me day to day, but it's tempting enough to keep trying anyway. 4.0.66 lasted a week before I fired it this morning. My main problems are with multi-head related (it really doesn't work very well from my and others experience, especially non-Xinerama multihead), but it keeps improving. Good work KDE Team
Palm shows no signs of having Flash on their phones either AFAIK. Which bums me out kind of, but since they work with YouTube in a similar fashion to iPhones, it's not as bad as I guess it could be.
And the website and air base are in Suffolk in the UK, don't be fooled by the .com TLD :-)
Thank you, you said it much more succinctly than I had been. There's a balance to everything. If the security admins are doing their jobs, the compromise of 1 desktop user password shouldn't be the end of the world for a company. They get access to a very limited set of data that that user has access to, and that's it. The attacker shouldn't be able to drop hash tables of passwords, shouldn't be able to copy the companies database backups, etc.
Sensible 2 factor access control can also be a very good thing. "password plus USB token" for instance is pretty straightforward, mostly brainless from the user's perspective, etc.
We're on the same team. I'm anti-over-complicated passwords that change every 4 days. I do agree that they need to change occasionally due to keyloggers, but 60 or 90 days is probably fine from an 80/20 standpoint. What I was getting at with Security Noobs is that they get a little responsibility and change the password policy to 14 character mixed-case alphanumeric with a minimum of 1 number and 2 "special characters", and have the password change often. I think that's a huge mistake that leads to sticky notes and users mailing their password to their GMail account.
At first, we used a pretty strict password policy at work...+8 characters, numbers, symbols, capitols etc. all required. YOu have to change your password every month. This is a security DISASTER! Everybody will set their password to like "jason1!" the first month, then "jason2@" the next month", then "jason3#" the next month and so on. Finally I changed the policy. Now a user can request a password that never changes, so long as it meets *MY* requirements...
I've found a lot of Security Noobs do this, and it's friggin annoying. It leads to people emailing their password to themselves, putting it on sticky notes, business cards, etc.
A policy of a password that changes and meets requirements is a Good Thing, but 30 days is too quick, and if every password has to look 1337, no one will ever remember them. Yes, passwords can be trivially cracked on good hardware and administrator access to a Domain Controller. You know what? Lock down that Admin access and don't let 80% of your company be Domain/Local admins.
I stumbled my way into getting on Sprint's global cellular outage/resolution mailing list.
It's staggering. Especially when you pull out all the little issues and just focus on total service outages for entire markets. I couldn't believe how much they're down in certain markets. Always seems fine to me, but then again, I'm not on the phone "Five-Nines" of the time.
I think that has a lot to do with it, if you're looking for hosting for some site, 5-nines is really necessary, or close to, with kick-em-in-the-teeth if they don't deliver SLA's, since that site needs to be up all the time and can be hit by anyone, anytime. My cellphone? Not so much. It needs to work when I need it to work, and if there's a 3 minute outage sometime during my day, I probably won't ever notice it.
Hah yeah, nah, I'm not easily intimidated by developers, but I really didn't want to appear as some wackjob stalker. I should have camphone'd our vanity plates next to each other though. Ah well.
I saw his Jeep at my local supermarket a few weeks ago and was going to head back in and find him, or stick around until he headed out and offer him a 6-pack...Something.
I didn't want to look like that much a fanboy dorkass though, and wisely let it go. Would have been nice to thank the guy though I guess.
I don't see how PGP would have helped. The idea is that you encrypt with the RECIPIENT's Public Key, then the recipient decrypts with his Private Key.
The sender cannot encrypt with his OWN keys because only the sender will have the sender's Private Key. It would not have helped here, since assuming the recipient (intended or otherwise) had their Public Key published, the sender would have encrypted against Reporter's public key and Reporter would have decrypted it with his private key.
The only thing that would have worked is if they put everything they send in an encrypted file and attach that, with an agreed-upon passphrase to open that file. That's pretty much something no lawyer I've met would ever be willing to do, or they'd use the same passphrase for everyone.
Study after study shows that people 16-25 years of age are such a vanishingly small percentage of the music listening public, that any backlash is likely to go totally unnoticed. If they were actually targeting the core fanbase demographic of most artists, it might be more of an issue.
Your dry realism is welcome in this "get in quick with the 'what court is open at midnight' joke and then split" world we're living in. I actually thought before posting "well, Night Court was an arraignment court and not a civil court of the type used for such moronic patent suits", but then decided to post anyway.
:-)
You're right, I should have found a popular 80's show about an all-night patent and trademark court, but I just couldn't be bothered to look hard enough.
Where can you file anything at midnight?
Right here. I hear they filmed it for a long running reality series about people with no tans.
Damn /. and their random mod point fickleness.
So great, now we've got a Geek Propetual Motion Machine.
Chris Isaak has the answer. (I have no idea whose blog this is, just showed up in GIS and I didn't want to hotlink her image)
New power generation facility receives Plasmatic injection at its main energy dome. Technicians wearing specially fitted xray spex oversaw the fueling of the power station.
Can't improve on the classics.
Always mount a scratch monkey.
Oh I'm sorry, you're right. I keep getting the US govt and Russian govt mixed up. I have to remember, it's MY government that wants to see behind all the locked doors.
That happened years ago (sorry Bruce and Janet...)