docker-handbrake VS Synapse

Handbrake (https://github.com/jlesage/docker-handbrake) - Similar to QT bittorrent, nice to have a spot where I can dump my video files and it has tools to monitor new files dropped in and custom formats.

I would highly suggest that you use https://github.com/jlesage/docker-handbrake/blob/master/README.md

Do you use docker? You could use the ripper container and use handbrake container. You’d set the output directory of ripper to be the handbrake input directory. Just put the disk in the drive you have setup and ripper will do it’s thing. After it’s done handbrake will detect a movie and encode it using your settings.

Very new to docker - although quite techy. I am guessing I missed permissions or something somewhere. I have set up Handbrake https://github.com/jlesage/docker-handbrake within Docker following this guide: https://www.youtube.com/watch?v=E6HgHsxdWIo I can access it via port5800, however when I go to add a file/folder the pop up goes to "storage" if I go to "Other Locations" I can see the folder I specified during set up, but then I get "Cannot Read contents of GoProToSort" "Error opening directory. Permission Denied"

But when jlesage/handbrake launches, even if you manually specify uid:gid 1000:1000, there are permission errors:

It sounds like you missed the x11vnc part of this. You connect into the container using vnc, not x11. If you want to see a working example of a gui app running successfully in docker, check out https://github.com/jlesage/docker-handbrake

There isn't a magic setting or anything, and honestly, I don't recommend tdarr, mostly because you can do all the same stuff it does with a bash script and jlesage's handbrake container (or just handbrake outright).

My NAS/home server is a NON-COREBOOT HPE-Proliant-Gen10 microserver I have some details here. 24G ECC, 24TB RAIDZ-2. I am running docker containers for Makemkv, Handbrake, Filebot, Jellyfin, Gitea, TinyTinyRSS, Bitwarden, Samba (readonly for Kodi running on an Nvidia Sheild TV), Restic backup, Nextcloud, PFELK (router stats) and a weather forecast app I run on an old Nook in a picture frame. It isn't fast but it doesn't need to be for my needs.

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