That video was… something…

Anyway I love Immich. It’s definitely been on a stable release for a bit, but I think they’re just trying to get the word out. A lot of people seem to think it’s still in alpha.

Personally, I’ve been running the same Immich server for years now, rolling all the way up to the current release and I’ve never had any data loss. I just had to read the patch notes and adjust my docker compose accordingly a couple times.

It’s well worth paying for that supporter badge, btw. I’ve easily gotten more than $100 value out of it.

If you go into self-hosting hating containers, you’re gonna have a bad time.

You’re, right, I misread the post.

At that point DNS is handled by whatever network you’re on. Since that not always under your control, hosting a private VPN (and setting DNS though that) is the way to go.

deleted by creator

deleted by creator

This seems like a cool project. I especially love the UI’s similarity to Discord, but it still has a long road ahead to be a viable chat platform IMO.

I’ve been periodically checking in with Revolt Stoat for about a year now, and personally, the two things that I’m waiting for are:

1. Voice chat - It seems like this is coming, but they had to clean up a bunch or tech debt first
2. Federation - Self-hosted chat is great, but not being able to talk to other servers is incredibly limiting for a social tool. AFAIK they’re not planning on implementing this. This is likely a deal-breaker for a lot of folks.

I’m currently running Matrix synapse, and while matrix is kinda a messy ecosystem, it’s really hard to compete with its maturity and adoption in the FOSS / Self-Hosted space.

Also, not super important, but this blog post reads like it’s AI generated.

Import our Postman library. ❌
Clone our curl repo. ✅

A house that needs the internet to function is not a “smart home”, it’s a “dependent home”.

A frustrating number of devices rely on cloud connectivity for astoundingly rudimentary tasks.

I was once at a friend’s house for a game night and it was really cold; everyone was under blankets. I asked to turn up the heat and they said, “The internet is down, so the heat doesn’t work.” 🤯

How could we tell you about an IP inside your own network? Look at the host using that IP and see what’s running on it.

I really hope this was just a joke.

If avoiding downtime is your number one priority and you’re willing to take on a lot of complexity to achieve it, then Kubernetes is probably the way to go. There are various chat platforms that can be distributed, but keeping a game server state synced between nodes isn’t an easy task. There’s a reason most multiplayer games are instanced.

I do find it a little odd that you’re so concerned about uptime with a casual gaming server, but to each their own.

You jest, but I’m currently running 13 containers on one of my Pi’s and using ~34% of the RAM.

IMO containers should be fairly small. If they’re too large, it’s probably time to look into breaking up that app into micro-services.

That’s how VMs were born.

I’ve seen this idea floated before a few times, and it’s a thought I’ve had before myself–some sort of self-hosted version of gify. AFAIK nothing exists as of writing, but I’ve seen this idea crop up enough times that maybe there’s a demand for this sort of thing.

Personally, I just have a well-organized meme folder that I sync between my client devices with syncthing, but something a little more integrated and easier to search might be fun.

Hm, I don’t know about that either. While scale is their primary purpose, another core tenant of containerization is reproducibility. For example

1. If you are developing any sort of software, containers are a great way to ensure that the environment of your builds remains consistent.
2. If you are frequently rebuilding a server/application for any reason, containers provide a good way to ensure everything is configured exactly as it was before, and when used with Git, changes are easy to track. There are also other tools that excel at this (like Ansible).

Do you host on more than one machine? Containerization / virtualization begins to shine most brightly when you need to scale / migrate across multiple servers. If you’re only running one server, I definitely see how bare metal is more straight-forward.

Plex isn’t perfect, but the open-source aspect of Jellyfin is holding the platform back. Fractured development across its third-party ecosystem prevents any clients from being as functional as apps like Plexamp while also creating hyper-focused support for popular platforms and leaving smaller platforms virtually unsupported.

This is a strange take. Being open source doesn’t cause unfocused development and platform prioritization issues. Those both happen to proprietary software, especially the latter.

These are more symptoms of it being a community project rather than developed by a company, but community FOSS projects can also be run very effectively. There are many examples of this.

A lot of FOSS development is done by the people who use it. So I suspect as more people move away from Plex, a subset of those users will help contribute to the aspects of Jellyfin they care about.

Jellyfin development is accelerating, while Plex’s enshittification is accelerating. The line is different for everyone, and one by one, I suspect Plex will cross them all.

If you already know NFS and it works for you, why change it? As long as you’re keeping it between Linux machines on the LAN, I see nothing wrong with NFS.

Understandable, I’m mostly just commenting on the demographic in this particular Lemmy topic.

I get that “just port it to Linux” is no easy undertaking, especially if multiplatform wasn’t part of the original architecture.