I feel all of the options I've glanced at, or heard about, are various stages of questionable; Fluxer in specifics looks very "what if mastodon but discord" and I didn't see any real way on how it plans on going forward with handling age verification bs -- based on how they assessed Mississippi's law, I expect there will be "fun" if it turns out that more states pull as heavy-handed verification as Mississippi did (or if any of the 13 states already called out in Fluxer's blog posts for their laws get more restrictive interpretations) because that'd sunder more users from interacting with us at all.
Also, it still hasn't had a 1.0 release yet, so it's very much a beta platform doing beta platform/client things... and they're trying to push people to using their testing client, it looks like, for reporting bugs -- the v2 announcement in June calls out using git for bug reporting and there's a pinned "issue" on git made the next month by the head going "no no, use our Canary client and report bugs there", which makes me go -.- because why tell everyone "hey, we have a git, report bugs there!" if you're going to shortly after tell everyone to use a testing client to report bugs through instead...

Basically, fluxer's not "released" yet, it smells of trying to be the mastodon (or what bluesky wanted their thing to be -- an api and client you could use but not a platform itself) to Discord's twitter, and I'm squinty at it because it's gonna run into all the same problems discord's had and is gonna likely run into the same "starts getting advertisers and promotions and more pay-exclusive features and possibly running to 'going public' if the back end's funding doesn't stay enough to cover costs" like every other company trying to replace a garbage current thing runs into. Discord replaced Skype and when it got to Skype levels of user access ran into all the problems that lead to Skype being bought up and torn apart for pieces by Microsoft, except Discord's not found a big company (or gone public itself yet) to keep it afloat/tear it apart for pieces.

I think you are looking at good points! When looking into it, though, I think some of those are intended to be temporary. So, we may want to see how it changes over time. For this post, I am going to focus on the possible differences. That said, it is important to review what exists right now, and some of these are promises of the future made by the developer.

They mention that, right now, they are dealing with a spam wave which has caused the beta (called Canary) and release versions to get significantly out of sync. They call this out as an issue they are trying to fix as well as finalizing the API and self-hosting documentation. If what they say is true, they will probably accept regular-release bugs again. We shall see how that goes, as this notice is from 2026-06-15.

It can be self-hosted, so I expect that will be the best option for many communities. This relieves the major pressure that Skype, Discord, Twitter, etc. face in terms of degrading the product/service for money. If they want to, communities can simply host their own instances. If the developer, for whatever reason, deems it right to degrade the experience, people in the community can just fork off the better version of the code. These are key structural differences. Now, if they get federation working well, that is awesome, but we can use it without that. For example, the SCG forums here do not need to federate with other forums to be useful. Still, that would be a bonus.

I do agree with the "not released yet" caution. In terms of timing, it is very new. Something like XMPP, of course, is very mature. I think the ability to simply clone and set up SCG chat elsewhere is the most important thing to consider with this current test. In this context, I would be glad to play with an SCG-hosted instance or even with a Fluxor-hosted one for a bit.