Selfhosted

60093 readers

775 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

[Meta] Removing definitions from Decronym? (lemmy.world)

submitted 2 weeks ago* (last edited 2 weeks ago) by Two9A@lemmy.world to c/selfhosted@lemmy.world

15 comments fedilink hide all child comments

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

[–] talkingpumpkin@lemmy.world 12 points 2 weeks ago

I've blocked the bot because I find it's more annoying that useful (I'm not complaining - just giving feedback).

That said, IMHO from that list you should remove the entries that:

are ambiguous (eg: HA has 2 entirely different meanings in your list)
have become words on their own (eg. DNS, HTTP, etc...): nobody cares what these expand to (think, NASA) and also knowing what these expand to doesn't help at all (if you tell me that HTTP means "hyper-text markup protocol" will I not have to go read wikipedia anyways to understand what it is?)
are often not used according to your definition (eg. IP is more often used to refer to an IP address rather than to the protocol) - of course you may want to amend the definitions instead

Also, you should keep the acronym expansion ("RAID" => "Redundant Array of Independent Disks") from any comment you may want to add ("for mass storage") and - since you are at it - provide relevant links to wikipedia articles and/or other resources.

PS: since a lot of entries in the list are not even acronyms... maybe you should consider renaming the bot to something related to "abbreviations" or "glossary"?