> If you think running a Matrix server is difficult, you are probably not the intended audience: running an IRC server, an email server, or some other server, is mostly similarly difficult.
Running an IRC server is absolutely not as difficult as running a Matrix server.
There is no state, so you can literally build a tiny Docker image with the config baked in, run it on a VM with the specs of a cheap computer from the 1990s, and then forget about it for years. If it gets hacked (which I think isn't super likely as it's a small codebase that's been out there for decades), you build a new image with a more recent version of ircd.
APKMirror has it, and it can be installed from there...
...but then I get "Location not supported" when I start it. Helpfully suggesting I use Google Assistant instead.
My main reason for trying Gemini is that I hope that it makes fewer errors than GAss, and be more powerful too. Operating Assistant's voice controls in the car might be more distracting than just typing. And that's just for reminders and Spotify playlists. Anything more powerful is completely impossible.
Apart from the 51nb stuff from China (https://www.xyte.ch/mods/x210-x2100/ and the like), the ThinkPad 25 is the closest official thing, but it's over 6 years old now (released in October 2017, but mine's still going strong and I haven't even replaced the batteries yet).
> People still connect their Apple computers to low-DPI monitors all the time.
They do, but the fonts are visibly blurry on those, as they did indeed remove the subpixel antialiasing. Thankfully, the Gtk4 developers removed it as well, so Linux (or at least the GNOME desktop) will soon look like crap as well.
> If I could support artists directly, I would. But I can't, and I refuse to support predatory labels, so I don't. I do feel a little bad about it, but options are limited.
I've had artists send me mp3 in the morning after I gave them cash at a concert the night before. :-)
> 1. … You'll need some rebase-fu to handle that, and the pain is significant if the chain is long.
`git rebase --update-refs` on the last branch will handle updating of all the intermediate branches in the stack, you just need to force-push them all at the end.
It does help with 2. as well, but you will indeed need to manually update the target branch of a single PR on GitHub.
> So you need rebase-fu to fix, and it’s per-stacked-branch.
Note that `git rebase --update-refs` lets you just rebase the last branch and the entire stack gets updated. You just need to know which branches to forcepush.
Running an IRC server is absolutely not as difficult as running a Matrix server.
There is no state, so you can literally build a tiny Docker image with the config baked in, run it on a VM with the specs of a cheap computer from the 1990s, and then forget about it for years. If it gets hacked (which I think isn't super likely as it's a small codebase that's been out there for decades), you build a new image with a more recent version of ircd.