Status Report on Community Discord Exit
The server was joined with enthusiasm. The server is now a source of ambient obligation. Exit procedures are more complicated than entry procedures.
Official Application for Community Discord Exit Submitted by: The Subject To: The Subject's Own Internal Governance Body Re: Approval to Leave the Server
Background
The subject joined a community Discord server in October 2021. The server was associated with a newsletter the subject had been reading. The server was described in the newsletter as a place where subscribers could connect and discuss relevant topics.
The subject joined. Joining was a single click. Leaving has required three weeks of advance preparation.
Current Server Status
The server has 847 members. The subject has direct knowledge of three of them. The subject has exchanged messages with one of them, on one occasion, regarding a topic that has since been resolved.
The server contains twelve channels. The subject is not muted in any of them. This was the default. The default has been generating notifications since October.
The Problem
The server cannot be left quietly because the member list is public and departures are announced in the server, to the server, at the moment of departure. The announcement reads as follows: "[Subject Name] has left the server."
This is a factual announcement. It is visible to 847 members. Most of those members do not know the subject's name. The subject nonetheless anticipates the announcement as a source of humiliation.
Complicating Factor
The subject knows one of the three known members well. That member is active in the server and posts content in two of the twelve channels. Leaving the server is visible to this member. The subject has not discussed leaving with this member because discussing leaving would require explaining why leaving is necessary, which would require acknowledging that the subject joined and never engaged, which is accurate and somehow worse.
Risk Assessment
Probability that any of 847 members will notice the departure notification: low. Probability that the one well-known member will notice: moderate. Probability that the well-known member will ask about it: low. Probability that the subject will experience the departure announcement as a judgment regardless of all the above: very high.
The Governing Rule
Online communities are easier to join than to leave because joining is framed as welcome and leaving is framed as departure; the asymmetry is structural, not accidental, because communities require members to function, and exit visibility is how they raise the cost of exit without making it impossible.
Recommendation to Internal Governance Body
Approve the exit. Set notifications to off first, so the departure is not preceded by a period of visible disengagement that is also visible. Leave on a Tuesday morning, when server traffic is lowest.
Status
Application pending internal approval. Departure estimated within two weeks, once the subject has made peace with the Tuesday morning strategy.