Random Tweets are back and in a bad way
@boulderbars, @denverbars, @losangelesbars all have random tweets showing up again. Please look into it ASAP!!!!
Comments are currently closed for this discussion. You can start a new one.
@boulderbars, @denverbars, @losangelesbars all have random tweets showing up again. Please look into it ASAP!!!!
Comments are currently closed for this discussion. You can start a new one.
2 Posted by chris on 20 Apr, 2010 11:21 AM
We've deleted most of the bad tweets but left two for you to investigate.
@denverbars http://twitter.com/denverbars/status/12501891361
@losangelesbars http://twitter.com/losangelesbars/status/12474443719
Support Staff 3 Posted by Josh Owens on 20 Apr, 2010 02:12 PM
Chris,
All my logs seem to point at this being a search problem, not a tweethopper issue. I show we parse the feed "http://search.twitter.com/search.atom?q=%23denverbars+from%3ADenver..." and the entry "http://twitter.com/henriqueramos/statuses/12501872546" shows up as something the feed gave us.
I will be checking with the twitter search api team to see if they can give us more insight.
4 Posted by chris on 20 Apr, 2010 05:26 PM
The user we have in that search feed is @DenverUncommon. The tweet that
got retweeted was from user @henriqueramos.
If I view that feed now, I don't see that other user's tweets in the feed.
Chris
Support Staff 5 Posted by Josh Owens on 20 Apr, 2010 06:41 PM
Right,
I get that. But my logs show that I parsed the feed for @DenverUncommon, then I found an entry from @henriqueramos, parsed it and tweeted it out. I added variable checking to the logs to show the job id and source id at every step of the job and everything is matching up, there is no "Variable bleeding or mixing"
That leads me to believe it is on the twitter side of things, they accidentally return a tweet they shouldn't in the feeds we see and parse it, then post it. I am trying to gather as much data as I can before I contact twitter to investigate,
6 Posted by chris on 20 Apr, 2010 06:45 PM
Sounds like you have a good idea what's going on. How long before
Twitter can tell us what's up?
Support Staff 7 Posted by Josh Owens on 20 Apr, 2010 07:27 PM
I've emailed a contact I have on the API team. I will let you know when I hear something back. Hopefully he doesn't take too long to respond, he is on my railsconf API talk panel (http://en.oreilly.com/rails2010/public/schedule/detail/14502).
--Josh
8 Posted by Chris on 26 Apr, 2010 10:57 PM
Any word? We just had more tweets show for @chicagopubs, @boulderbars & @neworleansbars.
Support Staff 9 Posted by Josh Owens on 28 Apr, 2010 01:31 PM
Chris,
The api team informed me that it is likely an issue on the search results end, but they doubted it could be tracked down very well. They suggested switching to the streaming api and to track keywords there.
Would you be interested in trying this approach? I could get a small beta test together for you.
10 Posted by wendy on 05 May, 2010 02:20 PM
Is the problem still occurring Chris?
11 Posted by Chris on 05 May, 2010 10:08 PM
Not recently. You can close the ticket if you wish.
Support Staff 12 Posted by Paolo Miguel on 30 Jan, 2011 09:58 AM
Chris,
Thanks for contacting us, we are cleaning up old tickets in our system. If you are still having this issue, please open a new ticket and give us the exact details of your issue.
Paolo Miguel closed this discussion on 30 Jan, 2011 09:58 AM.