It’s automatically handled by https://github.com/tubearchivist/tubearchivist-jf.
It works by identifying the videos downloaded by Tube Archivist and sending the info to Jellyfin. It hooks into the API of Jellyfin and adds the metadata.
i have no configuration files prepared but it’s not rocket science at all. It consists of:
Sorry to not be able to provide YAML or alike. But it’s not hard to configure.
As a archiver/data hoarder I use Tube Archivist that downloads videos from my subscriptions using sponsorblock to cut out ads. Then I use a script that tags the content and present them in Jellyfin with all info, sorted by channel and year.
This way I also have everything saved and no logging from YouTube of my viewing habits apart from what’s my subscriptions.
Not perfect, but close to it.
What’s your threat model?
Signal as a gold standard for encrypted messaging is based on many factors. Ease of use, UI/UX, protocol, platform support and so on.
Even though I’m a hard core FOSS person I’m also a realist. Sticking to a common platform is worth a lot. Bridging stuff with Matrix is cool but will not take off among most people.
Signal using Google blobs is a problem but let’s face it, the UI will be presented on a Google branded Android phone or a iOS device anyhow. Sure you can use GrapheneOS and Molly or you can switch to another app altogether but heck you’ll have no other to talk to then.
My biometric data, in this case my voice. Training an AI, tailored to my voice, out of my control, hosted as a cloud solution.
Of course there is an aspect of patient confidenciality too, but this battle is already lost. The data in the medical records is already hosted outside of my hospital.