No, you are right, Matrix is a protocol. Some of its major points are:

• It's decentralized (There are homeservers, but federation is built into the protocol. Think of this like email servers. There are many different servers out there, and they can talk to each other. Or not, depending of the configurations the server admins set.)
• It's a interoperable protocol, allowing users to communicate across different service providers and platforms. This is why Beeper used it as it's core.
• • Bridges allows taking posts from one service and posting it to another, and vice versa. For example, users from Discord, IRC, Telegram, etc can all talk between each other with little effort from whatever platform they choose. They don't need to be using a matrix server themselves, just someone who has set up a bridge with one in their spaces.
• • Puppeting allows users using a matrix homeserver & a bridge that supports puppeting to log in with their other service's account. For example, if you were to do this with Discord , you'd then be able to have all over your messages, including dms, bridge to your "matrix" account. You'd also be able respond via your account directly. That is, if you send a message to Discord from your matrix homeserver, it'll get posted via your Discord account and not the Discord bot used for the normal bridging stuff. NOTE: Puppeting is against Dscord's TOS, but is use in this example as most know what it is.
• End-to-end encryption is built heavily into the protocol. Not every space has to have it, but it's a core feature and enabled by default for DM's.
• It's an open source protocol

Personally, I feel there's still a few cons:

• Is is not polished.
• The new user onboarding needs work
• Some QOL things are missing. Thought this is more an issue with Element, the default reference client. They have a very shrill default notification sound and no way to easily change it. There's an open issue with a fair few users who understandable want to be able to change it easily.
• The spec is evolving still, and there's some things that haven't been figured out yet.

In saying that, I do still use Matrix and run a server myself. I think it's good, but needs some work still.

As to a NZ homeserver or space, I'm currently unaware of any sorry. And GoT felt like it was going of the rails before the last season >.<

Matrix does have some good documentation though, you'll find a lot of info on their site here: https://matrix.org

This does seem more like someone mixing sex and gender up.

For those who don't know, shift+F10 to bring up a command prompt when using a windows install image. Can do it when it starts asking you for stuff. I know the chkdsk tools and manage-bde (the bitlocker cli) are avaliable there at least.

Settings -> Default panel content

Haven't used it myself, but this looks like the setting for it.

Ahh, thanks for the info!

I've been out for a bit, what's wrong with them? Or is this being mixed up with microtransactions?

Something else to bear in mind, both sites have their own dark mode you can enable.

Dark reader doesn't currently treat subdomains differently from the base domain. So if you've disabled it for beehaw.org, it'll be disabled for old.beehaw.org.

There is a 5 year old issue on this...

https://github.com/darkreader/darkreader/issues/373

I'm not sure I really get the pull. It seems to just be a matrix server with bridges and custom clients

They do have their work open sorced which is nice, but this all kinda just looks like what matrix is on its own. I guess the only advantage I see is maybe making things a little easier for more casual folks, but it does cost to...

Glad it help!

Not sure what the Bitwarden TOTP app is, totp is build into the default clients.

I'll also confirm that 2fa with beehaw at least is working for me. Vaultwarden shouldn't make a difference, it's just the data host, your client is the one decoding and then generating the otp.

My advice, you shouldn't have to add anything. Copy the totp link from your lemmy instance and paste the entire link into the Authenticator Key field in the bitwarden entry. The link should start with otpauth://totp/. Don't remove anything from the link, it'll work as is.

If you're finding it's still not giving you the correct code, the only other thing that comes to mind is to make sure your device's time is synced and accurate. TOTP codes are time sensitive, and if the device's time is desynced, you will get incorrect codes generated.

Good luck.

Boat you say?

https://youtu.be/709ho4nH5QI