Plural accessibility in voice and text

(#947) Feature Under consideration accessibility profiles

Thread

Comment by @chiaracoetzee
RexSystem 1 vote edited originally by @chiaracoetzee on GitHub 1 reply
Per my comment above I have a prototype of this feature up at https://github.com/chiaracoetzee/fluxer-subprofiles/tree/features/subprofiles based on @haileyscommit's design and it's working well on our home server. It's web/desktop client only not mobile right now. Would need a lot more prep before submitting a proper PR. Supports both GUI subprofile selection and PluralKit-style prefixes, and can import a system from a PluralKit JSON export dump. Tested with a large imported system with 60+ members. Some screenshots below for reference. image image image
  • 647626661-6f5bb49a-b736-4409-ba78-86c87d403275.png

    647626661-6f5bb49a-b736-4409-ba78-86c87d403275.png

    622×655 | 73 kB

  • 647626096-1b76487e-8309-4cd0-8808-417eb24618e7.png

    647626096-1b76487e-8309-4cd0-8808-417eb24618e7.png

    598×745 | 81 kB

  • 647626981-ffec720b-2305-4199-86f4-52f0afe3216d.png

    647626981-ffec720b-2305-4199-86f4-52f0afe3216d.png

    1590×1144 | 181 kB

Comment by @haileyscommit
RexSystem 1 vote originally by @haileyscommit on GitHub
Also, I think the vocabulary is a bit inconsistent. In one place we're talking abut "subprofiles", in another it's "personas", and in another it's "subprofiles & personas". I think it should just be "subprofiles", it's the most neutral word that corresponds to the broadest application of this feature imo.
I'd argue that "personas" would be better to settle on because it's a more distinct name, whereas "subprofiles" could be misinterpreted as server-specific profiles.