Plural accessibility in voice and text
(#947) Feature Open: Under consideration accessibility profilesMerged posts
These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.
Report details
Problem
There has been notable demand for granular per-message profile management across Fluxer and Discord, built largely off tools like Tupperbox, Octocon and Pluralkit and their kin. As a plural system myself, i obviously benefit from the inclusion of features to accommodate for it. It's also perfectly common in roleplay communities and other areas like that. Additionally, the desire for more granular profile support and the ability to "present" in different ways was proven with per-server profiles when they became standard in Discord (and were, as such, added to this.) A lot of people benefit from this type of ability. I don't see any major reason not to add the additional flexibility. Except... Most people seem hesitant to support something like this due to the history of moderation issues and behavioural jank when interacting with third-party tools like Pluralkit. That's the part i wish to address, and why i've started a separate discussion to another one i had contributed to (https://feedback.fluxer.com/p/947).Proposed solution
Much like most of these implementations, the end goal is to provide a solution to allow for granular control over the presentation of one's profile on a per-message basis- to be able to send any given message, or multiple, using any of a set of different "identities", consisting of at most, an Avatar, a Display name, and- maybe- a profile description unique from the sender's basic profile. Unlike most implementations, working around the requirement for webhooks and the like, i want to directly address the human-friendliness issues, minimise the behavioural jank of third-party bot solutions, and solve the moderation-annoyance issues- something that should be little issue given the nature of native implementation. My hope is that addressing this from the jump might get some eyes on it that otherwise may have just skipped over it. Given the native implementation, i think most would agree the Author or user ID of the final message should not be different from the sender's original profile in any way. That's a result largely of the Webhook workaround, and largely the source of concerns regarding moderation with respect to Plural-accessible tools. In function, any given message sent under a different identity would be referencing a different set of metadata consisting of the things mentioned above- not unlike Server profiles. In addition, this fact should also mean that blocking users works exactly as normal. After all- changing your display name or avatar doesn't cancel out a block...obviously. In effect, the sudden receiving of messages from "people that werent part of a conversation before" or that have a bot tag attached to them, also causes some fair confusion in conversation with people unaware of the feature. My proposal for that is that anything sent under a separate identity would display the username- NOT display name- of the message author's basic profile, next to their display name in a smaller, faded font ie. the Time Sent marker.Notes (optional)
In addition to the faded username, it might be worth considering the following; If someone has sent messages in a server under one or more identity in addition to the basic profile, the username could perhaps be displayed above all their messages as per how i suggested. This would likely require some additional discussion, as it might potentially be a risk to systems that don't present in certain spaces, or might otherwise be considered un-friendly to the user utilising the feature. In addition, there's one other question begged, in my opinion, that no one seems to ask... and that's regarding Proxy tags. Proxy tags are a "part" of the message you send, that when sent, will signal the bot to proxy the message under the associated identity. Identity 1 is , for example,Id1:text and Identity 2 is "text", where text would be replaced with the message in question.
These have kind of become muscle memory for a lot of users, and i feel they should be replicated in some fashion. However, making them human-friendly and human-readable is a complicated matter that will require more discussion.
Consider that below :)
86 comments
Comment by Hailey
Comment by Hailey
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.Comment by Hampus
Comment by @arxari
Comment by @Beethoven-n
Comment by @ashenyuki
Comment by @bunnikyuube
Comment by @lucastheguyy
Comment by @Beethoven-n
Comment by @Perisys1312
Comment by @AstralPhnx
Comment by @monty58
- UI for swapping profiles
- a server setting to enable/disable it
- some sort of tag beside a profile name to make it clear what account is communicating. Possibly toggleable client side
- consideration for some sort of Plutonium limitation
- how best to include a profile selection in a message.
I'm sure I'll remember more later. I figure we can get a design doc sketched out, then once the refactor is public, and things have calmed down a little, we can pitch the idea to Hampus, and if he says yes to any of it, then start working on actually building itComment by @Beethoven-n
Comment by @monty58
Comment by @Beethoven-n
Comment by @Perisys1312
Comment by @SaphireLattice
Comment by @Beethoven-n
Comment by @monty58
Comment by @monty58
Comment by @SaphireLattice
Comment by @monty58
Comment by @AmilieDev
Comment by @lucastheguyy
Comment by @Beethoven-n
Comment by @bunnikyuube
Comment by Speykious
Comment by Hailey
- 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.
Additionally, subprofiles are only cosmetic and wouldn't affect permissions or blocks (you will stay blocked if you use a subprofile). Behind the scenes it would be "just" additional metadata, so the original message author is always there as well (and would still be used for other things like mentions, replies, blocks, and slowmode). I considered having subprofile use behind a permission, but I think that would end up in communities gatekeeping the feature. So it's better to double up on other abuse prevention methods. I am also considering taking this on myself... I'm just not confident that the effort would be worth it, if it isn't merged. An initial implementation would be for text, and it would really just cosmetically replace the profile picture and name of the sender with the subprofile's details [name color kept], and show the subprofile's details in the profile card, hinting at the main (system) profile somewhere on it. Future iterations could include VC support (depends on what I can do with VCs), cosmetic roles, or user-set custom name colors (which would be a part of regular profiles as well). edit: also I thought I'd call it Personas. Subprofiles might be better but it could be confused with server profiles. Not really sure on the name.Comment by @bunnikyuube
Comment by Hailey
Comment by @chiaracoetzee
Comment by @Hate9
Comment by @chiaracoetzee
Comment by @AspectBox
Comment by Hailey
Comment by @AspectBox
Comment by @chiaracoetzee
647615036-bab2621a-df3a-4288-a90b-09821a2a56ad.png
583×497 | 49 kB Link to 647615036-bab2621a-df3a-4288-a90b-09821a2a56ad.png
647621454-0b6ae11b-2a63-48c6-aebc-2932475231c0.png
631×502 | 59 kB Link to 647621454-0b6ae11b-2a63-48c6-aebc-2932475231c0.png
647615635-b57b5ff3-4448-4379-8d16-50b399174443.png
586×748 | 80 kB Link to 647615635-b57b5ff3-4448-4379-8d16-50b399174443.png
647615869-c80b3985-4d5e-45dd-89bf-807d89a0253a.png
1603×1119 | 181 kB Link to 647615869-c80b3985-4d5e-45dd-89bf-807d89a0253a.png
Comment by Hailey
Comment by @chiaracoetzee
Comment by @AspectBox
Comment by @chiaracoetzee
Comment by @nagaconnie
Comment by @bunnikyuube
Comment by @bunnikyuube
Comment by @bunnikyuube
Comment by Hailey
Comment by @coldreindeer
Comment by @Hate9
Comment by @virtueisdead
Comment by @virtueisdead
Comment by @Enovale
Problem
Users across all messaging apps, very prominently Discord, would like to be perceived and referred to by a different identity, avatar, pronouns, among other identifiers in certain contexts, without resorting to elaborate solutions like alt accounts. Users may want to do this for many reasons, but just to name a few:- Plural systems and/or people with DID wanting to associate a certain alter with sent messages
- Users who want to be seen a specific way among certain people, such as close friends, professional colleagues, or family
- Users role-playing as characters, for example in Tabletop Game communities
Platforms like Discord, Matrix, and Signal provide no native solution to this problem. However Discord users have come up with an interim solution, via bots utilizing Discord's webhook infrastructure. Typically users type in phrases that tell the bot to replace their next message with a webhook message styled after their chosen name and avatar, containing the original message content. I will refer to bot-produced messages pretending to be a user's given identity as "webhook messages" for simplicity, though note that Matrix bridge bots implement this behaviour with real accounts, though most of the same restrictions apply. I would like to address some problems with this solution:Proposal
I propose a feature I will refer to as Personas (though this is not meant to limit what it may be eventually labeled as in the Fluxer platform). This concept is malleable so consider the design I'm about to lay out a draft: Users are able to go into their profile customization settings, and using a similar system as is already implemented for Community Profiles, users can add a (hypothetically) arbitrary amount of Personas. These Personas inherit the global profile's details by default, like the Community Profiles do, and allow overriding all the profile data that you can customize in the global profile. The difference between Personas and Community Profiles is that Personas can be selected to be used for any given message at any time, and ideally can also be used during calls, streams, the current Persona is shown in the member list, etc. Perhaps a dropdown menu is available in the bottom left next to the rest of the user popout options like status and account switching. Just like Community Profiles, the original global account these Personas link should be obvious and easily retrievable by observing users. Perhaps in the member list there is a small cutout of the global user's avatar if it differs from the Persona. There is a button in the 3-dot menu of a Persona's popout to see the Global Profile, etc. But whenever possible, the Persona's information is the first and most prominent information the user sees. Certain exceptions may of course be made, audit logs should not be confusing when Personas are involved in actions, if Personas are visible in the member list perhaps they continue to be sorted by their global profile name, otherwise a user could cause rapid shifting in the member list. But these should be done only when necessary. The goal especially is for Plural Users or Users who want to only express themselves a certain way in certain communities to feel truly expressed in every aspect Fluxer can reasonably aim to provide (Not to sound too grandiose!). Back before Fluxer blew up, I chatted with Hampus about this feature, to discuss possible avenues for implementation, though this was before V2. Additionally, Hampus suggested all device's selected personas be pooled into an array of IDs in the presence object that could be used to show multiple personas as Online, if such a feature were to be implemented.Notes
I made it clear that an intended use case would be people using specific personas with specific people, which, if taken to it's logical extreme, could include vulnerable people using Personas that could make them unsafe if seen by the wrong people. Should Personas be publicly viewable/indexable? If not, how would we even prevent it? Ideally I want this system to be usable by bots as well. If the community around Fluxer decides the current system is inadequate, at least ports of PluralKit's idea could use the Personas system to get around many, but not all of the aforementioned limitations. Would blocking individual personas be a desirable feature? ----- I'd also like to note for the purposes of this discussion, I am not a system, I don't even do tabletop roleplay often, I just look at the system such users are stuck with on Discord and get sad.Comment by @bunnikyuube
- The "Personas" dropdown appears at the top of the member list, separated by a visible seam, and displaying, in order of priority; First activated Persona of all listed, Default Server Profile Avatar/Name, Global profile Avatar/Name.
- The Personas are treated as Tickboxes, enabling and disabling them in that menu will display them in the Members list as online publicly. (Maybe worth adding Online, Idle, DND, Ignore states too?)
- The Message box displays the current persona in the left side of it in Avatar/Name form (optionally either or both), defaulting to the first activated persona or the default profile.
- Additionally (when they're implemented) discord-style parametric slash commands could be used for sending messages instantaneously as a specific persona. Ie;
Done this way, it... would also be theoretically possible to block Personas individually. Which would be nice for quality of life and general usability, though i think there's also an agreement that it's pretty rare to have an excuse to block one Persona/alter and not others. That said, why not do it anyway? Unfortunately, i have very little technical insight to give on the matter, but the UX is incredibly important to Fluxer's popularity and my opinion and i'd love to contribute to a discussion in making a feature like this as smooth as it can be. Concept is definitely a switch-up from the one i sent in the comments a few months ago, but i think the multiple Online personas concept is far more important than sending one message under multiple. Under that context i think this workflow concept works fine, and Slash commands would be more than effective enough for sending one persona's messages at a time. It would be a major muscle memory issue for some (not having the traditional Pluralkit-style proxies), but that can be solved through community bots regardless./p:PersonaName/ID [Message]Comment by @Enovale
Comment by @Enovale
Comment by @bunnikyuube
Comment by @bunnikyuube
Comment by @monty58
Comment by @coldreindeer
Comment by @coldreindeer
Comment by @Hate9
Comment by @arxari
Comment by @bunnikyuube
Comment by @chiaracoetzee
Comment by @chiaracoetzee
Comment by @virtueisdead
632690920-afffb76c-8ebb-461a-9490-7ca5294d7361.png
684×355 | 30 kB Link to 632690920-afffb76c-8ebb-461a-9490-7ca5294d7361.png
632690921-5d97c247-d567-4c42-ace9-110a9450e67f.png
802×687 | 87 kB Link to 632690921-5d97c247-d567-4c42-ace9-110a9450e67f.png
632690930-a19a3cda-7eab-426d-98ef-06449d489da4.png
568×580 | 34 kB Link to 632690930-a19a3cda-7eab-426d-98ef-06449d489da4.png
632690941-67ee0b46-114e-4964-9eb6-bce286982717.png
562×215 | 10 kB Link to 632690941-67ee0b46-114e-4964-9eb6-bce286982717.png
632690949-96d675bc-d94f-4bf7-a679-15bbded6bd5f.png
329×68 | 7 kB Link to 632690949-96d675bc-d94f-4bf7-a679-15bbded6bd5f.png
Comment by @pyroraptor07
640485618-a2222498-c483-495d-b7ef-06bb9decd030.png
397×189 | 10 kB Link to 640485618-a2222498-c483-495d-b7ef-06bb9decd030.png
Comment by @chiaracoetzee
647626661-6f5bb49a-b736-4409-ba78-86c87d403275.png
622×655 | 73 kB Link to 647626661-6f5bb49a-b736-4409-ba78-86c87d403275.png
647626096-1b76487e-8309-4cd0-8808-417eb24618e7.png
598×745 | 81 kB Link to 647626096-1b76487e-8309-4cd0-8808-417eb24618e7.png
647626981-ffec720b-2305-4199-86f4-52f0afe3216d.png
1590×1144 | 181 kB Link to 647626981-ffec720b-2305-4199-86f4-52f0afe3216d.png
Comment by @bunnikyuube
Comment by Speykious
- I'd ensure that the
- I'd slightly increase the width of the subprofile switching modal in the second screen so that
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.Import from PluralKitandAdd Subprofilebuttons 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 ownButton(fluxer_app/src/features/ui/button/Button.tsx) component instead. Same for the other buttons if you did it that way there too.Last Useddoesn't span two lines of text.Comment by Hailey
Comment by @chiaracoetzee
- 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.Comment by Hailey
648345950-bedaba60-aa25-43fb-a62e-f22ec1aeffba.png
265×64 | 8 kB Link to 648345950-bedaba60-aa25-43fb-a62e-f22ec1aeffba.png
Comment by @chiaracoetzee
648372452-d0bf7e83-9444-4733-b17b-3817d568bf2d.png
597×793 | 82 kB Link to 648372452-d0bf7e83-9444-4733-b17b-3817d568bf2d.png
648372149-392e1f84-347a-4f7e-8508-50639746a77d.png
1966×1168 | 198 kB Link to 648372149-392e1f84-347a-4f7e-8508-50639746a77d.png
648383494-e6cad2a3-24bf-41cb-b8ff-651ca27793b4.png
667×420 | 66 kB Link to 648383494-e6cad2a3-24bf-41cb-b8ff-651ca27793b4.png
Comment by I
Comment by Speykious
Comment by I
Comment by @Hate9
Comment by I
Comment by @Enovale
Comment by I
Comment by I
Comment by @Hate9
Comment by @chiaracoetzee
Comment by @chiaracoetzee
Comment by @VanguardSys
- It has an avatar and display name distinct from the main/root profile.
- It can be toggled/switched to manually, or through trigger arguments such as prefixes and/or suffixes sent along with the message (such as
- The active Persona should be able to remain active for subsequent messages, the behavior of which is set by the user. Using a trigger argument could temporarily (or not) switch Personas, such as for one message or from then on.
- Multiple Personas should be able to used simultaneously, to show multiple people in front, co-conscious, or blurring; or, multiple characters speaking at once.
Personas should be easy to organize.f:<message>or{<message>}). Support for multiple distinct triggers would also be appreciated- The limit of Personas one account can have should be generous. Some systems are huge, some people have a lot of characters, and some people have multiple uses for the Personas feature.
- They should support folders/groups, and folders/groups within those. A simple list would get cluttered quickly with several Personas.
- They should be searchable by name and by group. For example, if I wanted to find all our characters for a particular campaign.
- Importing from plural/proxying bots can be done with a simple "Import..." button. Many if not all of the proxying bots use a common JSON format, so compatibility should be trivial without having to make it plural-specific.
Personas should be easy to moderate. - Moderation actions (kick, mute, ban, etc.) apply to the user, not the Persona. Many plural spaces already follow this rule ("be responsible for you and your system"). - Personas should show the user behind them in sent messages, in member lists, and in voice channels. It should be abundantly clear when someone is using the feature to impersonate another user, or one of their Personas. - If a particular Persona is bothersome, they should be able to be blocked without blocking the user, and without obstructing normal blocking usage. Ideally, you could additionally block all of their Personas at once, showing their original unmodified messages and appearance. We're not as well-versed in the technical side of things, so hopefully this works as a design doc or something. If you'd like to learn more about plural systems and how to best accommodate us, https://morethanone.info/ is a good starting point.Comment by I