FYI, it looks like the stray ampersands are still floating around in the
feeds of some Twitter lists. Still causes validation errors. Maybe the bug
fix is propagating throughout Twitter?
While we wait for this to be resolved, this regex might help any developer
who wants things to work on their
From what I can see, it looks like this is fixed now.
Thanks!
-Brandon
On Mon, May 10, 2010 at 9:46 AM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Hi Claudia,
Looks like I was mistaken and this bugfix hasn't hit the server yet. It
should go out sometime early this week.
Hello !
Thanks for the feedback.
See, for example, the url that my application is using:
http://twitter.com/statuses/user_timeline.atom?page=1user_id=54210117count=200since_id=12941651260
Thanks
Claudia Antonini Vitiello Callegari
São Paulo - Brasil
On 7 maio, 11:00, Taylor Singletary
Hello!
Sorry for my English.
I'm also having the same problem, has agumar forecast for this
problem?
Thanks
Claudia Antonini Vitiello Callegari
São Paulo - Brasil
On 4 maio, 12:33, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Brandon,
Thanks for the bug report. We'll work on
Hi Claudia,
Could you paste a little bit of the invalid ATOM feed you are still
receiving it? This problem should be fixed now, but it's possible that some
persistent cache elements may still have the unencoded ampersand within
them.
Taylor Singletary
Developer Advocate, Twitter
