[twitter-dev] Re: Search result pagination bugs
Sure... It repros for me every time in IE using the steps I outlined above. Do a query for lang=enq=http. Open the next link in a new tab of your browser and compare the ID's. So I just did this from my home PC and here's the condensed output. Notice that on Page 2 not only do I get 3 dupes but I even get a result that should have been on Page 1... I hadn't seen that one before but I'll assume that maybe a different server serviced each request and they're not synced. * for: http://search.twitter.com/search.atom?lang=enq=http feed xmlns:google=http://base.google.com/ns/1.0; xml:lang=en-US xmlns:openSearch=http://a9.com/-/spec/opensearch/1.1/; xmlns=http:// www.w3.org/2005/Atom xmlns:twitter=http://api.twitter.com/; link type=application/atom+xml rel=self href=http:// search.twitter.com/search.atom?lang=enq=http / twitter:warningadjusted since_id, it was older than allowed/ twitter:warning updated2009-04-16T03:25:30Z/updated openSearch:itemsPerPage15/openSearch:itemsPerPage openSearch:languageen/openSearch:language link type=application/atom+xml rel=next href=http:// search.twitter.com/search.atom?max_id=1530963910page=2q=http / ...removed... entry idtag:search.twitter.com,2005:1530963910/id published2009-04-16T03:25:30Z/published ...removed... /entry entry idtag:search.twitter.com,2005:1530963896/id /entry idtag:search.twitter.com,2005:1530963895/id idtag:search.twitter.com,2005:1530963894/id idtag:search.twitter.com,2005:1530963881/id idtag:search.twitter.com,2005:1530963865/id idtag:search.twitter.com,2005:1530963860/id idtag:search.twitter.com,2005:1530963834/id idtag:search.twitter.com,2005:1530963833/id idtag:search.twitter.com,2005:1530963829/id idtag:search.twitter.com,2005:1530963827/id idtag:search.twitter.com,2005:1530963812/id idtag:search.twitter.com,2005:1530963811/id idtag:search.twitter.com,2005:1530963796/id idtag:search.twitter.com,2005:1530963786/id /feed * for: http://search.twitter.com/search.atom?max_id=1530963910page=2q=http feed xmlns:google=http://base.google.com/ns/1.0; xml:lang=en-US xmlns:openSearch=http://a9.com/-/spec/opensearch/1.1/; xmlns=http:// www.w3.org/2005/Atom xmlns:twitter=http://api.twitter.com/; link type=application/atom+xml rel=self href=http:// search.twitter.com/search.atom?max_id=1530963910page=2q=http / updated2009-04-16T03:25:31Z/updated openSearch:itemsPerPage15/openSearch:itemsPerPage openSearch:languageen/openSearch:language link type=application/atom+xml rel=previous href=http:// search.twitter.com/search.atom?max_id=1530963910page=1q=http / link type=application/atom+xml rel=next href=http:// search.twitter.com/search.atom?max_id=1530963910page=3q=http / ...Removed... entry idtag:search.twitter.com,2005:1530963811/id published2009-04-16T03:25:31Z/published ...Duplicate 1... /entry entry idtag:search.twitter.com,2005:1530963803/id published2009-04-16T03:25:29Z/published twitter:langen/twitter:lang ...Not Even In Previous Page... /entry entry idtag:search.twitter.com,2005:1530963796/id published2009-04-16T03:25:29Z/published ...Duplicate 2... /entry entry idtag:search.twitter.com,2005:1530963786/id published2009-04-16T03:25:31Z/published ...Duplicate 3... /entry entry idtag:search.twitter.com,2005:1530963777/id ...First New Result (save the one above)... /entry idtag:search.twitter.com,2005:1530963755/id idtag:search.twitter.com,2005:1530963732/id idtag:search.twitter.com,2005:1530963725/id idtag:search.twitter.com,2005:1530963718/id idtag:search.twitter.com,2005:1530963710/id idtag:search.twitter.com,2005:1530963709/id idtag:search.twitter.com,2005:1530963706/id idtag:search.twitter.com,2005:1530963699/id idtag:search.twitter.com,2005:1530963698/id idtag:search.twitter.com,2005:1530963690/id /feed
[twitter-dev] Re: Search result pagination bugs
Ok... So I think I know what's going on. Well I don't know what's causing the bug obviously but I think I've narrowed down where it is... I just issued the Page 1 or previous query for the above example and the ID's don't match the ID's from the original query. There are extra rows that come back... 3 to be exact. So the pagination queries are working fine. It's the initial query that's busted. It looks like that when you do a pagenation query you get back all rows matching the filter but a query without max_id sometimes drops rows. Well in my case it seems to drop rows everytime... This should get fixed... * for: http://search.twitter.com/search.atom?max_id=1530963910page=1q=http feed xmlns:google=http://base.google.com/ns/1.0; xml:lang=en-US xmlns:openSearch=http://a9.com/-/spec/opensearch/1.1/; xmlns=http:// www.w3.org/2005/Atom xmlns:twitter=http://api.twitter.com/; link type=application/atom+xml rel=self href=http:// search.twitter.com/search.atom?max_id=1530963910page=1q=http / twitter:warningadjusted since_id, it was older than allowed/ twitter:warning updated2009-04-16T03:25:30Z/updated openSearch:itemsPerPage15/openSearch:itemsPerPage openSearch:languageen/openSearch:language link type=application/atom+xml rel=next href=http:// search.twitter.com/search.atom?max_id=1530963910page=2q=http / ...Removed... entry idtag:search.twitter.com,2005:1530963910/id published2009-04-16T03:25:30Z/published /entry entry idtag:search.twitter.com,2005:1530963908/id published2009-04-16T03:25:32Z/published ...Where Did This Come From?... /entry entry idtag:search.twitter.com,2005:1530963898/id published2009-04-16T03:25:30Z/published ...And This?... /entry idtag:search.twitter.com,2005:1530963896/id idtag:search.twitter.com,2005:1530963895/id idtag:search.twitter.com,2005:1530963894/id entry idtag:search.twitter.com,2005:1530963892/id published2009-04-16T03:25:32Z/published ...And This?... /entry idtag:search.twitter.com,2005:1530963881/id idtag:search.twitter.com,2005:1530963865/id idtag:search.twitter.com,2005:1530963860/id idtag:search.twitter.com,2005:1530963834/id idtag:search.twitter.com,2005:1530963833/id idtag:search.twitter.com,2005:1530963829/id idtag:search.twitter.com,2005:1530963827/id idtag:search.twitter.com,2005:1530963812/id /feed
[twitter-dev] Re: Fast140 Dodginess and OAuth Authorization Clarity
So just as an FYI... It's not just fast140.com that's doing this In order of offenderness (the most spam first) its also currently: wefollow.com (5x the spam of fast140.com) fast140.com tinychat.com macheist.com geofollow.com ... and many more I'm sure... On Apr 15, 7:17 pm, Rod Begbie rodbeg...@gmail.com wrote: Hey folks. It's been noted that the fast140.com app, posts a tweet as the authorized user. In fairness, they do disclaim this on their homepage, although users tend not to notice and are surprised to find they've spammed their friends
[twitter-dev] Re: sending DM to all followers?
Jesse, so what is it about mass DMs that bugs you? Just curious? You would only recieve one DM and it would look like any other DM. So what's the issue? I agree with Chad though... There's already a way to do this Update your status... I know where you're going with this feature though and what you really want is groups. But that's just not the Twitter way... -steve
[twitter-dev] Re: Search result pagination bugs
Thanks for the reply Matt... Just as an FYI... I updated my code to track duplicates and then did a sample run over a 5 minute period that once a minute paged in new results for the query http filter:links This resulted in about 11 pages of results each minute and over the 11 pages I saw anywhere from 60 - 150 duplicates so it's not just 3 or 4. My concern isn't really around the extra updates it's the fact that sometimes updates are missing. Anyway... It sounds like you guys are working on it and I just thought I'd share that data point with you. -steve
[twitter-dev] Re: How is lang tracked for queries?
Matt... Did you already fix this? I was going to file a bug on it and I just noticed that now the next and previous links contain the lang param. So do you still need a bug on it for tracking purposes or did you already add one? -steve
[twitter-dev] Re: Search result pagination bugs
So my project is a sort of tweetmeme or twitturly type thing where I'm looking to collect a sample of the links being shared through Twitter. Unlike those projects I don't have a firehose so I have to rely on search. Fortunatly, I don't really need to see every link for my project just a representive sample. The actual query I'm using is http OR www filter:links where the filter:links constraint helps make sure I exclude tweets like can't get http GET to work I don't really care about those. Agreed with this query being a high volume query so maybe it'll never be in sync but that's ok... Now I'm just ignoring the dupes. And to be clear, I have no intention of trying to keep up and use search as a poor mans firehose. What ever rate you guys are comfortable with me hitting you at is what I'll do. If that's one request/minute so be it. Just wanted to get the pagenation working so that I could better control things and that's when I noticed the dupes. -steve (Microsoft Research)
[twitter-dev] Re: TimeLine of 3~4 users
So why can't you do this? http://search.twitter.com/search.atom?lang=enq=from%3Aaplusk+OR+from%3Amashable+OR+from%3Atechcrunch If your queries under 140 characters, you should be able to retrieve the public updates for multiple users using the search API. You just use the from: filter and OR operator. -steve On Apr 20, 1:26 am, Raquibul Islam ranacs...@gmail.com wrote: Hello peter thanks for ur replay . U got me right .Thanks for the advice . Peter Denton wrote: Hi Raquibul, I know what you are asking and it is not possible. Basically, if I may guess, you want to make a group of 3 people you follow and be able to make a call to their stream collated. You can not do this with an API method, however there are plenty of tools like magpie rss that can grab 3 feeds and parse them into one feed, to achieve what you are looking for. On Sun, Apr 19, 2009 at 9:40 PM, Raquibul Islam ranacs...@gmail.com mailto:ranacs...@gmail.com wrote: i saw this before . How can i call with 3 users name together ? Abraham Williams wrote: Use http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_t... for the 3 or 4 users. On Sun, Apr 19, 2009 at 16:06, ranacse05 ranacs...@gmail.com mailto:ranacs...@gmail.com mailto:ranacs...@gmail.com mailto:ranacs...@gmail.com wrote: Hello suppose i'm following 100 users , how can i get the twittes only from 3 or 4 users ??? I meant using the api , so that the page will show the selected users status only . -- Abraham Williams |http://the.hackerconundrum.com Hacker |http://abrah.am|http://twitter.com/abraham Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States -- Regards Rana homepage:http://ranacse05.wordpress.com Bangla job site:http://jobs.mukto.org -- Peter M. Denton www.twibs.comhttp://www.twibs.com i...@twibs.com mailto:i...@twibs.com Twibs makes Top 20 apps on Twitter -http://tinyurl.com/bopu6c -- Regards Rana homepage:http://ranacse05.wordpress.com Bangla job site:http://jobs.mukto.org- Hide quoted text - - Show quoted text -
[twitter-dev] Re: TimeLine of 3~4 users
You can, provided it's under 140 characters and the accounts are public. If you get up to about 5 or more accounts, you'll have to make multiple calls, and you're back to merging them together again. -Chad Right... But even if you have to spread things out across 4 or 5 calls, because you have 20 - 25 users, it's less round trips to the server. I know they're working to combine the Search API's with the other REST API's but at some point it would be great if there was a single query API that could be used to replace all of the other retrieval API's. And hopefully it wouldn't have a 140 character limit :) One thing I really like about programming against Facebook is their query language. FQL rocks! But for openess Twitter rocks! I'd just like to see Twitter get something on a par with FQL. -steve
[twitter-dev] Re: Case is wrong in GeoRSS
I'm actually looking for both uppercase Point and lowercase point so if you fix this on your side I'm ready... On Oct 6, 9:40 pm, steve ick...@gmail.com wrote: You're currently sending Geo Tags as: geo xmlns:georss=http://www.georss.org/georss; georss:Point37.78029 -122.39697/georss:Point /geo But according to the schema for GeoRSS-Simple Point should be lowercased: http://www.georss.org/simple as in: geo xmlns:georss=http://www.georss.org/georss; georss:point37.78029 -122.39697/georss:point /geo The original example you posted to the form had the correct case but what you actually rolled out is different. Was there a reason for the switch? I've updated my code to look for uppercase Point for now... -steve
[twitter-dev] Re: Case is wrong in GeoRSS
no worries... it is a bit confusing... as I said I'm looking for both in my code so either is ok. But others are probably looking for georss:Point so you may just want to send a notification when you change it... On Oct 7, 10:08 am, Raffi Krikorian ra...@twitter.com wrote: hi steve. you're right! we should be using georss:point and not georss:Point! the confusing thing is that in JSON, the type attribute of the geometry object is Point and not point. we'll ship a fix for that. thanks! You're currently sending Geo Tags as: geo xmlns:georss=http://www.georss.org/georss; georss:Point37.78029 -122.39697/georss:Point /geo But according to the schema for GeoRSS-Simple Point should be lowercased: http://www.georss.org/simple as in: geo xmlns:georss=http://www.georss.org/georss; georss:point37.78029 -122.39697/georss:point /geo The original example you posted to the form had the correct case but what you actually rolled out is different. Was there a reason for the switch? I've updated my code to look for uppercase Point for now... -steve -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi- Hide quoted text - - Show quoted text -
