Hey #mastodon !

With #discord doing its age verification thing, where are your communities migrating?

#matrix ? #discourse ? Anywhere else?

@alxd We're evaluating Matrix and IRC atm.

Matrix has all the bells and whistles, but it's also quite resource-hungry, and tedious to maintain. Federation for smaller servers is likely not an option - making it rather unwieldy, when many clients don't support multiple homeservers.

IRCv3 has some nice features, like message history and replies, but also major friction points like poor support for uploading images via the client.

At least our data will be our own, and we can use it how WE want.

@CFDS @alxd As Matrix rooms and spaces are not bound to a single server by design, you may also consider finding some trustworthy federated Matrix-instances and recommend them to your users. The dependency to a single server is much weaker, so maybe self-hosting is not even necessary.
@hexmasteen @alxd to my undestanding, self-hosted server admins are reluctant to federating, because connecting to a mega-instance can quickly swamp the server's disk, RAM and CPU. One could say Matrix is geared towards mega-instances, because a situation where *everyone* self-hosted their own federated instance could make the resource usage problem even worse. At least that's how it was explained to me.
@CFDS @alxd Your server will hold a copy of all rooms, that any of your users is joining. It is not about connecting to a big instance, but joining big rooms (which is what the config I linked before prevents).
@hexmasteen @alxd I only saw your link to a discussion of multiple account support. If you have configuration tips, I'd be interested in seeing them! :)
Configuration Manual - Synapse

@hexmasteen Thank you! The definition for room "complexity" is... interesting! 🤔