If you're never going to show a tweet in a HTML context, it would be safe to
unescape the entitized characters. Tweets are often fed directly from an API
call to an HTML context, which is why we protect against malicious HTML by
escaping certain tags. Storing as received is likely the best bet.
@e
I see how to fix it,I have to html unescape the tweet, is it safe to
html unescape all tweets ?
On Aug 4, 4:58 pm, Jeremy Dunck wrote:
> Characters are not necessarily a single byte. Which are you counting?
>
>
>
>
>
>
>
> On Thu, Aug 4, 2011 at 5:05 PM, Jason Toy wrote:
> > I see some tweets
I am counting unicode characters.
On Aug 4, 4:58 pm, Jeremy Dunck wrote:
> Characters are not necessarily a single byte. Which are you counting?
>
>
>
>
>
>
>
> On Thu, Aug 4, 2011 at 5:05 PM, Jason Toy wrote:
> > I see some tweets going through my system that are over 140
> > characters, for e
