For a community, you *have* to ban early and ban often, and defederate early and often.
As an admin, it's your job to protect the ✨vibes✨ of your space, to promote community, and to remove elements that are toxic or harmful.
A service doesn't work the same way. It isn't attempting to create (or promote) a specific vibe, it's just *there*. You make of it what you will, find what you will, and (as an end user) block what you will.
The admin "just" makes the service available.
@aurynn I've seen the recommendation given to Fediverse newcomers: start at a large instance, then branch off into your favourite small one.
I wonder if the same kind of evolution happens for communities? First, people bump into each other on a large "service" instance. They get to know each other better and interact more; perhaps they start a few common 🐟 gup.pe groups.
Then, at some point,the "service" instance can't sustain the community, so they branch off and form their own instance ⤴️
@aurynn of course this assumes someone in the community has the technical know-how and enthusiasm to set it up; the worse case would be that they simply stay on the service instance with a not-so-optimal experience 😕
Scholar Social is a microblogging platform for researchers, grad students, librarians, archivists, undergrads, academically inclined high schoolers, educators of all levels, journal editors, research assistants, professors, administrators—anyone involved in academia who is willing to engage with others respectfully.