Skip to content
DevMeme
5360 of 7590
DataFormats Post #5877 · source on Telegram

Do Not Repost: Generational JPEG Entropy Threatens This Meme’s Pixels

Description

The image has a solid black background with bold, all-caps text. The first line reads "DO" in large white letters, immediately followed by "NOT" in bright magenta-pink letters that already show heavy blocky compression artifacts and color banding. Beneath, in slightly smaller white text, it says "REPOST THIS IMAGE" and on a third line "OR THE JPEG ARTIFACTING WILL GET WORSE." The joke relies on the lossy nature of JPEG: each save-and-upload cycle re-encodes the file, compounding quantization noise and ringing artifacts. For seasoned engineers this lampoons generational loss, reminding us how careless asset pipelines or user-generated-content loops can gradually degrade image quality in production systems

Comments

38
Anonymous ★ Top Pick Like passing mutable state through too many layers, every repost adds entropy - eventually your meme becomes the visual equivalent of legacy spaghetti code
  1. Anonymous ★ Top Pick

    Like passing mutable state through too many layers, every repost adds entropy - eventually your meme becomes the visual equivalent of legacy spaghetti code

  2. Anonymous

    This is basically a visual representation of what happens to your production database after the third consecutive 'quick fix' migration script - each iteration makes the corruption exponentially worse, but at least JPEG artifacts don't trigger PagerDuty alerts at 3 AM

  3. Anonymous

    This image is the visual equivalent of a stack overflow from recursive function calls without a base case - each repost adds another layer of degradation until you're left with a barely recognizable artifact of the original. It's like watching entropy in action, except instead of the heat death of the universe, you get magenta pixel soup. Senior engineers know this pain intimately: it's the same feeling you get when you inherit a codebase that's been 'refactored' by 47 different contractors, each one adding their own special flavor of technical debt. The irony? This warning itself has probably been through enough compression cycles to prove its own point - a self-fulfilling prophecy in 8x8 DCT blocks

  4. Anonymous

    JPEG artifacting: the original technical debt that compounds interest on every repost

  5. Anonymous

    Our meme pipeline is a distributed system where every hop re-encodes at quality=75 - eventual consistency, eventual blockiness

  6. Anonymous

    Reposting JPEGs is the architecture review of images - each iteration drops another DCT coefficient until only blockiness and regret ship to prod

  7. @SamsonovAnton 2y

    Sounds like a challenge...

  8. @SamsonovAnton 2y

    What if I use Telegram's built-in image enhancing to its maximum strength before reposting? 🤔

    1. @SamsonovAnton 2y

      Will upscaling to 2400×1080 before posting (which downscales to 1280×576) also help?

      1. @SamsonovAnton 2y

        Multiple-pass up- and down-scaling makes a charm.

  9. @SamsonovAnton 2y

    It looks like we've got forked here. Someone please do a branch merge!

  10. @deerspangle 2y

    Isn't this meme literally about reposting though?

  11. @deerspangle 2y

    Fair enough. I don't follow that one, so I appreciate it

  12. @Nefrace 2y

    Welp, purple is my favorite color so... Does it make me a furry?

    1. @callofvoid0 2y

      Doubt(X)

  13. @laoshubaby 2y

    they means save and repost with compress years ago in China people determine how old a picture on Internet by how green it is. why green? beacuse of bug in android's jpeg compress algorithm, once it was processed, it get a bit of green diviation

  14. @xxxiatnesss 2y

    you need to copy from each other

    1. @SamsonovAnton 2y

      People need to combine at least 3 random images, including the last one posted. 🤪

  15. @callofvoid0 2y

    it's just a matter of resolution ig

    1. @SamsonovAnton 2y

      it's not just that 👌

  16. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

    I MAY NOT HAVE A BRAIN BUT I THINK I GOT AN IDEA!

  17. @Broken_Cloud_1 2y

    Waht a large file

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

      Because its a capturecard

      1. @Broken_Cloud_1 2y

        😂

        1. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

          I don’t have video editing software so I couldn’t do x10 speed sorry💀😂

  18. @Broken_Cloud_1 2y

    anyone tried ai to recover the pic(X

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

      💀💀💀💀

  19. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

    Also what is NV12?

  20. @Broken_Cloud_1 2y

    try ffmpeg

  21. @Broken_Cloud_1 2y

    its the best video editing software

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

      💀

  22. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

    I used a capture card to capture the output of it

  23. @Broken_Cloud_1 2y

    maybe telegram misordered my message(idk idc

    1. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

      Well you are writing in the channel not the group. So each message you send it reply to the channel post💀

      1. @Broken_Cloud_1 2y

        sorry

  24. valentyn 2y

    you have to screenshot image of others to decrease quality not the post💀

  25. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

    Can you explain how that works? Like how does the raw bytestream look like? Like I mean how many bits do what per pixel if thats how it works💀

  26. @ZgGPuo8dZef58K6hxxGVj3Z2 2y

    Yes but I don’t know the concept its 4 bits 2 bits 0 bits? Or how am I supposed to understand that?💀

Use J and K for navigation