• itslilith@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      It’s a failed html escape sequence for &

      some lemmy instances were having trouble with that for a while now. html used ampersand to encode special characters, and a regular ampersand gets encoded as &

      Somehow, the decoding sometimes breaks, and we get to see it the way it is here