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 @Hate9
RexSystem 1 vote originally by @Hate9 on GitHub
Yeah, to be clear, I do think stripping this functionality in the name of "not sounding too plural-coded" would be a stretch too far. I like having the feature be neutrally-named, because that makes it clear that it's available for whatever use-case you have that needs it, but removing functionality because it means integrating with a solution that has "plural" in the name is a serious stretch.