From what I understand the communication transport is encrypted so it’s designed to be secure.

The problem with this however is the sharing of the key. To be truly secure you’d need to share the key securely (i.e. in person), and explicitly trust everyone in that group not to leak the key, so it depends on which group you join and their opsec.

This is all based on my rudimentary understanding though. I am very interested in Meshtastic but UK law is quite restrictive about encrypted radio communication.

I used Lutris for anything Windows related that needs installers, etc. You can run that on pretty much anything.

As far as distros go it depends on how hands off you want it to be. If you want a set it and forget it distro I’d go with Fedora or Ubuntu.

If you want something more bleeding edge and customisable I’d go with EndeavourOS, which is basically Arch on rails.

I like the concept, but personally I see the decentralised nature of the Fediverse as a benefit rather than a hindrance, and moving all identity functionality to a centralised system would create more problems than it solves.

Suddenly you’ll have a single point of failure for the entire Fediverse. A very appetising target for hackers and DDOS attacks.

An alternative that’s in the spirit of your idea would be to allow for auth delegation, i.e. if you sign in with an Activitypub ID rather than a plain username, redirect to that instance to sign in then redirect back to the instance you started from, auth token in hand.

The nice thing about this approach is it’s basically just OAuth 2. It’s familiar, simple to implement and built in to a lot of web frameworks already. The only extra step would be advertising the server’s auth URL via the nodeinfo endpoint, which is fairly trivial to do.

I used to have an hour of Internet a week as a kid. I’m sure it cost a lot paying per minute.