this post was submitted on 04 Jun 2026
19 points (100.0% liked)

Selfhosted

60091 readers
1413 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I've had some feedback today that Decronym is "spamming" unrelated acronym definitions into threads that don't need them. Unfortunately, details of which acronyms are superfluous wasn't forthcoming, so:

From this list, which acronyms do you guys think can be removed as unnecessary to explain?

http://decronym.xyz/acronyms/selfhosted@lemmy_world

Edited to add: There've been instances of the bot "finding" acronyms that aren't mentioned in the thread, and speculation that vibecoding is at fault. The real answer, I think, is simpler.

Decronym uses a local Lemmy instance, and polls the database directly for new comments. Last time I tried to upgrade Lemmy, it went so badly I had to wipe the server and start over from a fresh Debian; threads on the fresh instance started from ID 1 again.

But Decronym's list of detected acronyms wasn't wiped, so it's been pointing at the wrong thread IDs this whole time.

I've now wiped the threads and detected acronyms for this comm, and the bot should behave more sensibly.

you are viewing a single comment's thread
view the rest of the comments
[–] non_burglar@lemmy.world 8 points 2 weeks ago* (last edited 2 weeks ago)

You are trying to de-jargon topics, and that's fine, but the two following categories do not help, they are localized habits and don't have any value to non-english or nontechnical people, or both:

  • shortenings: a11y for accessibility is not a common contraction, it's not helpful for anyone to understand the term itself
  • names of services: CF for cloudflare is not something worth defining. Names change, and you wouldn't see this in a professional document. It's like defining "lol", the acronym is shorthand in typed communication, not technical jargon.

Side note, DNS stands for domain name system, it has never meant domain name service.

I personally find bots annoying, half the content on the internet is already bots.