(I’m the maintainer) I do use the messenger bridge and it works for me, without disconnection issues.

But what is dead may never die!

Nah, because it’s like no text for 30 secs, then “3 lines per second” (faster than you can read), then more or less synced, then again too slow/too fast. That teletext explanation someone else gave is more plausible. I cannot believe that the original are that bad, so my guess is that the way they’re ripped has issues.

Yes, it’s totally fantastic, and I’m not biased at all when I talk about it. xD

It does support a crazy amount of networks (it uses libpurple which is the lib of pidgin), unfortunately it lacks modern features and even groups don’t work that well. I actually started to work on slidge because I was fed up with spectrum2’s limitations and realised that spectrum2’s maintainer think, like many others, that XMPP is dead…

Oh that “teletext” thing I guess, I get it. I remember using subtitles from this source in France in the 90s, and it was never that off sync. I guess the way they’re ripped may make the offsyncedness worse.

Sounds like a dream. Try JIRA tickets and MS Word.

It’s excellent. Too bad there is no lidarr integration yet. I manually run beet import once a download is done, but I’d like to automate that at some point.

I use beets and soulseek but my ambitions are lower than yours.

I would suggest airvpn over mullvad as they allow port forwarding, which will make torrenting work better.

If transmission is running in a container, my latest blog post is actually about that: https://www.nicoco.fr/blog/2023/09/10/wireguard/

Here