🐈‍⬛ the more you've been exposed to the way that the diversity of plural self expression expands to fit the capabilities and technical-social friction of the tools immediately available, the more it becomes eye-burningly obvious that "let's set the bar where it already is" is a completely ridiculous take. neither of us knows who has no way to comfortably speak today but could tomorrow - if we don't accept stagnation on our standards as the default.

give us, give eachother, more thought than the bare minimum.

🐈‍⬛ chat multi-id implementation pitfalls:

- Impermanence i.e treating using a different ID as a "change" (IRC /nick)
- Scoping i.e admin agency (tupperbox perms, discord bot invites, matrix via getting IP banned after joining 20 times)
- Armbanding i.e. BOT, APP, "masquerade", "x used proxy", anything that de-naturalises it being a message sent by a user
- Opaqueness i.e. missing interactions (moderator, profile view, etc) compared to other messages OR multi-id not being trivially findable (e.g. client mods)
- Serversidedness i.e client can't preview the ID avatar before sending a message
- Complexity i.e scaling anything with identity quantity (matrix account switching, anything that lacks in-message tag parsing)

This is not something you can "tack on" - the ultimate ideal is that ALL messages/accounts are multi-id - most just never set up their second ID.

PluralKit is worlds better than most people have the perspective to understand, but we can do better. don't compromise on us.

@lavenderdotpet so a big reason that the reason that the APP tag exists on discord webhook messages is that you can't click on them and see where they came from.

if you're in an impl where you can trivially reveal the username of the sender account on click, you don't need a mark (or it can be a user-defined tag, as if PK system tags were clickable)

if you're not, the mark should be the username itself, not something related to the impl/feature.