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

Top is really versatile, but I still love my btop.

I’m getting an HTTP 522 from that link. What’s Polyproto?

Also, is there a reason you’re not considering Matrix?

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. ✅

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.

Watching this company slowly circle the drain has been a pretty sad saga.

In that case, why self-host? A cloud-based solution would accomplish this very easily.

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.

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.

There’s no excuse for this crap. Even if they insist on scraping every FOSS repo, there needs to be some logic to it (caches, diffs, longer intervals). These AI scrapers are so poorly thought out they are indistinguishable from DOS attacks.

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.

Personally, I use OneDev and it definitely has

• CI/CD
• runners
• issues
• project management
• releases management (packages)

I’m not sure about wikis or third-party plugins.

If you’ve never tried GitHub alternatives, you’ll be surprised by how good they are (I definitely was). Many of them match the feature set of GitHub and some even surpass it.

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.