Plural accessibility in voice and text

Hi!! Any instructions for helping with testing? I'd love to put the work into getting this into Fluxer proper but i'm rather inexperienced with actual development testing & etc. Assuming i'll need to build it but i don't know how to do that from my own knowledge, nor what would be required after that point. Sorry for the silly questions, but i hope i can help contribute in the end <3

Looks pretty good from the screenshot! Just a few things about design:

• I'd ensure that the Import from PluralKit and Add Subprofile buttons look like the rest of the buttons on the platform; right now the icon is above the text instead of on its left. The rounding is also off. Looking at your PluralKit modal commit, it looks like you used plain HTML <button>s, it would be better to use Fluxer's own Button (fluxer_app/src/features/ui/button/Button.tsx) component instead. Same for the other buttons if you did it that way there too.
• I'd slightly increase the width of the subprofile switching modal in the second screen so that Last Used doesn't span two lines of text.

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.

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.

Hi!! Any instructions for helping with testing?

@bunnikyuube If you just want to try it you can hop on my development/testing instance at https://chat-dev.hypersystem.xyz/ and try out there. If you want to run your own local instance you can use Fluxer's turnkey Dev Container setup:

• Install Docker Desktop (or Docker Engine on Linux)
• Install Visual Studio Code (or Cursor) with the Dev Containers extension (ms-vscode-remote.remote-containers)

1. Clone the fork and branch and open in VS Code:

   git clone -b features/subprofiles https://github.com/chiaracoetzee/fluxer-subprofiles.git
   cd fluxer-subprofiles
   code .
   

2. Reopen in Container:

• A popup will appear in the bottom-right corner asking to "Reopen in Container". Click it (or press Ctrl+Shift+P, type "Dev Containers: Reopen in Container").
• Docker will build the container and spin up everything, this will take some time.

3. Inside the VS Code integrated terminal, run:

   cargo run -p fluxer-dev -- dev
   

4. Open http://localhost:8088/

If you want to integrate it with your existing local homeserver I'd need to know more about your setup and config.

Something I added to this today: Screenshot From 2026-09-08 22-42-18 (yeah that test account doesn't have a profile picture cause i didn't bother lol)

We decided for now to settle on the "Personas" language (because it's widely-understood and to avoid the issue where "subprofiles" may be confused with server profiles). This isn't the most popular term in the plural community (they prefer "identities") but I think it's clearer to a general audience and we can emphasize in the messaging that this isn't just for fictional roleplay. Also decided to forego the "proxy" term which only really made sense in the historical PluralKit context which proxied messages through a bot. So instead of "proxy tag" we use "persona tag" or just "tag", and instead of "autoproxy" we use "Active Persona Mode". Can revisit terminology as needed. Also did a bunch of style fix-ups, using proper Fluxer Button components, avoiding Discord CSS tags and colors, gave "Last Used" a nowrap, tested in light theme. And haileyscommit did the feature above to show succinctly who a persona belongs to on each message, as well as supporting deep links to persona settings, a slash command for latch control, and a visibility toggle for the persona composer adornment. image image image

I would suggest not include an Import from PluralKit button. "System Tag" could be revamped. These two features could make the Persona feature very plural-coded, which might not be ideal. IMHO maintaining language neutrality here is crucial.

Language neutrality is one thing, but importing from PluralKit is just a useful functionality. What's wrong with having it?

idk. it reads too plural-coded (as pluralkit is mostly a plural bot) and also it replies on a 3rd party that most people havent even heard of. too niche of an input source vs the supposedly "many-usecase" persona system

PluralKit is used by a lot of people for roleplay and other non-plural-specific use-cases, so I don't think it's a bad thing to have an import for it. That said, as an alternative, we could instead have our own import/export system and then build a third-party pluralkit-export-to-persona-export converter?

yes, that's what i'm thinking. instead of relying on pluralkit format (which is tailored to mainly systems) we can have a custom import/export format that fits the persona model

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.

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

also, this should probably be moved to its own discussion post? now that an implementation exists, i think a new discussion post with the category of "development" will facilitate this discussion better. @chiaracoetzee

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.

@HellishBro I created a development post at https://github.com/orgs/fluxerapp/discussions/2635 and we can have further discussion there!

Regarding the comments above: I agree that the System Tag language (and especially having a separate System Tag on each persona) is not ideal for the more neutral language I'm going for. I'm still workshopping this. I'm also amenable to changing the "Import from PluralKit" button to just "Import" and it will automatically recognize any number of supported import formats including PluralKit json and its own export format, I think that's a good idea.