clb92

u/clb92@kbin.social
1 posts · 78 comments

Recent posts

Recent comments

on /kbin Issues · c/kbinMeta · 3 pts · 2y

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 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.

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.

I've found a bug: The article preview buttons disappear after page reloads if bookmarks feature is turned on.

Once they're gone, I can toggle the "show article preview button" twice to get them to show up again, but once the page reloads, they flash briefly and disappear again. If I disable the bookmarks feature, they work as expected.

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.