Overspark

Zen on the desktop, Firefox on mobile. Zen has quickly surpassed what I thought it would be capable of, and it keeps adding awesome UI bangers that I wish Firefox would have though of decades ago.

A cookie is a small piece of data a website can store on your computer, and it will be included with every request your browser makes to that website. While most visible cookie usage (I.e. the endless popups) is just to track you and violate your privacy, their are plenty of legitimate uses for cookies:

• store settings you make on a website, such as dark mode or (ironically) that you don’t want to be tracked
• store a session ID so the website can store more data on their end, such as the contents of a shopping cart. This is also often used for analytics, which is basically following the paths users take through a website to see if everything works as intended.
• store a successful login to a website. Most websites will require a cookie to allow you to log in. There are other ways to accomplish this but they’re ancient and annoying.

Basically you should keep declining cookie popups, except for functional cookies on a website where you actually want to do stuff (login, shop, etc) instead of just reading something.

DDG is good enough for me.

Oh yeah, the tools to help you with that have gotten much better, I completely agree with that.

25 years ago the people that were online were sitting behind a PC, not swiping on their phone and hoping the autocorrect got it right. So every typing mistake was an actual typing mistake on a real keyboard by an actual person. The use of language online has definitely gone downhill when phones entered the picture.

If you mean that most people write even worse now than 25 years ago then yes 😄

I met my wife on IRC. She was attracted to the fact that I could spell. That was 25 years ago.

I use mergerfs (and snapraid because I do care about my data and want parity) on ext4 formatted disks. This is a much better way to use your disks if you’re mostly just storing media. RAID is for mitigation of downtime after drive failure, not for joining a bunch of (differently sized?) disks into one pool if downtime isn’t really a problem.