Plural accessibility in voice and text

(#947) Feature Under consideration accessibility profiles

Thread

Comment by @SaphireLattice
RexSystem 1 vote originally by @SaphireLattice on GitHub 1 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.
Comment by @monty58
RexSystem 1 vote originally by @monty58 on GitHub
Yeah, like I said, make it common enough to not be weird to see, and make them not provided my the server unless you request a specific UUID for the proxy. Sure theoretically someone could brute force find it to pull it, or share the ID around for other people to pull it, but someone putting the resources in to do that is already harrassment, and this is not a high damage thing for them to be doing.