I've been building a small app for twitter, and I've noticed that my
XML feed isn't being updated at all until I post. Am I to assume that
this should be expected behavior? It wasn't like this prior to today.
Also of note, my XML feed had apparently been replaced with someone
else's? I can't even begin to describe the weird behavior I've been
having today. The feed did not switch over for a good 3-4 hours.
Any help would be appreciated. I've noticed the same behavior in
twitteroo, s I don't think it's my code, but hey you never know, right?
This is probably related to the API response caching that we deployed
yesterday (see my email to this list from last night).
--
Alex Payne
Obvious
http://twitter.com/al3x
I'm not seeing friends_timeline update until after I post a message. I
didn't think it was related to caching because I only figured it out
after I waited approx 2 hours to post another message. Only after I
posted my message did the actual XML feed itself update.
Thanks for helping :)
Jason
On Apr 5, 3:09 pm, Alex Payne <a...@al3x.net> wrote:
> Could you please be specific about which feeds aren't updating for
> you? Is it your friends_timeline, your user_timeline, or something
> else?
>
> This is probably related to the API response caching that we deployed
> yesterday (see my email to this list from last night).
>
> --
> Alex Payne
> Obvioushttp://twitter.com/al3x
Today I started getting even weirder behavior with my app, Spaz.
My friends&me timeline
(http://twitter.com/statuses/friends_timeline.xml) stopped updating
about 5 hours ago. I've posted a couple new tweets from Spaz, but I
can't read them in Spaz (though they do show up on the web site).
Retrieving my timeline (user_timeline.xml) is even weirder: I am
getting the messages for DDoak, not the user I'm logged in as.
Doesn't matter what user I'm logged in as. This happened at work and
at home, on two different machines.
If I use curl from the command line in OS X, everything works fine.
I can save out the headers sent and headers retrieved for debugging if
that would help. I'd chalk it up to something ridiculous I did in my
code, but I'm pretty darn sure I didn't change anything in the XML
retrieval logic, and I don't do any caching on my end (yet).
--
- Ed Finkler
http://funkatron.com/
--
Alex Payne
Obvious
http://twitter.com/al3x
I don't know if I'm having the same issues, but I'm seeing an update
problem too.
My friends_timeline:
http://twitter.com/raghos/with_friends
I definitely have some updates from friends missing in my timeline,
and at least one twit of mine dissapeared from my own timeline,
although I can see it in my friends'.
This is all quite bizarre. I'll be happy to help debug this.
Carlos
I would like to add a few more notes to this current thread.
The XML api caching on the following call is causing issues.
http://twitter.com/statuses/friends_timeline.xml
I can see that the friends_timeline.xml will not update until my
application posts to
http://twitter.com/statuses/update.xml with a new status.
Once the update has been been made the friends_timeline.xml now
updates correctly and shows the latest posts sitting there (I can see
what posts are missing via twitter.com) that have not been coming
through.
Last night the twitter api had cached the friends timeline for over 40
mins and still will not update with the correct xml with the latest
posts. Again sending an update fixed this.
I have included a screenshot of my firefox screen showing the latest
posts
http://groups.google.com/group/twitter-development-talk/web/My+Screen.png
And an output from Charles showing the current requests at this same
time showing my last tweet, but it was missing the latest changes that
should have appeared above it.
http://groups.google.com/group/twitter-development-talk/web/CharlesDebug.png
Hope this helps,
Thanks for listening.
John Ballinger