this post was submitted on 09 Jun 2026
14 points (79.2% liked)

Programming

27223 readers
488 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] TehPers@beehaw.org 1 points 2 hours ago (1 children)

Gatekeep (v.):

to restrict access to (something of value, such as information, knowledge, or resources) in order to exert power or control over a person or group

The person I was responding to was restricting the author's access to the conversation by publicly refusing to engage with them over a trivial, irrelevant matter. So if that's not gatekeeping, then clearly they're calling the author a clueless idiot, which is just plain rude.

[–] x74sys@programming.dev 1 points 6 minutes ago

You have it plain sight. Refusing to engage with someone is not gatekeeping. Your definition pretty much aligns with what I said.

And if someone doesn’t have any idea what they’re talking about, then maybe they shouldn’t take part in the talking. You can’t tell me that you‘ll take cybersecurity advice from someone who saw a movie about hacking.

Which doesn’t mean that clueless people have nothing of value to add, but it’s unlikely (especially in highly factual discussions).