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 @Beethoven-n
RexSystem 1 vote originally by @Beethoven-n on GitHub OP
doing it exactly as pluralkit does is a bit of a naive approach, for a few reasons:
  • again, blocking doesn't work
  • users are not required to display their account name when proxying
  • because messages are sent twice (once through the account, once through the proxy,) pings are sent twice, even everyone pings