196
Community Rules
You must post before you leave
Be nice. Assume others have good intent (within reason).
Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.
Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.
Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".
Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.
Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.
Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.
Avoid AI generated content.
Avoid misinformation.
Avoid incomprehensible posts.
No threats or personal attacks.
No spam.
Moderator Guidelines
Moderator Guidelines
- Don’t be mean to users. Be gentle or neutral.
- Most moderator actions which have a modlog message should include your username.
- When in doubt about whether or not a user is problematic, send them a DM.
- Don’t waste time debating/arguing with problematic users.
- Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
- Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
- Ask the other mods for advice when things get complicated.
- Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
- Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
- Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
- Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
- Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
- First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
- Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
- No large decisions or actions without community input (polls or meta posts f.ex.).
- Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
- Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.
view the rest of the comments
I mean in that sort of case then the group would defer to the person more knowledgeable in that specialty, same as what happens when after brainstorming people split into small groups or volunteer for individual responsibilities. Crowdsourced decision making is meant to be for the bigger aspects, stuff like what the end goal of a project should be. Smaller, extremely specialized aspects should get handled by those best equipped for it, that's not a hierarchy. Listening to an expert is just respecting someone's knowledge, and as long as they don't have actual authority over you, then there's much less risk of corruption taking place. There's a quote from I think ~~Proudhon~~ Bakunin that I can't remember off the top of my head, I'll come back and edit this when I find it. But effectively, it boils down to the difference between authority as in power over people, and authority as in knowledge.
And people who help organize and manage jobs also don't necessarily need to be part of a hierarchy either. If the group agrees that someone is extremely effective at helping resolve conflicts or suggesting the best path to take and that sort of role is desirable for the project then that's what they should do. The difference is that they aren't in a position of power over anyone. They don't have the unilateral ability to fire someone (nor does any individual), or take away their income/ability to live. And since they don't have that power, they aren't in a hierarchical position over anyone. If they start trying to force their way without taking feedback then the group will stop listening to them and appoint someone else if they still feel that it'd be useful. Without a position of authority over people no hierarchy exists in the definition used in anarchist theory.
Edit: Thanks @[email protected]! Knew I read it somewhere on here recently.
— Mikhail Bakunin, God and the state, Chapter 2
But yeah, respecting peoples expertise in topics, splitting up work, or appointing people to give managerial suggestions aren't hierarchical. A lack of hierarchy is not a lack of structure, it's just a lack of power and violence being used to oppress or control people. Efficient structures like these tend to naturally fall out of self-organization once the monopolies on violence used to prop up hierarchies are removed.
good post. since i'm here, i want to expand on a few things:
i recommend using expertise to refer to authority as in knowledge — like you did later in your comment, as Andrewism does — to avoid confusion.
no criticism, just expanding:
i think it's important that someone who is given by a role or responsibility should have a mandate: the role should be specific, and it should be temporary (for an arbitrary amount of time, or till the end of a project) or recallable by a vote.
Graeber notes in something i'll link below: 'If something has to be done, then it’s okay to say all right, for the next three hours she’s in charge. There’s nothing wrong with that if everybody agrees to it. Or you improvise.'
in Kurdistan, this is the difference between technical decisions and the political ('moral') decisions[1]. it's the difference between 'when should we have our next meeting?' and 'should we be nonviolent?'.
the political decisions are consensus decisions, of at least 1/3 of the group. these are vetoäble by anyone affected who wasn't present for the vote.
the technical decisions are 2/3 or 3/4 majority votes, of the minimum affected people.
tho, as Graeber notes:
only partially related, but this discusssion reminded me of an essay on the myth that
management == efficiency
: David Harvey, anarchism, and tightly-coupled systems