I used to run the (kubernetes-run) ingress-nginx. When they announced they’d stop updating it, I knew I wanted to move to the Gateway API/HTTPRoute method, because that seems like the future. I originally switched to nginx-gateway-fabric. That is controlled by NGINX/F5 though, and they want money, so they’re putting features I want behind a very expensive paywall. You know who doesn’t paywall features and also supports Gateway API v1.5.1 (or newer)? envoy-gateway.
I have been enjoying watching @ninakalinina switch her primary workstation from MacOS to NetBSD. The various issues she’s hitting really remind me of the early days of Linux, and the (fun) frustration that comes with getting everything up and running. So, I decided to give it a shot, for fun. Unfortunately NetBSD has zero support for the wireless driver of the laptop I want to run (iwx), but OpenBSD did, so let’s see how it goes…
I’ve been a paying member of Proton for almost 10 years (10 years in February 2026, it looks like), so I’ve been heavily hooked into their ecosystem. My every-day stuff was ProtonMail, ProtonVPN, and ProtonPass. I synced stuff to ProtonDrive as a backup of a backup, and I used ProtonCalendar as my personal calendar. I don’t do a heavy amount of calendaring, however, so I don’t count that as one of my main products. I’m moving on from Proton, so I thought I’d document the issues I’ve had moving, and the alternatives for the different products.
I am not sure what I’m going to write here. With everything going on in the world right now (cliche phrase, but COME ON), I decided to try and write down some off my angst and stress and depression. As it is, I’m fairly lucky right now, and not heavily effected (yet). Many people are much much much worse off than I am from this, but this is just the beginning, so it’s about what’s coming down the road as much as it’s what’s currently happening.
I decided to experience some nostalgia and learn some new useless stuff by playing with some different file sharing platforms, new and old. I also played some platforms that are specifically not made for file sharing.
To do this, I use The Silent Library’s libraries. This is both the main library (subbed content) and the Raw Wing, which holds raws that typesetters and subbers use. I explain a bit of what The Silent Library and Gaki no Tsukai is in this blog post. I love the original show and the catalogued associated shows so much, they are so fun. Full credit to Bipedal for curating and numerous typesetters (the unsung heroes) and subbers (the more-sung heroes) for all their work.
All the method belows are not the best way to get TSL files, unless you are already using the platform. Then maybe it’s the way to go. In this blog post I’ll discuss what I’ve set up, and any quick notes on challenges/problems. The page that indexes the various protocols/networks is at https://tsl.joyrex.net. The below is more about how the setup went and how to access the data.
I’ve spent a lot of time writing some better code to handle keeping the on-disk version of The Silent Library (or anything) up to date with what IPFS sees/knows about. This means it scans both libraries and adds/removes files to/from IPFS as needed.
Through this experience, I wrote a script in python, and a script in go. The go one is unfinished, but the python one is working. In both cases I did this in a “dumb” way, where I wrote all the code to scan and compare libraries, got a clean list of differences/changes that need to be made, then looked at uploading files. This is where I got stuck. This is for various reasons: I am new to writing serious stuff in both languages, the IPFS doco is poor, and IPFS itself seems to be in constant flux. This experience has shown me that IPFS is not a good solution for sharing The Silent Library, or possibly any large project. Below I will list what I’ve done since the original blog post, as well as further details of the problems I hit trying to explore the IPFS ecosystem.
The Setup was documented soon after the first blog post. The IPFS / Summary sections where documented a couple months later.