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 tempest:squll.fartcore.ai
tempest:squll.fartcore.ai 1 vote originally by @HellishBro on GitHub
implicit conversion can still be done. i do think "not sounding too plural-coded" is a valid concern though. while pluralkit and tupperbox are the de facto standards, i dont think that justifies an Import from PluralKit / Tupperbox button