He's chosen to go to Russia to keep from being jailed by the US. He has a LOT more freedom there.

Someone (I forget who) has the FreeBSD fortunes-4 #791 sig:
IBM had a PL/I,
Its syntax worse than JOSS;
And everywhere this language went,
It was a total loss.

That's the way life worked up until the invention of writing.

Yes, I simplified it. I also got the first sentence wrong, and corrected that by mentioning the ability for congress to override a veto. The main point is that every bill goes before the President before it can become law.

The president must sign every bill before it becomes law. If the president chooses not to sign a bill, it is considered a veto and the bill is returned to congress. If it gets a 2/3 majority vote, the bill becomes law anyway. This is one of the primary duties of the president.

So yes, it went to the president, just like every other bill that has gotten through congress.

Also the Banach-Tarski paradox.

I have an algorithm. I open Keepass, type my master password, and use the generator to make a password for that site!

Freyja is also a goddess of War and Death. She takes half the slain warriors, Odin takes the other half.

So people have a "right to be forgotten" except by people actually publishing information about them. If the public record is important enough to preserve in violation of this "right" then telling people how to access the public record is surely an important duty.

The site owner should be responsible, not the search engines who don't host the content.

The problem is that you can't hide things from the service provider with nothing but a browser. You need an addon or such to do secure crypto. You need to decrypt the password database locally, in-browser, and without an addon that means using JS crypto, which isn't ideal. Your mailing example is very different, since it doesn't matter if the service provider knows the address and financials, they're the intended recipient of the info! With a password manager, you don't want the service to be able to learn the contents of the encrypted database. That means the encryption/decryption must be done client-side.

That said, it's perfectly possible to store the encrypted database on the internet. A local encryption/decryption program (like Keepass) works just fine, and if combined with a cloud storage client that also does local encryption/decryption (Wuala, Spideroak, etc) it should be quite secure.

I step off my bike, hit the walk button, and wait for the walk signal. Then I walk the bike across the crosswalk and get back on. It's really easy to become a pedestrian with a bike, and therefore be subject to the laws governing pedestrians. Just get off the bike!

Jetpacks are possible, but probably will never be practical.
The issue is the energy density of the fuel. If the energy density is low it takes a lot of fuel, which reduces flight time. If the energy density is high, it's a bomb strapped to someone's back, which means adding safety features, which add weight, which reduces flight time.
Jetpacks have been made, and they do work, but only for short times. You'll never fly around in one like a helicopter, the chemistry simply doesn't support it.
Sadly, Robbie Rocketpants shall forever be a part of the diseased imaginations of utter smegheads.

Helicopters fly because they're so ugly the Earth pushes them away.

Well, it's certainly better than timothy...