• MacN'Cheezus@lemmy.todayOPEnglish
      0·
      10 months ago

      Pretty sure it’s garbage, because it kept repeating JzH a couple hundred more times before terminating without a closing parentheses.

    • MacN'Cheezus@lemmy.todayOPEnglish
      0·
      10 months ago

      I tried to wait for it to finish, but after a couple hundred more repetitions of JzH it just stopped abruptly without a closing parentheses, so I think I’ve been had.

    • OhNoMoreLemmy@lemmy.ml
      0·
      10 months ago

      It used to do this all the time a few months ago. The links never worked. Eventually I got bored of asking it.

    • Ephera@lemmy.mlEnglish
      0·
      10 months ago

      I can’t get it to decode, even after correcting the base64 padding. Firefox just shows the broken image icon. My image viewer throws out the glorious log message Image format is actually "png" not "png", along with a bunch of checksum errors.

      I guess, the checksum can’t be correct when it’s cut off, but none of my image viewing/editing software wants to look past that.

      In a hex viewer, it looks like this:

      Compared to a normal PNG:

      I don’t know the PNG spec by heart, but I guess, it doesn’t look completely off the rails before it goes there…

  • superbirra@lemmy.world
    0·
    10 months ago

    it’s meta and some assembly is required: the meme is the broken response so you can screenshot it and post on lemmy

    • EvokerKing@lemmy.world
      0·
      10 months ago

      The response isn’t even broken. It’s not finished. It gives responses in markdown, same as Lemmy. That is the syntax for a picture embed, it’s just still typing the rest and it doesn’t show it until it’s finished typing.

      • ChaoticNeutralCzech@lemmy.ml
        0·
        10 months ago

        I analyzed it in another comment: the header says the image is 300x300px 8-bit RGBA but the data is invalid. Most viewers will notice that and show an error.

        However, the syntax it used for embedding images is valid, as data:image/png;base64, is the start of a valid image URL and you can use it like other image URLs in supported Markdown interpretors.

        Example, using the 103-byte Google Maps’ sea tiles, and a 178-byte GIF:

        ![Google Maps sea map tile](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQAAAAEAAQMAAABmvDolAAAAA1BMVEW10NBjBBbqAAAAH0lEQVRoge3BAQ0AAADCoPdPbQ43oAAAAAAAAAAAvg0hAAABmmDh1QAAAABJRU5ErkJggg==)
![wink.gif](data:image/gif;base64,R0lGODlhDwAVAKIEAAAAAP//AP//3v///wAAAAAAAAAAAAAAACH/C05FVFNDQVBFMi4wAwEAAAAh+QQFlgAEACwAAAAADwAVAAADSUiq0L2QtEDpg6Bqu/LeAGN5wVRKlVmS6qe17hiDHvlyNciho5N2sxDGtoIMBgyH8Kg4IiMEZ1NKlUarSOdTe81arZHvE3olJAAAIfkEBR4ABAAsCAAEAAQABQAAAwYIGtz+ASQAOw==)

        renders as

        Google Maps sea map tile wink.gif

        Works in the default web interface