this post was submitted on 20 Aug 2024
621 points (88.7% liked)

Showerthoughts

30430 readers
1021 users here now

A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. The most popular seem to be lighthearted, clever little truths, hidden in daily life.

Here are some examples to inspire your own showerthoughts: 1

Rules

  1. All posts must be showerthoughts
  2. The entire showerthought must be in the title
  3. No politics
    • If your topic is in a grey area, please phrase it to emphasize the fascinating aspects, not the dramatic aspects. You can do this by avoiding overly politicized terms such as "capitalism" and "communism". If you must make comparisons, you can say something is different without saying something is better/worse.
    • A good place for politics is c/politicaldiscussion
    • If you feel strongly that you want politics back, please volunteer as a mod.
  4. Posts must be original/unique
  5. Adhere to Lemmy's Code of Conduct

If you made it this far, showerthoughts is accepting new mods. This community is generally tame so its not a lot of work, but having a few more mods would help reports get addressed a little sooner.

Whats it like to be a mod? Reports just show up as messages in your Lemmy inbox, and if a different mod has already addressed the report the message goes away and you never worry about it.

founded 2 years ago
MODERATORS
 

It sounds way less offensive to those who decry the original terminology's problematic roots but still keeps its meaning intact.

you are viewing a single comment's thread
view the rest of the comments
[–] SpaceCadet@feddit.nl 8 points 5 months ago

I’ve seen ‘Active / Passive’ used, that seems alright

That's not always an accurate description though.

Consider a redundant two node database system where the second node holds a mirrored copy of the first node. Typically, one node, let's call it node1, will accept reads and writes from clients and the other node, let's say node2, will only accept reads from clients but will also implement all writes it receives from node2. That's how they stay in sync.

In this scenario node2 is not "passive". It does perform work: it serves reads to clients, and it performs writes, but only the writes received from node1. You could say that node2 slavishly follows what node1 dictates and that node1 is authorative. Master/slave more accurately describes this than active/passive.

There’s plenty of alternative terms to use without borrowing terminology from sexual roleplay.

Do I have news for you ....