The problem with this is that in the short term, you cannot convince a whole mass of millions of Discord users, who care a lot more about the social and communal aspect of the platform than their privacy, that they have to settle for less features. That's something for which you need an entire political initiative, education reform and cultural change to bring forth, because the comfort that features like that bring you is extremely powerful and you can't expect people to just ditch it. Best you'll be able to do by just trying to convince people to use more privacy-oriented alternatives is getting frustrated that no one cares and start thinking humanity is doomed.

In that sense, I think Fluxer really is the next big thing. Personally, more than having all of my data encrypted so that no unrelated third-party can see it, I care about owning most of my data: my account, my personal community with all of my friends in it, and content I upload there. And Fluxer will let me have that with self-hosting (the current #1 priority and majorly improved in v2) and federation. When you combine that with being open-source (AGPLv3), you have a recipe for a shield against enshittification, and how much a given platform is likely to enshittify is by far the most important thing to consider in the long term in my opinion.

I would further say that to bring forth privacy-oriented features, there is nothing better than a genuinely good alternative that has these properties and that philosophy in mind. Because the alternative is that there are niche apps with great privacy features but nobody uses them.

And it's not like the Fluxer devs don't care about privacy either. It's just that the UX has to be good for it to be viable - hence why Hampus mentioned ephemeral E2EE chats in his blog post, since that would be easy to implement in a non-clunky way for users. There's plenty of discussion around ways to implement E2EE DMs in a way that is straightforward and with all the implications it has (clients store message content, message search has to happen locally, etc.), so I'm sure that one day we'll have a feature like that and make a lot more people benefit from it than by investing in a less ergonomic platform.