this post was submitted on 26 Sep 2025
1104 points (99.2% liked)
196
4542 readers
2235 users here now
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.
founded 8 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Most circuit boards are an absolute pride parade. You have your male to male/female to female connectors, MtF/FtM transformers, master/slave setups, multiport adapters, splitters, switches, docking, etc
There are also gender benders... Turn male to female or female to male.
They included that already with MtF/FtM
Master/slave terminology needs to die off. What a blatant callback to slavery times.
Should be using Dom/Sub amirite?
Oh, surely you must've meant Kermit/Miss Piggy.
Yes.
Noo! It just needs to become kinky instead.
I like parent/child. Add something? Parent adopts. Remove something? Parent abandons, leaving the process or component with trauma that will require years of therapy.
Then you get people asking how you kill abandoned child processes
"All orphans will eventually become zombies" -My OS lecturer last year
-9
I think it would be less of an issue if human slavery and all its attendant and resultant issues were actually firmly a thing of the past. It could become a "clinical", accurate way to describe technical constellations where one component is strictly subordinate to another, if it didn't have the connotation of ongoing human rights issues.
Not saying it's the best or the only option for the terminology, just wondering aloud whether the callback would be an issue if the topic wasn't still so raw and sore.
I quite agree. Personally I use Main/Secondary, I find it does away with the problematic terminology while needing no changes in acronyms.
Eh, I think master is used (AFAIK) unproblematicly in other contexts like a master key, recording master, and master pattern. Converting it to "main" seems like a change or loss of meaning, but the problem may be that there is not really a consistent meaning across electronics usage to start with. I think "secondary" has some connotation of filling the same purpose or type as the primary, which doesn't really fit for m/s usage. Master/sheep is my most similar option that keeps the "m/s", but it feels awkward enough to draw attention to what it replaces. Could just do master (or main) and sub, where "sub" could mean substitute, subordinate, subscriber, [submissive,] etc. as needed.
I like sender/receiver
Pitcher/catcher?
No, no, perhaps not.
leader/follower for things like Paxos and RAID arrays works okay.