Yeah lmao, I have come here occasionally over the years. Don't post too much tho

The error shown in the video is the one that means that they just... didn't set up video calling? It requires more setup than just the text chat for technical reasons that no service can escape.

Star dragons, or whatever they're called, are... uh... mildly bad. Also important to the pre-human lore iirc

I'd recommend joining https://matrix.to/#/#continuwuity:continuwuity.org for support

I'm talking about https://github.com/element-hq/matrix-authentication-service which is the only implementation of https://github.com/matrix-org/matrix-doc/pull/3861 right now.

Yeah, saml is a nightmare! Never make me touch saml, please 🥺

In Continuwuity, the first user created is the admin user - so creating a user using either a registration token, or an admin command via --exec, the emergency password, the interactive console, etc would work.

This is like the opposite of what you want to do for complex software - don't add more abstraction, or you won't know what to do when stuff goes wrong!

I feel like people didn't make this much fuss about micro python lol

My personal selfhosting repo is just about 2 years old with 750 commits now, and probably more than 60 containers running. It's not because of one great effort or design or anything, just setting up a service or two when I find it interesting every few weeks, and trying to make all my setup consistent. Almost everything is deployed as a container run by Podman quadlets, files mounted in /var/opt, config etc copied into place by an ansible script. But not everything, sometimes getting it working was easier without the sensible or I needed to do some funny networking.

TLDR: Coming back again later, and making that easier.

Yes? June's personal stuff isn't your business, and she left open source because of people like you

Continuwuity.org has reasonable documentation, and you can (and should) disable signups or require a token to sign up.

That page seemed outdated, but: From further down that page:

The recommended strategy is to share the keys automatically only to verified devices of the same user

This is the same situation where the key backup is accessible - which is not described on that page, but it's a key store of all the megolm keys. This is what is now generally used instead of that as it doesn't require devices to be online and allows recovering keys if all devices are lost.

A few days late, but I have a pretty similar usecase to you on https://forgejo.ellis.link/. My solution is go-away, https://git.gammaspectra.live/git/go-away, which just sits as a reverse proxy in between traefik and Forgejo. I haven't enabled fancy stuff like TLS fingerprinting. It's been effective enough at killing the bots downloading archives and DDoSing the server from residential IPs. My config is based on the example Forgejo config, but with a few tweaks. Too long to post here, though, so message me if you need access