itslilith, 1 year ago (edited 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