Plural accessibility in voice and text

(#947) Feature Open: 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
Comment by @Enovale
RexSystem 1 vote originally by @Enovale on GitHub
Having its own export format is one thing (in case other chat apps copy fluxers system) but I really cannot see how allowing for the native import of PluralKit systems betrays any sense of inclusion to anyone else. It's not language, its a feature. And as far as I'm aware PluralKit and TupperBox is THE defacto implementation of this feature on discord, so supporting input from either would be a large boon in accessibility. Stripping functionality and requiring users to separately "convert" their import data for the sake of.. not sounding too plural-coded? Genuinely sounds bigoted.