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 @SaphireLattice
RexSystem 1 vote originally by @SaphireLattice on GitHub
Oh I meant restricting access to proxies, not the root account. That should be overall always visible. It's the existing of any proxies at all, and access to the list of them, that should have privacy controls