RexSystem1 voteoriginally by @SaphireLattice on GitHub1 reply
From what I'm aware of, biggest pain point for PluralKit is that blocking people doesn't really work. So either a system for establishing "this bot message was caused by this used" could be helpful, or integrated multi-profile stuff.
Ideally any implementation should provide privacy control, as to not announce to the whole world that someone is plural, unless they use the feature in a given community. As well as allowing to limit which community can see which profile, which would help a lot for queer people in general, and others.
Though something to keep in mind is abuse potential, so making sure blocking and moderation tools are natively integrated is a good thing to do.
Considering the lack of subtlety with the current solutions, I don't think obfuscating the root user is a super high priority. We'd probably be better off making the feature useful and intuitive enough that that it's used for more use cases, preventing one from being the default go to assumption.
I could see it being useful for large community server staff using it to switch between chatting as a user and chatting as a staff member for example.
Thread
Comment by @SaphireLattice
Comment by @monty58