Hailey
haileyscommit#0352
Joined Oct 6, 2026 @haileyscommit on GitHub
- On Plural accessibility in voice and textUpdate for whoever's made it over here, thanks
hampusfor breaking email notifications: there is a draft PR for this now: https://github.com/fluxerapp/fluxer/pull/3236 It's still a work in progress, and there are a few rough edges still which is why it's a draft. But it's opened to help stir some conversation on the implementation details. - My WIP Personas implementation, which is aiming for a PR, now has a test server up, huge thanks to @chiaracoetzee: https://fluxer-personas.system32labs.com/ (source: https://github.com/haileyscommit/fluxer-contributions/tree/feat/personas) I am hoping to get a draft PR up soon to start getting maintainer feedback while I finish everything up. I just need to figure out how to get their attention to approve me for it.
- I do like the stack design, however it does tend to imply that it's multiple people talking (so, a feature where multiple personas can be used for a message could use these). Plus, it would also make the profile pictures smaller since they'd need to fit in the same space. I think both of these approaches are actually already implemented in Fluxer in a couple places: the left one is used for typing indicators when multiple people are typing, and the right is used for group DMs. (For a hypothetical multiple-personas-writing-one-message feature, I'd use the one on the right.)
- We've discussed the name quite a lot, and we chose not to call it "subprofiles" because it could be confused with community-specific profiles that way. Personas is kinda the next-best fit.
- 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)
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.- Hey @chiaracoetzee, this is awesome! Do you mind if I add you on Fluxer or Discord to collaborate a bit closer on this (in other words, can I send you git-bundles and ask stupid questions)? FWIW, I got this running in a local dev-container, and I might tackle a few of the missing and broken(-ish) things I've noticed, if that's okay with you.
Hello @haileyscommit @chiaracoetzee, I was wondering if either of you had started on making your own implementations intended for a PR or even just for your own client? I have also been considering the possibility of attempting to implement the persona's idea as well.
I've been basically waiting for Hampus's okay on it. Also PRs are locked now so I wouldn't be able to contribute it anyway. edited to clarify: I haven't personally, directly asked Hampus because they've said they don't want unsolicited DMs- As far as the message metadata for it goes, I think I'd store an ID (referencing the subprofile) and the "short name" of the persona/subprofile along with the message [I do have to look into how webhooks and existing messages handle authorship metadata and reflect that behavior], and use the short name for a fallback message signature for clients that don't support the feature (i.e. older clients). In light of the "multiple contributors" suggestion, the shortname used for a message would account for the "other contributors". Plus, the shortname thing means that even if the subprofile/persona is deleted, the name, at least, can remain. I'll add the profile picture link to the message metadata too if webhooks do it (possibly reuse the field it uses?). It's something to look into when I can actually start working on it (once the codebase stabilizes and PRs are opened; or if hampus greenlights me sooner somehow). The rest of the profile metadata will be offloaded and only requested when the profile itself is looked up (i.e. clicking the profile picture). edit: something I've also considered for the feature is allowing bots to set an endpoint clients can call to get subprofile information. In particular, this could be helpful to support bridges, so that full profile information can be lazy-loaded, and that it won't have to pretend that every user using the bridge is a bot. Bots could therefore have unlimited subprofiles, even on the main instance, because the main instance isn't hosting them. (Otherwise, bots can't have subprofiles at all; yes this is related to limits.) I do want to have a way for users to be able to bypass the limit by using a bot but I haven't figured out how that would work yet.
- I'm thinking about having a different metadata field for the "other" contributing personas/subprofiles, so that the first one can be looked up and used for the nickname/avatar, with an indicator that there are more somewhere (and if there are two, perhaps both names will be shown, if possible; this gets weird at 3 or more). This would be a later extension of the feature, though, so that the feature can exist first.
- My vision for this was that it would do two things to help with abuse:
- Show a subprofiles icon and the main profile picture on the message byline somewhere (in Compact mode, probably just the icon before the profile picture or name, similar to the bot tag).
- Show the main profile when you expand a subprofile in the chat, de-emphasized. That way the main profile can be identified when necessary.