It most likely has to do with where you are creating the saylink. Titanium and SoF/SoD use slightly different formats for passing links. If you create the link inside an event that is initiated by a specific client, such as EVENT_SAY, it will generate the link for that client version and it will appear correctly.
If you create the link outside of an event, however, there is no way of knowing what client will trigger it. It currently assumes the SoF style of link, so those extra characters appear when viewing it with a Titanium client. You can work around this by creating links only inside events that pass a client variable.
|
Threaded Mode
