what it means to refuse to add PluralKit to your discord server.
on a fundamental level, there are two* ways one can present their plurality in online communication.
1. the parts of a message that represent a singlet's identity are mapped to a shared system identity.
messages are sent under a shared system name, profile image, etc. and distinctions between system members are made on a lower level of information hierarchy; emoji indicators, names in sign offs, etc.
2. the parts of a message that represent a singlet's identity are mapped to individual system member identities.
each message gets the name of the headmate who wrote it, their own avatar, etc. shown to other users. usually with some gesture towards a shared identity in the form of a system tag or unifying style elements across profile pictures, naming conventions, and the like.
approach 1 here is already possible with existing platforms, whereas approach 2 almost always requires somewhat hackier interventions like PluralKit (or pluraldawn on mastodon). and these two approaches encode beliefs about plurality.
primarily presenting as your shared system identity can make sense for some people. if you're median you might literally see your system members as parts of a larger whole. for others their plurality may feel like a personal internal phenomenon, that they don't want to realise socially. many systems have contexts where they want to converse on a system level, making shared decisions.
but for other systems, having your headmates treated as whole individual people is necessary, and it is very hard to do this when they are visually treated as a typing quirk of the person known as Your_System_Name_Here.
they might prefer to be addressed by their own name and not the system's. they might be talking about a personal topic that applies to them and not the others. these are not impossible in an approach 1 context, but it makes it significantly harder - the structure of the messaging app works against you.
being seen and perceived as yourself and not the system as a whole can be necessary for building any kind of close rapport with someone. oftentimes we need to bring friends into personal servers with PluralKit to properly unmask and feel seen as ourselves.
I'm writing here, as a median-ish system who often feels fine speaking as a shared whole in less intimate contexts. sometimes we blur together, or will deliberately deproxy where the speaker doesn't matter. but the kind of interactions where you need to be seen as your own person, separate from your headmates, require tools to make that happen.
the design of chat apps makes this problem one-way. you can always choose not to proxy a message, to speak as a shared self. but to present individually, as your own person, on the same level as any other user, you need PluralKit (or similar).
when an admin refuses to incorporate these accessibility tools, they are denying that possibility. if they go a step further, recommending approach 1 type solutions instead ("just use emoji indicators") they are in fact expressing a belief about plurality; that they see these two representations as equivalent, that every plural system's headmates are parts of that system before they are their own people - this might be how some systems self identify, but it is a wildly inappropriate way to treat plurality as a whole.
i understand PluralKit messages are not as transparent as other messages. users may be confused, admins may need to be taught how to interact with them. in a large enough public server the burden may seem (or even be) too high for your team to manage. but consider what these tools actually do for users, and what beliefs you are encoding about plurality, when you respond to their requests.