Just had an idea: maybe Twitter could add an optional parameter to
switch off HTML escaping (&escapeHTHML=false or something like that).
That way developers who are unaware of the issue would get the escaped
HTML, and the developers who are aware could get the proper data.

Reply via email to