Proton’s CEO turned out to be a Trumper with a Nazi dogwhistle username and a lot of Republican buzzwords peppering his vocabulary. Lots of people are defending Proton anyway because of sunk cost fallacy.

Unfortunately, several of the author’s conclusions are drawn from either errors or outright lies, or simply things being swept aside. Several of Andy’s later posts are ignored, as is the amount he doubled down. Him using the official proton accounts to call his statements the official proton stance is waved away. It basically only examines the cleaned up, shiny final version of events proton would like you to pretend happened after they deleted everything, instead of what actually happened. Worse, it pretends that was the only chain of events that happened. It’s straight up gaslighting.

It’s a very, very biased article that doesn’t even attempt to do any kind of deep analysis and just tries to justify its stance by cherry picking, instead of actually looking at the facts and coming to a conclusion from there.

Are you kidding me right now? You call a fascist takeover a bit of “dissent” that we need to “relax a little” about?

You think the CEO of a privacy company coming out in support of a dictator who wants to erode rights and abolish privacy laws, and believes in jailing dissenters, to not have gone rogue?

We literally have American citizens being sent to an offshore military concentration camp so their lawful rights can be waived, and you think that’s okay?!

A massive, massive astroturfing campaign Epic Games paid for in hopes of tarnishing Valve and Gabe Newell’s reputation to try and bolster their failure of a shop ecosystem.

Unfortunately, it worked, because there are people on the net who don’t remember the and days before steam, or even the initial versions of steam that people had Actual problems with, and not just made up ones.

If you think Mozilla is the canonical of browsers, you’ve been consuming too much of Google’s anti-mozilla propaganda after they announced v3 manifest.

Servers, and workloads are various- DNS, ntp, databases, a few websites, internal servers running code/apis/etc for internal processes, etc.

As someone who has strong opinions on this, and not only has a job but has a job related to exactly sort of thing… We use freebsd.

Specifically to avoid shit like systemd, and other questionable choices forced down people’s throats by idiots who can’t stop touching things that work well because they didn’t invent it.

Honestly, these days it’s pretty simple. The thing you need to remember is that you do not need to know EVERYTHING all at once. Learn a little bit, use it, keep what you use, discard what you don’t, get it in muscle memory, and learn a bit more. Very quickly you’ll be zooming through vim.

You can learn the basics, and go from there- the basics of vim (which imo everyone should know- vi is often the fallback editor), and then you can just casually learn stuff as you go.

Here’s the basics for modern default/standard vim: Arrow keys move you around like you expect in all ‘modes’ (there’s some arguments about if you should be using arrow keys in the vim community- for now, consider them a crutch that lets you learn other things). There’s two ‘modes’- command mode, and edit mode.

Edit mode acts like a standard, traditional text editor, though a lot of your keybinds (e.g. ctrl-c/ctrl-v) don’t work.

Press escape to go back into command mode (in command mode, esc does nothing- esc is always safe to use. If you get lost/trapped/are confused, just keep hitting escape and you’ll drop into command mode). You start vim in command mode. Press i to go into edit mode at your current cursor position.

To exit vim entirely, go to command mode (esc), and type :wq<enter>.

‘:’ is ‘issue command string’,

‘w’ is ‘write’, aka save,

‘q’ is quit.

In other words, ‘:wq’ is ‘save and quit’

‘:q’ is quit without saving, ‘:w’ is save and don’t quit. Logical.

Depending on your terminal, you can probably select text with your mouse and have it be copied and then pasted with shift-ins in edit mode, which is a terminal thing and not a vim thing, because vim ties into it natively.

That gets you started with basically all the same features as nano, except they work in a minimal environment and you can build them up to start taking advantage of command mode, which is where the power and speed of vim start coming into play.

For example ‘i’ puts you in edit mode on the spot- capital i puts you in command mode at the beginning of the line. a is edit mode after your spot- capital A is edit mode at the end of the current line.

Do you need these to use vim? Nope. Once you learn them, start using them, and have them as muscle memory, is it vastly faster to use? Yes. And there’s hundreds of keybinds like that, all of which are fairly logical once you know the logic behind them- ‘insert’ and ‘after’ for i/a, for example.

Fair warning, vim is old enough that the logic may seem arcane sometimes- e.g. instead of ‘copy and paste’ vim has ‘yank and put,’ because copy/paste didn’t exist yet, so the keybinds for copy/paste are y and p.