It doesn't matter the input size, it hashes down to the same length. It does increase the CPU time, but not the storage space. If the hashing is done on the client side (pre-transmission), then the server has no extra cost.
For example, the hash of a Linux ISO isn't 10 pages long. If you SHA-256 something, it always results in 256 bits of output.
On the other hand, base 64-ing something does get longer as the input grows.
As an emacs user, have you considered org mode, with org-roam enabled? You can use source control to back it up or, use something like syncthings to move the files around.
As someone stuck in DTW, I feel the pain.
I just sleep in full plate, because keeping track of the AC difference is too hard (because I am lazy).
My opinion of Alien 3 went up a lot after watching all the movies that came after it.
Probably for tax purposes.
The beauty of Linux at home, you get to choose what works best for you.
Also, you can configure sudo to prompt every time if you really want.
I was on a system that was configured that way for "security", so I would just 'sudo bash' which is obviously much safer /s.
I totally expect one day a XFCE (Wayland) option will show up, I will click it, forget I did, and use it forever more.
XOrg is my daily driver for these reasons:
That being said, I have no fundamental opposition to Wayland, and will probably use it someday.
Hashing is more about obscuring the password if the database gets compromised. I guess they could send 2^256 or 2^512 passwords guesses, but at that point you probably have bigger issues.