docker-handbrake VS The Lounge

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.

IRC as a protocol is indeed incredibly simple and easy to get started with. Years ago did discover this when I was able to make [this atrocity](https://github.com/creesch/discordIRCd) bridging IRC and discord where for IRC I effectively did a simple server implementation.

There is a caveat, though. Like many older protocols (ftp) there is a lot that was not initially written down or left up to clients and server implementations. This, does lead to a lot of edge cases you need to be aware of once you want to actually support a wider user group.

Also, as this is apparently is still a discussion. IRC is not simple from a modern user UX perception. Registration can be complex and confusing, though hidden a bit through clients. Managing channels with various flags is a whole other thing. Then there is also the fact that these days people are no longer used to the fact that they can't see messages from periods where they were not connected. Of course, the latter can be easily handled by a BNC or fancy clients like https://thelounge.chat . But, that is only easy for technically inclined folks.

> It’s 2024, people aren’t going to go out of their way to setup “bouncers” to keep up with conversation that happens when they’re not online or leave their computer running 24/7.

You can just set up something like The Lounge [0].

[0] https://thelounge.chat/

Excellent idea! You'll have a mature, open standard protocol under the hood, with no vendor lock-in, excellent extensibility, and great modern frontends like The Lounge (https://thelounge.chat/) or Convos (https://convos.chat/) to choose from (and you can choose).

For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.

Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.

[1] - https://github.com/thelounge

[2] - https://thelounge.chat/

[3] - https://github.com/convos-chat/convos/

[4] - https://convos.chat/

[5] - https://www.mumble.info/

[6] - https://github.com/umurmur/umurmur/wiki/Configuration

As another self-hosted solution, I quite like TheLounge (https://thelounge.chat)

TheLounge (https://github.com/thelounge/thelounge) - web IRC client that I set to listen on my vpn/mesh. Works great on desktop and mobile, and supports push notifications.