Jellyfin has Watch Groups that my (tech-challenged) family uses regularly without my help.
I just added IPTV to my setup, so I haven't tested if they work together. I can't see why they wouldn't. Worse case, have then tune into the same channel as you, it should sync up almost perfectly on its own.
I recommend adding hostname: app-name lines for each container then you can just use the hostname and the native port (even if you don't pass it through with a port: line).
It's super useful if you want to expose any apps with a reverse proxy like Caddy. That way the ONLY way to access an apps web interface is via the reverse proxy. Then look at filter rules to deny access unless the client has a LAN IP.
Poof, you've got SSL and custom subdomains for all your apps, but still only on your LAN or personal VPN (like Wireguard or Tailscale).
I've been using Caddy instead of nginx for years now. As long as your port forwarding is already setup, it'll pull TLS certs for every domain in the config automatically and keep it up-to-date forever.
It's also super easy to use as a reverse proxy, so you can run one caddy server for all your sites on the same machine pretty easily.
I just checked and you're right! I looked into Briar a while ago and ignored it because I couldn't run the Briar-Mailbox program on Linux.
Signal is great, but it was unclear if I would be able to self-host my own Signal server if I wanted to support the public network and provide redundancy to my local LAN and connected networks.
Every time I look at Matrix it looks really cool and sounds great. But each time I try to setup a client or actually use it, nothing works, apps crash, and I can't actually use the dang thing. I tried setting up my own server, even tried using a public server with the Element web-app and still nothing worked, couldn't join rooms, etc.
Love the idea, haven't seen a decent implementation yet. Honestly kinda wish there was PGP for sms or something like that. I couldn't care less if the transport is insecure, as long as I can trust that only the intended recipient and myself can read/modify my messages.
Thank you, I didn't see that thread.
Is there any reason these browsers would be more functional than regular Firefox with Sideberry or the Tree Style Tabs extensions?
I use Sideberry at work and at home. Between the containers, folder sorting, tab sleeping, and snapshots, I haven't found another browser configuration that's as flexible and functional.
Not to mention it works with any release or flavor of Firefox. So I don't have to worry about weird issues with non-standard browsers.
*Bonus points if you take the 10 minutes to setup a stylesheet to hide the default horizontal tabs.
They have a platform and process for selling digital access to audiobooks and ebooks. Selling access to that type of content in an way that circumvents those DRM requirements is against their Terms of Service.
It's unclear to me how this project does anything to protect the identity of users or who is talking to whom. It's nice to know my messages can't be read, but if my ISP can see who I'm talking to and how often it's not doing much.
Also how to clients find one another? Tor and i2p sites are notoriously require friends or public wikis to share the addresses.
I recommend Restic. It's fast, it supports snapshots and compression, written in Go so it's much quicker than most other solutions I've tested. It also supports multiple different backends for transporting and storing the files so you can use one you've already got or use the restic-server (which is pretty easy to setup).
Make sure the Allowed-IPs is as small a subnet as possible. Your device will only route traffic over your VPN that has a destination IP in that subnet.
That way you're only tunneling the traffic that needs to go over it. Everything else will go out the normal route.
Having your device package up and encrypt every packet takes some overhead and will inherently lower your bandwidth throughput, so it's worth minimizing the number of packets that have to go through that process.
Yeah, you'll need to spin up a Jellyfin server. It's really easy in docker though, and it shouldn't need a machine too powerful. I've heard of people running it on an rPi4 or old laptops.