If in-line replies become the only option, I'll have the choice of wasting countless time to dig through past replies, or just stop checking chat altogether.
Anyway, when reading the code, you're safe in assuming "=3D" is just a single plain old equal sign. In the "quoted-printable" encoding scheme the two characters following an equal sign are the hex value of the intended character. In effect, equal signs need to be escaped using the "=3D" sequence.
This drove me a little nuts as I was reading and trying to code switch between the assorted languages used in the examples.
I once tried to rebrand an in-house, purely dev facing product. I failed.