docker-qBittorrentvpn VS Synapse

Looking at the Github issues for the container many seem to be in the same situation as you: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues There doesn't seem to be any activity from the developer either.

I'm trying to deploy the markusmcnugen/qbittorrentvpn image but I'm having issues.

- Docker container https://github.com/MarkusMcNugen/docker-qBittorrentvpn

In terms of downloading your "Linux ISO's" automatically, I highly recommend setting up a qbittorent/vpn combo docker container, such as this one. There's also an entire set of programs with docker containers youll see referred to as the "*arr" stack, which help to manage your collection, as well as automatically download your selected media as it becomes available. These are a bit trickier to set up, but once you have everything configured and running, they are a godsend.

why not use qbittorrentvpn. Auto kill switch, etc. https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/

Hey all, I'm pretty decent with normal networking on routers and switches, etc. but I know very VERY little about iptables. I am trying to fix an issue with a qBittorrent + VPN container. The VPN includes a script setting up a bunch of iptables rules to prevent leaks outside of the VPN. Script is located here: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/blob/focal/qbittorrent/iptables.sh

Been having issues with docker ever since I first tried it, I can't for the life of me access it on the supposedly open ports. Tried setting up this docker for usage in my home plex server with arr services.

I went with the qbittorrentvpn container.

So here's the situation. I have a seedbox at home. It is currently running this docker image: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Which runs qBittorrent and OpenVPN. It's set up so that all of the torrenting traffic goes through the VPN while the rest of my seedbox can be used for other things without having to worry about the VPN. I access this seedbox using the WebUI, which works fine whenever I'm on the local network.

Have Sonarr, Radarr, Sabnzbd, qBittorrent/VPN (NordVPN just for qBittorrent, not on Usenet connections) running in containers on the NAS using Docker Compose. Had OMBI also connected, but has been troublesome as of late for me. Newshosting as my usenet provider, NZBGeek for usenet indexing, Rargb and Nyaa for torrents. Just joined a few private trackers, but those are manually managed and seeding day and night.

What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.

Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).

If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.

some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...

Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.

This is honestly really disappointing behaviour from a platform owner.

[0]: https://github.com/matrix-org/synapse/issues/14481

> That doesn't make this situation any less bad to the rest of the community.

How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.

You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.

And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.

The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.

[0]: https://github.com/matrix-org/synapse/graphs/contributors