If all goes according to plan, you should now be able to comment on this blog post by replying to the related post on the fediverse. It’s a somewhat clunky system, but it should be fairly resistant to spam (you need to have an account on a federated server to post) and more importantly, it’s a way to provide some interactivity on an otherwise static site…
I just noticed that certain navigation functions on the page would attempt to direct you back to the clearweb if viewed from tor or i2p. This appears to have been due to a mismatch in my nginx config, but I think I’ve got it all straightened out.
I’m on a roll!
In 2025, this blog went from being a clunky, PHP application, only accessible via IPv4 and gopher; to a sweet static site, native on IPv4, IPv6, gopher, TOR, and now, I2P!
That’s right, this blog is now natively served on I2P.
This blog is now
For the homelab: I've met a lot of my learning goals over the last two years, and I find myself wondering what to do next.
For a little background, I don't work in IT. I don't need to learn any of this; it's just been a hobby of mine, mostly in pursuit of fun, knowledge, and control over my personal digital systems...
I picked up a Feker Alice98 in an attempt to get something a little more "ergonomic" than my previous keyboard. It's an "Alice" layout, with the interesting distinction of having two "B" keys.
This keyboard is also compatible with VIA, making keymapping, backlighting, and macros easy to manage. This keyboard isn't listed on VIA's website, though, so it requires manually importing the keyboard definition file. Hopefully VIA will add it officially, eventually.
It recently occurred to me that as I update each Linux container or VM, I'm downloading a lot of the same files over and over again. While the downloads aren't huge, it still seems wasteful to request the same files from the repo mirrors so many times... So why not just download the update once and then distribute it locally to each of my systems?
That's the purpose of a caching proxy.