Open DEEO opened 14 years ago
Ok, so it appears that every tweets sent via the API get this "special treatment" (the characters &, < and > are already escaped in the json).
It may be out of the scope of Tweetify itself, but making the xhtml escaping optional (activated by default) would be usefull for plugins depending on it. Pull request sent (but it may need a rewrite since it looks ugly).
I ran across a very troubling issue concerning the XHTML escaping.
It's seems that sometimes twitter escapes the & character ( exemple : status / json ) while other times it doesn't ( exemple : status / json ). I must say I love their consistency.
We should find out what is the discriminating factor (is it because the tweet was send to the API or because twitter doesn't like to be fed with html entities) to fix the problem. I might work at it tomorrow.
(yes, this is only an issue for those who actually use tweetify with contents from twitter)