• 2 Posts
  • 11 Comments
Joined 3 years ago
Cake day: June 13th, 2023

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.





  • I’m hosting the Decronym bot on a single-user instance, and it’s a real pain. The bot’s been down for weeks, actually, because an upgrade failed with some obscure error around the database schema…

    I’ve ended up just today, wiping the whole thing and starting over, losing all data and having to refederate the bot. So yeah, I wouldn’t recommend.

    [Acronyms to help the bot re-establish: LVM, HASS, k8s]






  • A little lower down the stack, I always liked the Evil Bit in TCP, a standard which removes all need for firewalls heuristics by requiring malware or packets with evil intent to set the Evil Bit. The receiver can simply drop packets with the Evil Bit set, and thus be entirely safe forever from bad traffic.

    At the physical interface layer where data meets real life, I especially enjoy IP over Avian Carrier; that link in particular is to the QoS definition which extends the original spec for carrying packets by carrier pigeon.




Let’s get the AMAs kicked off on Lemmy, shall we.

Almost ten years ago now, I wrote RFC 7168, “Hypertext Coffeepot Control Protocol for Tea Efflux Appliances” which extends HTCPCP to handle tea brewing. Both Coffeepot Control Protocol and the tea-brewing extension are joke Internet Standards, and were released on Apr 1st (1998 and 2014). You may be familiar with HTTP error 418, “I’m a teapot”; this comes from the 1998 standard.

I’m giving a talk on the history of HTTP and HTCPCP at the WeAreDevelopers World Congress in Berlin later this month, and I need an FAQ section; AMA about the Internet and HTTP. Let’s try this out!