https://git.feneas.org/feneas/fediverse/-/wikis/watchlist-fo...
This is the wide assortment of applications that speak the same common protocol that Mastodon does, as part of an interoperable social cloud. There's a Cambrian explosion of diversity in this space. Let's see more content management systems adopting this system for self-sufficient publication.
The idea of building a local community that you have to have an account and associated identity on a specific server to access is the kind of mal-aligned incentive that tends to cause federated systems to become de-facto centralized silos and, eventually, return to the status quo of a controlling oligopoly :(.
An architectural feature of a federated system is that people congregate on servers together for whatever reasons they have. Communities are an emergent part of this architecture whether we like it or not, and this can be used to create a positive user experience that you cannot truly get on centralized services. What we wind up with is a network of communities that interact with one another, not as some people envision a network of superfluous servers that humans use simply to interact with one another, and this is unavoidable in a federated system like this. If we do want a network where the servers are meaningless to the social interaction it has to be fully peer to peer.
There's also pleroma, which I've run and is pretty great and low on resource requirements. And there are tons of other social UX paradigms like link aggregators and even Peertube which is a tube site server on the same network as mastodon using the same ActivityPub protocol.
I'd love to see people implement novel types of social sites besides functional clones of existing social media, there are some significant architectural and UX differences in a distributed, federated social architecture that can be leveraged to great effect.