- 1 Post
- 7 Comments
festus@lemmy.cato
Selfhosted@lemmy.world•Plex’s crackdown on free remote streaming access starts this week - Ars TechnicaEnglish
191·1 year agoJellyfin can’t go closed source as it’s a fork of Emby from before it was closed source, licensed under the GPL. They don’t own that code so they can’t change that license, thus the whole project is GPL. In addition, Jellyfin isn’t being developed by just one company (it’s all volunteers), so every new contribution is also GPL licensed, owned by each contributor. The only way Jellyfin could go closed source would be to cut out the Emby backend and for every single contributor ever to agree to change the license, or have their code cut out. In short it’s not happening, and if somehow it did the project would just get forked regardless for everyone to switch to (the community did it once already!).
festus@lemmy.cato
Selfhosted@lemmy.world•Friendly reminder that Tailscale is VC-funded and driving towards IPOEnglish
6·1 year agoYour approach won’t work if you’re behind carrier grade NAT or you can’t open ports. My landlord provides my internet so I use tailscale (with headscale on my long distance vps) to connect everything and it works great. It uses LAN when I’m home, and NAT punches when I’m elsewhere.
Entirely depends on who’s publishing the image. Many projects publish their own images, in which case you’re running their code regardless.
Yes but there are ways to protect against that. For instance you can configure Tailscale clients to only trust nodes that have been signed by trusted nodes, or something like that.
I started self-hosting a bit prior to when Docker took off, and getting multiple services running was much harder. Service A wants a certain version of PHP installed with certain plugins while Service B wants a different version. You’d follow a tutorial for installing Service C and desperately hope that it wouldn’t somehow break Service A or B. You installed Service D for a bit despite all the installation pain and now want to uninstall it - I hope you tracked exactly what config changes you made throughout the system so you can undo it.
Docker fixed all of this by making each service independent through containers which made self-hosting 10x easier. I’d also add that I love how easy it is to transfer my setup to a new server - I keep all of my container volumes in a specific directory and my docker-compose files in another and that’s all I need to backup / transfer. Without Docker you’d have to specifically handle each & every configuration file and database location, and if you later upgrade to a newer version of the OS or a different distro you’d have to handle possible conflicts between your versions and what the distro expects.
FYI I’ve had a really good experience with using Headscale for a true open-source Tailscale experience. It helps that the Tailscale clients work with it too and that Tailscale (very unofficially) help support it.

What does it mean for a project to deserve the [AI] tag? This matters, because you may have a lot of projects where a developer may think “no” and someone else thinks “yes”. Some examples from my day job:
In these examples the developer carefully reviews the AI’s output, which I think distinguishes it from vibe-coded slop, which at least is what I want to ignore.
It’s also worth noting that an open-source project may receive and incorporate a well-written contribution where the human developer used AI carefully like this. Unless they disclosed that they used AI, it may be unknowable to the project maintainers whether their project is [AI] or not, depending on how you define it. What tag should these projects use?