[twitter-dev] Re: Entity encoding in API is broken.

[Chad Etzel]

Confirmed. Both if entering an update from web or API.

I sent a message "< &lt;" and got back "< <" as stated below.
also entered "& &amp;" got back "& &"

-Chad

On Thu, Feb 26, 2009 at 3:24 PM, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
>
> If you put a literal left angle-bracket into a tweet, it is rendered
> as the characters 'ampersand', 'l', 't', and 'semicolon', which is
> reasonable. However, if you put that sequence of characters into a
> tweet--'ampersand', 'l', 't', and 'semicolon'--then they are rendered
> literally. Therefore, it is impossible to correctly decode a tweet.
> You should be encoding literal ampersands as 'ampersand', 'a', 'm',
> 'p', 'semicolon'.
>
> In other words, either encode the whole tweet, or none of it, when
> providing tweets as data.
>
> Thanks.
>