I am well aware that third party extensions for FF4 exist that add status bar function.
I haven't used FF4 myself, but I would be surprised if you couldn't just enable the status bar in about:config, no extensions needed.
Or the government would have to lease the right to run data lines on public property to anyone who asked. But then that government would have to set a price, which means the government is now in the internet business whether they like it or not.
I guess what I'm getting at is that a "free market" for broadband cannot and will never exist.
If there were only a name for such a rule...
But they're not talking about that, are they? They don't want my streaming video to interfere with their other customers' VOIP calls... which would seem to suggest that they don't actually have the capacity to deliver their Unlimited****** (up to) 10Mbps** that they sold to everyone in my neighborhood.
We have this fundamental problem where these companies have oversold the bandwidth, and the only solution they're willing to consider is to invent rules that will give you less of what you paid for. Because any other solution would force them to abandon an already-misleading marketing gimmick.
- Creating a fake Facebook account.
- Using a picture of an attractive female in your age range.
- Locating your friends.
- Carpet-bombing them with friend requests. (Surely someone will bite.)
- Sending you a friend request. (I'm a friend of a friend, so we've probably met, and you've just forgotten.)
- Reading everything about you.
It doesn't matter what your privacy settings are. I would bet money that you could get access to 99% of Facebook targets' info by following that pattern. Social networks are practically designed for social engineering hacks.
Hash = 1-way crypto
The only way to "un-md5" anything is to crack it. Also, I'm not sure you actually put any real thought into this.
Since it's best practice to store only password hashes (and not the passwords themselves) in your database (or whatever), your process is apparently:
- Client md5's the password, sends it to server
- Server "un-md5"s the password (let's say for argument's sake that this makes perfect sense)
- Server md5's the un-md5'd password
- Server checks hash against user's hash in the database