Kairos

Cron job and termux-notify

I block minuses too

No

Literally

1. Back up instance config and data
2. Swap out ELF for same or newer Forgejo version

Edit: this seems to have changed recently :/

Oh it’s the heat? I thought it was vibration (I actually don’t know).

Just in case you dont know most drives aren’t rated for this many in one case.

There’s also issues with the state disagreement / resolution algorithms across federation.

Has this been solved? Maybe it’s also due to database corruption, where some state is forgotten across the federation, and thus the algorithm breaks down?

It can baloon as it scales up. Matrix.org (homeserver) has had at least one DB corruption and that’s with their proprietary Rust bindings for Synapse. Small communities, especially ones that share rooms between them, should be fine on most systems. Make regular backups of the DB.

Well, pretty much all OEMs are months behind security patches as well. Google actually withholds the patches/exploit source code for months because of it. Graphene OS has a separate channel for builds with these patches that don’t have source code released.

The turn server must be able to access other nodes on the Internet and vice versa unless operating exclusively within your local matrix server.

Debian is stable. It works well, but the software in its apt/deb repo are relatively outdated compared to what might be in Fedora.

For a domain you own, you can use Let’s Encrypt. If it’s a custom TLD (.lan, etc.) then you need to do self-signed. Most systems can install certificates.

The answer is literally in your screenshot.

I don’t know maybe 2023?

And the account had to have a Plex pass at the time.

Only old accounts are grandfathered into this for sharing libraries to other plex accounts.

Yeah probably.

Even big Minecraft servers are just many servers with load ballancers. The game has server redirects built in for this reason.

Actually I can provide a little more detail. Check out how Matrix handles event graph resolution/desync. It’s why messages sometimes come in out of order. This is a fundamental problem with decentralization: authority breakdown. The homesever in Matrix is considered the authority for the clients, but within the Federation itself there is no true authoritative party or event history. If a server goes off federation for a while, a room will split, and once it re-federates it and other servers will have different event graphs, assuming something happened in those rooms in the meantime for both the defederated server and federated server(s).

Basically: videogames assume that within a certain amount of latency the server’s state is permanent and authoritative. Federation breakdowns even for 500ms can destroy a games running state.

The game has to be made for distributed servers. The game software expects that everything the server says is authorative, including for rollback. Multiple servers introduces an extra source of latency and it’s just so hard to deal with.

I don’t know too much about this.

Chat server is easy: Matrix (actually multiple servers but same effect)

Game server is very hard. The game has to be made for it or you have to be very good at network application engineering to hack it in.

This project runs on Tor. You are effectively hosting a Tor site.