AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Features

Plural accessibility in voice and text

(#947) Feature Under consideration accessibility profiles
by RexSystem edited originally by @Beethoven-n on GitHub

Thread

View full discussion
Comment by @SaphireLattice
RexSystem 1 vote originally by @SaphireLattice on GitHub 5 replies
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.
Permalink
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
Permalink
Comment by @monty58
RexSystem 1 vote originally by @monty58 on GitHub
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.
Permalink
Comment by @monty58
RexSystem 1 vote originally by @monty58 on GitHub
As for visibility, presumably the root profile that's displayed would be the per-server profile, with the proxy profiles linking back to that and not being retrievable aside from when used in a chat. If each proxy has a randomized UUID that you have to know to request them, then anyone trying to request the details would have to already know it, and if someone's following you around trying to expose that, it would fall under the rules umbrella of someone following you around and harrasing you, which already have it's own solutions
Permalink
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
Permalink
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.
Permalink