Get a load of Ross Ulbricht ovah here!

I’d love to see the state of online banking if everyone were to manage their own ssh keys

Most people couldn’t figure out how to download a binary release from a GitHub repo, much less clone it, regardless of HTTP or SSH.

SSH keys are more like passkeys than passwords.

I think this post is about git CLI, not www.github.com.

SSH keys are very secure and you can still encrypt them with a password if you wish.

Atomicity: either all parts of the transaction complete, or all parts of the transaction don’t complete; there’s no “partly complete” state

Consistency: the state of the database after a transaction is stable; all “downstream” effects (e.g. triggers) of the query are complete before the transaction is confirmed.

Isolation: concurrent transactions behave the same as sequential transactions

Durability: a power failure or crash won’t lose any transactions

Traditionally, ACID is where relational databases shine.

• Push directly to master, not main
• No command line args, just change the global const and recompile
• No env vars either
• Port numbers only go up to 5280, the number of feet in a mile
• All auth is just a password; tokens are minority developers, not auth, and usernames are identity politics
• No hashes – it’s the gateway drug to fentanyl
• No imports. INTERNAL DEVELOPERS FIRST
• Exceptions are now illegal and therefore won’t occur, so no need to check for them
• SOAP/XML APIs only
• No support for external machines. If it’s good enough for my machine, it’s good enough for yours.