guess what just broke on my laptop after 2 years

I'm guessing it was the floppy drive?

We're experiencing so many federation issues, I think. There's much less content in the communities/magazines I subscribe to when I browse them from Kbin, and in some I only see very old posts :(

My disaster recovery plan:

1. I plan on not having a disaster.

2. If I do have a disaster, I plan on trying to recover from it.

My biggest problem has been that the ink always dries up, since I don't print very often, and a laser printer has solved that for me. Now, about 3 years later, the black toner is still at 90%, and still working reliably.

Caddy reverse proxy handles that for me. I just set my domains' DNS to point to my public IP, where port 80 and 443 are forwarded to a server with Caddy listening.

Well, pack the flashlight and phone away and enjoy the movie.

Honestly, I mainly just use Google Play Books, since that's where I buy most of my ebooks. I do download and de-DRM my purchased books though, since I don't trust Google to keep all my books available to me in the future.

On my eink reader, I also use either Google Play Books or the default reader app, "Neo Reader" I believe.

That was fast.

Could we stop with the viruses for a while, please? Just a few years is all I ask.

Nice and clean looking result, great job!

1000/1000 Mbps fiber for $43 in Denmark, no data cap.

I like how it basically generated the Ubisoft logo.

It's the Scunthorpe problem.

Nothing's more permanent than a temporary solution.

"No, it's true, I swear! The coffee machines on our side can do both espresso and latte! And all the American barracks have 2-ply toilet paper! It used to be only 1-ply, but then last mo— What do you mean 'this guy is useless', I've just given you everything!"

Calckey sounds like a calculator/math/graphing application and Firefish sounds like another generic fork of Firefox.

They're implying that all the posts must be astroturfing.

The first paragraph is correct, but your second paragraph is not. A cryptographic hash function is a lossy one-way function. Knowing exactly how something was hashed does not mean you can turn the hash back into the starting value again.

The server would never see a plain text version of your password.

As you realized in your edit already, this part is not correct. The server would always receive your password plaintext (when signing up and when logging in), but only store it hashed and salted.

The server needs to receive your password to verify it and log you it. That's how it always is. As long as you are connecting via HTTPS, this is not a problem.