WCGW: Emacs, Tramp, Remote Editing.

I'm a long-time vim user. When I started programming when I was 14, I started with Notepad++ on Windows, but quickly migrated to Linux and Vim. When developing, I always used a wide variety of computers (school computer, parents computer, friends computer). But that caused a problem: I needed to bring my source around.

Eventually, I decided the solution to the problem was to get myself a server. I'd simply ssh into it, and run vim in a tmux. This was great! I could now logout from a computer anytime and resume my session from another place.

My flow with vim was based heavily on Ctrl+Z: The shell was a keystroke away. With tools like ripgrep and fd, I can easily find where methods are defined without relying on fancy IDE features, I get the imense power of CLI git, etc... But this came at a cost: the terminal sucks. I wish I could like the terminal, but it's unredeemable. Let's go over its biggest problems:

• It can't show images inline. No, w3m-img doesn't count.
• It can't change the font size for a single line. I'm editing this file in emacs, and the title is in a fatter font ahn the text.

Every time I look at certificate management, I wonder how the fuck is it possible that this god-forsaken mess of technology can possibly work. And today, Microsoft has reinforced that feeling one more time.

Microsoft has a file format called "STL" (don't ask me what it is for), where they keep the list of certificates they trust, along with some metadata for each certs.

Some of those metadata include whether this certificate has been deprecated, which is really important to avoid having problems if a certificate ends up in the wrong hands. So far, so good, this all makes sense.

So Microsoft has five different ways to handle deprecation (which is a bit much, but ah well), all described in this document (which was not saved on the wayback machine before today, if you can believe that).