quote:
Originally posted by Spunky
As people are getting this problem without updating anything, it's safe to say that it is happening server-side. There is no way to get around it.
That doesn't mean editing the exe won't work. Yes, there is some stuff going on server side, but there is also something happening client side. Just because no one updated doesn't mean there wasn't already code in place to handle this situation. Perhaps there's a flag sent with every message to tell it not to parse links? I dunno how exactly they implemented it, but it shouldn't be too hard to fix.
(having said that, I don't know anywhere enough assembly to even attempt fixing it >_>)