this post was submitted on 10 Oct 2025
150 points (95.2% liked)

The Shitpost Office

297 readers
770 users here now

Welcome to The Shitpost Office

Shitposts processed from 9 to 5, with occasional overtime on weekends.

Rule 1: Be Civil, Not SinisterTreat others like fellow employees, not enemies in the breakroom.

  • No harassment, dogpiling, or brigading
  • No bigotry (transphobia, racism, sexism, etc.)
  • Respect people’s time and space. We’re here to laugh, not to loathe

Rule 2: No Prohibited PostageSome packages are simply undeliverable. That means:

  • No spam or scams
  • No porn or sexually explicit content
  • No illegal content
  • NSFW content must be properly tagged

If you see anything that violates these rules, please report it so we can return it to sender. Otherwise? Have fun, be silly, and enjoy the chaos. The office runs best when everyone’s laughing.... or retching over the stench, at least.

founded 2 weeks ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Cypher@lemmy.world 21 points 1 day ago (1 children)

Back in my sys admin days a software packager couldn't get a packaged application to replicate to the distribution servers.

Knowing a few things, as all wizards do, I added a NSFW meme to the package. The package replicated to the distribution servers. Removing the meme breaks it.

I can still picture his expression of confusion, frustration and sheer bloody rage.

spoilerFor those who really want to know, it was with SCCM 2012 and the package had been corrupted when doing the initial hash. A package will fail replicating to distribution points if the hash doesn't match, adding the image updated the hash while removing it reverted it to the broken state. Adding any file to the package will fix it, as will a version update to the software.

[–] Rhaedas@fedia.io 10 points 23 hours ago

Neat reveal of the magic trick. Makes sense and pretty simple, but sometimes it's the simple things right in front of us that are the hardest to see.