[twitter-dev] Re: White listing rejected - no reason
Hi Chad, I already submitted whitelisting request since my hosting company changed my outgoing IP address without notifying me which is very annoying since i can already see some errors comming from most active users. My new IP is 99.198.100.139 . Could you please take a look or should I send a mail? Thanks! On Oct 30, 12:58 am, Chad Etzel c...@twitter.com wrote: Email your username to a...@twitter.com and we can look up the reason and help you figure things out. -Chad On Thu, Oct 29, 2009 at 7:50 PM, Arnaldo de Moraes Pereira eggh...@gmail.com wrote: Hello, I've submitted my application to be on the white list, but this request has been rejected, without a reason. For some weeks now, I've been receiving 400 Bad Request http responses frequently and didn't reach the rate limit, not once ( http://apiwiki.twitter.com/Rate-limitingsays the app would receive 503 if the rate limit was reached). I just can't fetch fresh updates (just old, delayed ones), can't get directions here to understand why this is happening and now I can't be white listed. I'd ask for an answer and a direction here, but since that seems hard to get: may please somebody tell me anything useful about this situation? Thanks, -- Arnaldo M Pereira- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Oauth API not updating statuses consistently
On Mon, Nov 02, 2009 at 09:38:48PM -0800, Enlai wrote: Sorry if this is a dumb question but I can't find an answer online. This is happening right now so I thought I'd see if something is up with the API. Sometimes, I get no response from the status update post and other times, I get a response with a successful post result. However, the text in the post shows the previous successful post rather than the one I just posted. What does this mean? Has some rate been tripped? This has been noted by a few of us since mid-October. Twitter changed the API behaviour such that a status update will fail silently and return the user's most recent prior status in two (known) cases: - If the text of the update exceeds 140 characters. (This is a change from the documented behaviour of truncating the text to 140 characters.) - If the text of the update is a duplicate of *any* previous status update within an as-yet-unknown time period. I know from my own experience that the time period is at least an hour and I suspect that it it much longer, perhaps even unlimited. (This is a change from the documented behaviour of only rejecting duplicates when consecutive.) There has been a comment made here on the list to the effect that Twitter intends to respond with an error code in these cases rather than failing silently, but no indication was given regarding an expected timeframe. Until Twitter does get around to telling us when updates have been rejected, two basic approaches have been suggested for detecting these silent failures: - Store the highest status ID which has been seen by your application. When you submit an update, check the ID of the returned status. If the returned ID is less than the stored ID, you know the update was rejected and an old status was returned. - Compare the text of the sent status to the text of the returned status to see if they match. I prefer the ID-based method, as the text-based method is subject to both false positives (if Twitter applies bit.ly shortening, you'll think it failed unless you remember to ignore URLs when comparing the text) and false negatives (if the update is a duplicate of the user's most- recent status, the text will match even though the update failed), but YMMV. -- Dave Sherohman
[twitter-dev] Re: Is image shrinking broken?
It's broken. Add a star here: http://code.google.com/p/twitter-api/issues/detail?id=1158 On Tue, Nov 3, 2009 at 9:54 PM, janole s...@mobileways.de wrote: Would be cool to have this fixed as soon as possible. I'm getting a lot of complaints because my mobile client silently discards any oversized avatars ( 10kB .) It's not a good idea to download dozens of 200 kB avatars if you're not on a flatrate mobile data plan ;-) Also, scaling all those avatars on the mobile phone takes quite some time ... @janole On 3 Nov., 06:25, TCI ticoconid...@gmail.com wrote: I am noticing an increase in the number of avatar images which do not get shrinked in the smaller versions. It is most noticeable in the twitter.com homepage as the images load very slowly from top to bottom. How are your clients handling this? In my case I am assuming the shrinking is working and therefore my page load times are being affected. Example: http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4...http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4...http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4. .. are all the same...
[twitter-dev] Re: Lists API
From what I gathered as soon as you could access lists on the Web interface, you also gained access to the List APIs too On Nov 3, 6:08 am, Michael Steuer mste...@gmail.com wrote: Well, I¹m in no beta, but it all seems to be accessible and working.. According to Marcel Molina, the API went public/open last Thursday. I guess it wasn¹t announced (not on the group at least). On 11/2/09 9:57 AM, Sean Scott sean@gmail.com wrote: List API is in Beta. If you're in the beta you can play with it. If you're not in the Beta you can't play with it just yet On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer mste...@gmail.com wrote: With all the discussions on this mailing list about the Lists API, can someone please confirm, is the API now available to all developers or all of you in some sort of preferred position? Thanks, Michael.
[twitter-dev] Streaming Api - Keywords matched
Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Search API: max_id and page parameters giving very weird results
I've been trying to write a script to use the max_id parameter to loop through all 15 pages of results (with 100 results per page) without getting in troubles with grabbing the same tweet multiple times. Every time I do so, I find that not only are there a couple of duplicates on page 1 and 2, but also that the last tweet on page 1 is well further into the future, and has a lower ID, than a bunch of tweets on page 2. For example, consider these two, both with the same max_id but page = 1 and page = 2 respectively: http://search.twitter.com/search?rpp=100page=1geocode=-40.900557,174.885971,1000kmmax_id=5379894247 http://search.twitter.com/search?rpp=100page=2geocode=-40.900557,174.885971,1000kmmax_id=5379894247 (Or if you prefer json links which are what I am actually using, but I see the same thing on the above ones which are easier to describe: http://search.twitter.com/search.json?q=rpp=100geocode=-40.900557,174.885971,1000kmpage=1max_id=5379894247 Request: http://search.twitter.com/search.json?q=rpp=100geocode=-40.900557,174.885971,1000kmpage=2max_id=5379894247) The first result on page 2 above was posted about 4 hours before the last tweet on page 1. There are also duplicates, eg AshleyGray00: Fireworks! I've been trying to figure this bug out for a while as I'm sure I'm missing something obvious but I'm completely stumped. Does anyone have any clue what is going on here? The only other threads I have found are about people trying to combine since_id and max_id which I know is not allowed, so I can't find anyone else having similar problems.
[twitter-dev] Re: Lists API
Yep, on for everyone. Just waiting and hoping for whitelisting so I can actually release the website I built around the API. Right now I can't make enough calls to keep its database fresh.
[twitter-dev] Re: Oauth API not updating statuses consistently
Thanks for the prompt response. Yes, the request is timing out with no response right now. We've seen sporadic behavior like this the last few days and we've built in retry mechanisms so messages aren't getting lost. As far as I understand, posts of statuses aren't being rate limited so this shouldn't be a problem. Individual account rate limits aren't being hit (we tested one account and when the rate per day was hit, we were getting actual error responses regarding this limit). However, the retry mechanisms are failing because the post succeeds, yet the text being posted is not the one we're posting. Instead, we get the post from the previous successful message about 2 hours ago. Sent for posting: Hv 2 catch up on the scriptures: He has delivered us from the power of darkness and conveyed is into the kingdom of the Son of His love. COLOSSIANS 1:13 The response shows the succesful post, but the text is the previous post from 20 minutes ago: texthi/text Entire response is below. Thanks, Enlai Response: ?xml version=1.0 encoding=UTF-8? status created_atTue Nov 03 05:39:55 + 2009/created_at id5384817467/id texthi/text sourcelt;a href=quot;http://www.mogotxt.comquot; rel=quot;nofollowquot;gt;MogoTXTlt;/agt;/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/in_reply_to_user_id favoritedfalse/favorited in_reply_to_screen_name/in_reply_to_screen_name user id48108108/id nameEnlai Test/name screen_nameenlaitest/screen_name location/location description/description profile_image_urlhttp://a3.twimg.com/profile_images/277692677/enlai_elf_normal.jpg/profile_image_url url/url protectedfalse/protected followers_count143/followers_count profile_background_color9ae4e8/profile_background_color profile_text_color00/profile_text_color profile_link_colorff/profile_link_color profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color profile_sidebar_border_color87bc44/profile_sidebar_border_color friends_count393/friends_count created_atWed Jun 17 20:43:25 + 2009/created_at favourites_count0/favourites_count utc_offset/utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1257210731/images/themes/theme1/bg.png/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count58/statuses_count notificationsfalse/notifications geo_enabledfalse/geo_enabled verifiedfalse/verified followingfalse/following /user geo/ /status Enlai Raffi Krikorian wrote: Hi Enlai. Can you provide more information, please? If you experience times that there is no response, do you mean that the request is timing out? As for getting a successful response, yet the status not updating could be caused by sending tweets with the same text as a tweet you sent recently. Either way, I don't know which of these, if any, are afflicting you. Can you provide more information as to what precisely you are issuing to the API, and what precisely is it responding with? Thanks! On Nov 2, 2009, at 9:45 PM, Enlai en...@3jam.com wrote: Sorry if this is a dumb question but I can't find an answer online. This is happening right now so I thought I'd see if something is up with the API. Sometimes, I get no response from the status update post and other times, I get a response with a successful post result. However, the text in the post shows the previous successful post rather than the one I just posted. What does this mean? Has some rate been tripped? Thanks Enlai
[twitter-dev] Re: Draft of List API documentation
It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call DELETE (which only GET and POST). So, will twitter provide POST or GET method API to delete? Thanks On Oct 16, 3:04 pm, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. You may notice this API is a bit of a departure from the rest of the API. It's a bit more, errr, REST than the rest. First off, here's the current payload for alist: ?xml version=1.0 encoding=UTF-8? list id1416/id nametall people/name full_name@noradio/tall-people/full_name slugtall-people/slug subscriber_count0/subscriber_count member_count3/member_count uri/noradio/tall-people/uri modepublic/mode user id3191321/id nameMarcel Molina/name screen_namenoradio/screen_name locationSan Francisco, CA/location descriptionEngineer at Twitter on the @twitterapi team, obsessed with rock climbing amp; running. In a past life I was a member of the Rails Core team./description profile_image_urlhttp://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no.../profile_image_url urlhttp://project.ioni.st/url protectedfalse/protected followers_count40059/followers_count profile_background_color9AE4E8/profile_background_color profile_text_color33/profile_text_color profile_link_color0084B4/profile_link_color profile_sidebar_fill_colorDDFFCC/profile_sidebar_fill_color profile_sidebar_border_colorBDDCAD/profile_sidebar_border_color friends_count354/friends_count created_atMon Apr 02 07:47:28 + 2007/created_at favourites_count131/favourites_count utc_offset-28800/utc_offset time_zonePacific Time (US amp; Canada)/time_zone profile_background_image_urlhttp://a1.twimg.com/profile_background_images/18156348/jessica_tiled/profile_background_image_url profile_background_tiletrue/profile_background_tile statuses_count3472/statuses_count notificationsfalse/notifications geo_enabledtrue/geo_enabled verifiedfalse/verified followingfalse/following /user /list === Lists === POST '/:user/lists.:format' Creates a newlistfor the authenticated user. Parameters: * name: the name of thelist. (required) * mode: whether yourlistis public of private. Values can be 'public' or 'private'. Public by default if not specified. (optional) Usage notes: :user in the url should be the screen name of the user making the request to create thelist Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=tall peoplemode=privatehttp://twitter.com/noradio/lists.xml POST/PUT '/:user/lists/:list_slug.:format' Updates the specifiedlist. Takes the same parameters as the create resource at POST '/:user/lists.:format' (:name and :mode). Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=giantsmode=publichttp://twitter.com/noradio/lists/tall-people.xml GET '/:user/lists.:format' Lists your lists. Supported format: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml GET '/:user/lists/memberships.:format'Listthe lists the specified user has been added to. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/memberships.xml DELETE '/:user/lists/:list_slug.:format' Delete the specifiedlistowned by the authenticated user. Parameters: * list_slug: the slug of thelistyou want to delete. (required) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -X DELETEhttp://twitter.com/noradio/lists/tall-people.xml GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specifiedlist. Parameters: * list_slug: the slug of thelistyou want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml GET '/:users/lists/:list_slug.:format' Show a specificlistyou can use the new resource. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people.xml ===Listmembers === POST '/:user/:list_slug/members.:format' Add a member to alist. Parameters: * id: the id of the user you want to add as a member to thelist. (required) Usage notes: The :list_slug portion of the request path should be the slug of thelistyou want to add a member to. Supported formats: xml,
[twitter-dev] Re: Oauth API not updating statuses consistently
Dave, thanks a bunch. You called it. Looks like the update was greater than 140 characters and the API was failing silently. Thanks! Enlai Dave Sherohman wrote: On Mon, Nov 02, 2009 at 09:38:48PM -0800, Enlai wrote: Sorry if this is a dumb question but I can't find an answer online. This is happening right now so I thought I'd see if something is up with the API. Sometimes, I get no response from the status update post and other times, I get a response with a successful post result. However, the text in the post shows the previous successful post rather than the one I just posted. What does this mean? Has some rate been tripped? This has been noted by a few of us since mid-October. Twitter changed the API behaviour such that a status update will fail silently and return the user's most recent prior status in two (known) cases: - If the text of the update exceeds 140 characters. (This is a change from the documented behaviour of truncating the text to 140 characters.) - If the text of the update is a duplicate of *any* previous status update within an as-yet-unknown time period. I know from my own experience that the time period is at least an hour and I suspect that it it much longer, perhaps even unlimited. (This is a change from the documented behaviour of only rejecting duplicates when consecutive.) There has been a comment made here on the list to the effect that Twitter intends to respond with an error code in these cases rather than failing silently, but no indication was given regarding an expected timeframe. Until Twitter does get around to telling us when updates have been rejected, two basic approaches have been suggested for detecting these silent failures: - Store the highest status ID which has been seen by your application. When you submit an update, check the ID of the returned status. If the returned ID is less than the stored ID, you know the update was rejected and an old status was returned. - Compare the text of the sent status to the text of the returned status to see if they match. I prefer the ID-based method, as the text-based method is subject to both false positives (if Twitter applies bit.ly shortening, you'll think it failed unless you remember to ignore URLs when comparing the text) and false negatives (if the update is a duplicate of the user's most- recent status, the text will match even though the update failed), but YMMV.
[twitter-dev] Re: Firehose Sample Geo Only
Thought so! Is it something you're thinking of implementing at any stage? On 3 Nov 2009, at 01:52, Raffi Krikorian wrote: hi scott. unfortunately, not currently. right now you need to filter through the statuses to see ones that have a populated geo tag. Hi Folks, After seeing Kal's post earlier, I was wondering its its possible to filter a set of statuses only to be returned if they have geodata (other statuses aren't useful to me for this project). Is this possible?
[twitter-dev] Need Help
Hi, I wanna know can we use PIN# authentication for web applications?? As far as my understanding PIN# authentication can be used only in desktop applications... Any help will be highly appreciated. Regards Aaqib Iqbal
[twitter-dev] Problems getting other people's friend list or follower list
Hi, just signed up for the forum and posting a new topic. Gotta love
people like me, but I really need the help.
When I make a call to the API like this:
$user1results = $to-OAuthRequest('https://twitter.com/friends/
ids/'.$user1.'.json', array(), 'GET');
or this:
$user1results = $to-OAuthRequest('https://twitter.com/followers/
ids/'.$user1.'.json', array(), 'GET');
and pass the $user1 variable from a form entry, no matter what it is,
it always returns MY username's friend list or follower list.
Am I crazy, I thought you could request other people's info as long as
your account had access to that information on Twitter. But no matter
what I do, even hard-coding somebody's username in there, it still
only pulls my information.
7am and headed out to work, but I was up to 3am this morning working
on this to no avail. I really am stuck.
Let me know if you want to help me but need more code examples. I am
using the standard OAuth library linked to from twitter's apikiwi by:
Abraham Williams (abra...@abrah.am) http://abrah.am if that helps any.
Thanks to anybody for any assistance you can offer!
[twitter-dev] Re: Streaming Api - Keywords matched
I agree with the idea, since I too have this need, but I think that you'll still need to check the existence of matches in filtered stream results. The algorithm used by this API doesn't always return what you'd expect or need, such as making sure the matches are separate words, or they are used in the right context or position. Even if the API told me what it matched, I'd still want to parse each tweet myself to prevent false positives. On Nov 3, 4:53 am, Fabien Penso fabienpe...@gmail.com wrote: Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Re: Draft of List API documentation
It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call DELETE (which only GET and POST). So, will twitter provide POST or GET method API to delete? Thanks I'd like to second this (I asked for it a while back, but never heard anything). There are other environments where DELETE may not be possible to issue as a method. Since the other API deletion methods offer POST as a stub to delete, I think it would be orthogonal to offer it here too. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- People are weird. -- Law Order SVU ---
[twitter-dev] Re: Streaming Api - Keywords matched
The assumption is that client services will, in any case, have to parse and route statuses to potentially multiple end-users. Providing this sort of hint wouldn't eliminate the need to parse the status and would likely result in duplicate effort. We're aware that we are, in some use cases, externalizing development effort, but the uses cases for the Streaming API are so many, that it's hard to define exactly how much this feature would help and therefore how much we're externalizing. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 1:53 am, Fabien Penso fabienpe...@gmail.com wrote: Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Re: Need Help
don't supply a callback function to twitter, and you'll get a pin. Why would you want to use Pin-based auth for the web, though? On Tue, Nov 3, 2009 at 03:22, mr.aaqib - IIUI mr.aa...@gmail.com wrote: Hi, I wanna know can we use PIN# authentication for web applications?? As far as my understanding PIN# authentication can be used only in desktop applications... Any help will be highly appreciated. Regards Aaqib Iqbal -- Internets. Serious business.
[twitter-dev] broken refresh link in search api results?
I used to be able to grab the refresh link out of an xml document returned from a query like http://search.twitter.com/search.atom?q=iphone . however, now, after two iterations of grabbing the refresh link, I get 403s back from search.twitter.com. the refresh link appears to be broken/poorly encoded. steps to reproduce via curl: request 1: http://search.twitter.com/search.atom?q=iphone - works fine request 2: http://search.twitter.com/search.atom?q=iphoneamp;since_id=5393893759 - this url came from the refresh link within response body's xml document returned in request 1. - works fine request 3: http://search.twitter.com/search.atom?amp%3Bsince_id=5393893759amp;q=iphoneamp;since_id=5393907862 - this url came from the refresh link within response body's xml document returned in request 2. - results in a 403 from the server.
[twitter-dev] Re: Draft of List API documentation
Does Air not support REST properly? For an application to be RESTful it should support GET, POST, PUT and DELETE On Nov 3, 2:14 pm, Cameron Kaiser spec...@floodgap.com wrote: It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call DELETE (which only GET and POST). So, will twitter provide POST or GET method API to delete? Thanks I'd like to second this (I asked for it a while back, but never heard anything). There are other environments where DELETE may not be possible to issue as a method. Since the other API deletion methods offer POST as a stub to delete, I think it would be orthogonal to offer it here too. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- People are weird. -- Law Order SVU ---
[twitter-dev] Re: Suggestion for User record
This would be so useful. +1
[twitter-dev] Re: Streaming Api - Keywords matched
The Streaming API and the Search indexer both tee off the same point in the new status event pipeline. New statuses are born in the web containers and queued for a cluster of processes that begin the offline processing pipeline. This first process does many things, including routing statuses to various subsystems (timelines, SMS, various backing stories, etc. etc.). This process also determines if the updating user is public or protected and if they are filtered from search. If the user is both public and unfiltered, the status is enqueued to both Search and Streaming. See also: http://apiwiki.twitter.com/Streaming-API-Documentation#ResultQualitynbsp The Streaming API then syndicates all these statuses. The Search system may or may not sort, filter, and otherwise rank statuses for relevance based on various heuristics, including, but not limited to: phase of the moon, state of tides, the DJIA, etc. Roughly: Complete corpus search: Streaming Low-latency results: Streaming Accurate keyword counts: Streaming (tally both statuses and limit messages) Complex queries: Search Historical queries: Search -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 11:02 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: It would help if John Kalucki (hello) would clarify the difference between what is visible via streaming as opposed to what is visible via search. I've been operating under the assumption that streaming is warranted when an app needs a different or more powerful search than the current one (e.g. nested boolean expressions), or is interested in seeing tweets before they are filtered out by twitter's spam detection (dealing with the tweet removal protocol, etc).) As a developer it would help us if you could paint out what the twitter data pipeline looks like, and where the various apis plug in, so that we know what we get when we plug in there. I assume, for instance, that search is farther downstream than the various firehose/stream apis, but I've little idea (or documentation) on what steps the data is as it moves down the pipe Would Twitter be open to shedding some light?. jeffrey greenberg tweettronics.com On Nov 3, 9:59 am, Fabien Penso fabienpe...@gmail.com wrote: I agree, however it would help a lot because instead of doing : for keyword in all_keywords if tweet.match(keyword) //matched, notify users end end we could do for keyword in keywords_matched // same as above end for matching 5,000 keywords, it would bring the first loop from 5,000 to probably 1 or 2. You know what you matched, so it's quiet easy for you just to include row data of matched keywords, I don't need anything fancy. Just space separated keywords would help _so much_. On Tue, Nov 3, 2009 at 3:15 PM, John Kalucki jkalu...@gmail.com wrote: The assumption is that client services will, in any case, have to parse and route statuses to potentially multiple end-users. Providing this sort of hint wouldn't eliminate the need to parse the status and would likely result in duplicate effort. We're aware that we are, in some use cases, externalizing development effort, but the uses cases for the Streaming API are so many, that it's hard to define exactly how much this feature would help and therefore how much we're externalizing. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 1:53 am, Fabien Penso fabienpe...@gmail.com wrote: Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Search operators not working properly?
I tried putting together tweets about an event today (the release of a beer) but ran into issues when trying to combine multiple operators. For instance, how would I combine these two into one search query string? from:deschutesbeer abyss deschutes abyss from:deschutesbeer abyss OR deschutes beer = doesn't work (from:deschutesbeer abyss) OR (deschutes beer) = doesn't work This should allow me to search for instances of abyss from @deschutesbeer and to search for any user who tweets both deschutes and abyss (not necessarily a phrase) in a tweet. Seems so basic yet I can't do it?
[twitter-dev] Re: Draft of List API documentation
A work around for environments that don't support the DELETE request method is, I believe, to pass a parameter called _method with the value DELETE. In other words _method=DELETE. On Mon, Nov 2, 2009 at 11:26 PM, wilfred yau wld991...@gmail.com wrote: It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call DELETE (which only GET and POST). So, will twitter provide POST or GET method API to delete? Thanks On Oct 16, 3:04 pm, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. You may notice this API is a bit of a departure from the rest of the API. It's a bit more, errr, REST than the rest. First off, here's the current payload for alist: ?xml version=1.0 encoding=UTF-8? list id1416/id nametall people/name full_name@noradio/tall-people/full_name slugtall-people/slug subscriber_count0/subscriber_count member_count3/member_count uri/noradio/tall-people/uri modepublic/mode user id3191321/id nameMarcel Molina/name screen_namenoradio/screen_name locationSan Francisco, CA/location descriptionEngineer at Twitter on the @twitterapi team, obsessed with rock climbing amp; running. In a past life I was a member of the Rails Core team./description profile_image_urlhttp://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no.../profile_image_url urlhttp://project.ioni.st/url protectedfalse/protected followers_count40059/followers_count profile_background_color9AE4E8/profile_background_color profile_text_color33/profile_text_color profile_link_color0084B4/profile_link_color profile_sidebar_fill_colorDDFFCC/profile_sidebar_fill_color profile_sidebar_border_colorBDDCAD/profile_sidebar_border_color friends_count354/friends_count created_atMon Apr 02 07:47:28 + 2007/created_at favourites_count131/favourites_count utc_offset-28800/utc_offset time_zonePacific Time (US amp; Canada)/time_zone profile_background_image_urlhttp://a1.twimg.com/profile_background_images/18156348/jessica_tiled/profile_background_image_url profile_background_tiletrue/profile_background_tile statuses_count3472/statuses_count notificationsfalse/notifications geo_enabledtrue/geo_enabled verifiedfalse/verified followingfalse/following /user /list === Lists === POST '/:user/lists.:format' Creates a newlistfor the authenticated user. Parameters: * name: the name of thelist. (required) * mode: whether yourlistis public of private. Values can be 'public' or 'private'. Public by default if not specified. (optional) Usage notes: :user in the url should be the screen name of the user making the request to create thelist Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=tall peoplemode=privatehttp://twitter.com/noradio/lists.xml POST/PUT '/:user/lists/:list_slug.:format' Updates the specifiedlist. Takes the same parameters as the create resource at POST '/:user/lists.:format' (:name and :mode). Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=giantsmode=publichttp://twitter.com/noradio/lists/tall-people.xml GET '/:user/lists.:format' Lists your lists. Supported format: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml GET '/:user/lists/memberships.:format'Listthe lists the specified user has been added to. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/memberships.xml DELETE '/:user/lists/:list_slug.:format' Delete the specifiedlistowned by the authenticated user. Parameters: * list_slug: the slug of thelistyou want to delete. (required) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -X DELETEhttp://twitter.com/noradio/lists/tall-people.xml GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specifiedlist. Parameters: * list_slug: the slug of thelistyou want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml GET '/:users/lists/:list_slug.:format' Show a specificlistyou can use the new resource. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people.xml ===Listmembers === POST '/:user/:list_slug/members.:format'
[twitter-dev] Re: Streaming Api - Keywords matched
I agree, however it would help a lot because instead of doing : for keyword in all_keywords if tweet.match(keyword) //matched, notify users end end we could do for keyword in keywords_matched // same as above end for matching 5,000 keywords, it would bring the first loop from 5,000 to probably 1 or 2. You know what you matched, so it's quiet easy for you just to include row data of matched keywords, I don't need anything fancy. Just space separated keywords would help _so much_. On Tue, Nov 3, 2009 at 3:15 PM, John Kalucki jkalu...@gmail.com wrote: The assumption is that client services will, in any case, have to parse and route statuses to potentially multiple end-users. Providing this sort of hint wouldn't eliminate the need to parse the status and would likely result in duplicate effort. We're aware that we are, in some use cases, externalizing development effort, but the uses cases for the Streaming API are so many, that it's hard to define exactly how much this feature would help and therefore how much we're externalizing. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 1:53 am, Fabien Penso fabienpe...@gmail.com wrote: Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Re: List API : statuses timeline and count parameter
cool :) thx a lot ! On Nov 4, 2:34 am, Marcel Molina mar...@twitter.com wrote: Oh. I've realized that all the options *except* for count are supported. Fixing that now. Should be deployed to production in the next day or so. Thanks for reporting this. On Tue, Nov 3, 2009 at 5:01 PM, Marcel Molina mar...@twitter.com wrote: You can use all the same parameters as are available in the other status timeline resources (e.g. max_id, count, since_id, etc). On Tue, Nov 3, 2009 at 4:07 PM, stephane stephane.philipa...@gmail.com wrote: Hi guys ! Is there a way (or planned method) to get more than 20 statuses per list timeline API call ? apparently there is no equivalent to the count parameter. Best, Stephane Philipakis @sphilipakis www.twazzup.com -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] API requests log
Sometimes, I find myself hitting the 150 API requests limit. The problem is, I don't change my normal behavior (it works fine for hours, and then it suddenly hits the limit). I wonder if there is a way to know what is the offending app? Disabling all the OAuth Permission is not a good way as I use the apps. (By the way, there should be a enable/disable option). Jose
[twitter-dev] Field sizes documented as maximum character counts vs number of utf8 encoded bytes
The user description field (for instance) is documented as a maximum of 160 characters, but how many bytes is that exactly? If we get bytes from twitter that are utf-8 bytes, will we then see a maximum number of how many bytes per char, 1, 2, 3 or 4 bytes/char ? This matters when spec'ing a database field size, for instance. I'm asking whether Twitter is talking characters or 'utf-8 encoded bytes when it is specing a field in the docs? thanks in advance... (would appreciate it if this were clarified in the docs)
[twitter-dev] Re: Is image shrinking broken?
Added my star. If you are also affected add yours... TCI On Nov 3, 3:09 am, Tim Haines tmhai...@gmail.com wrote: It's broken. Add a star here:http://code.google.com/p/twitter-api/issues/detail?id=1158 On Tue, Nov 3, 2009 at 9:54 PM, janole s...@mobileways.de wrote: Would be cool to have this fixed as soon as possible. I'm getting a lot of complaints because my mobile client silently discards any oversized avatars ( 10kB .) It's not a good idea to download dozens of 200 kB avatars if you're not on a flatrate mobile data plan ;-) Also, scaling all those avatars on the mobile phone takes quite some time ... @janole On 3 Nov., 06:25, TCI ticoconid...@gmail.com wrote: I am noticing an increase in the number of avatar images which do not get shrinked in the smaller versions. It is most noticeable in the twitter.com homepage as the images load very slowly from top to bottom. How are your clients handling this? In my case I am assuming the shrinking is working and therefore my page load times are being affected. Example: http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4 .. are all the same...
[twitter-dev] Re: List API : statuses timeline and count parameter
You can use all the same parameters as are available in the other status timeline resources (e.g. max_id, count, since_id, etc). On Tue, Nov 3, 2009 at 4:07 PM, stephane stephane.philipa...@gmail.com wrote: Hi guys ! Is there a way (or planned method) to get more than 20 statuses per list timeline API call ? apparently there is no equivalent to the count parameter. Best, Stephane Philipakis @sphilipakis www.twazzup.com -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Draft of List API documentation
A work around for environments that don't support the DELETE request method is, I believe, to pass a parameter called _method with the value DELETE. In other words _method=DELETE. I'll take a look at that. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- If it weren't for Carbon-14, I wouldn't date at all. -- Diesel Sweeties --
[twitter-dev] Re: List API : statuses timeline and count parameter
Oh. I've realized that all the options *except* for count are supported. Fixing that now. Should be deployed to production in the next day or so. Thanks for reporting this. On Tue, Nov 3, 2009 at 5:01 PM, Marcel Molina mar...@twitter.com wrote: You can use all the same parameters as are available in the other status timeline resources (e.g. max_id, count, since_id, etc). On Tue, Nov 3, 2009 at 4:07 PM, stephane stephane.philipa...@gmail.com wrote: Hi guys ! Is there a way (or planned method) to get more than 20 statuses per list timeline API call ? apparently there is no equivalent to the count parameter. Best, Stephane Philipakis @sphilipakis www.twazzup.com -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: flagged as dupe post when string is unique (ideas?)
Is the posted status similar to any other status created by that user? Does the above imply that similar will trigger the dup detector? Argh! Please don't tell me that you're now rejecting similar tweets Url shorteners can easily generate similar urls, so if someone is in the habit of tweeting check this out followed by a shortened url, the tweet text is likely to be similar even though the actual url is different. Heck, urls that are similar often point to very different web pages. There are lots of other cases where similar tweets can actually be very different, and thus should not be rejected as duplicates. (I've heard of a project that tweets data that is guaranteed to be unique but is reasonably likely to be similar because of aggressive encoding.) as noted by other people on this list, twitter is currently rejecting tweets that match either your last update, or an update you recently sent. unfortunately, the API is currently silently failing but it is on the short list to have the API return an error code instead. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: Anyone else getting HTTP 404 with APIs today?
I'm getting 404 today as well on favorites/destroy for well-formed requests. And this on recent favorited tweets using the API. Any official response if this is a bug or not ? Thanks - Martin On Oct 15, 12:49 pm, Josh Roesslein jroessl...@gmail.com wrote: Just ran my unit tests and they all pass now. :) Seems the issues have been resolved for now. Josh On Thu, Oct 15, 2009 at 12:32 PM, Josh Roesslein jroessl...@gmail.com wrote: Yesterday I was having issues withfavorites/destroymost of the day. Haven't tried today yet. Josh -- Josh
[twitter-dev] Re: Draft of List API documentation
I have try this and It's work, thank you =] On Nov 4, 7:16 am, Marcel Molina mar...@twitter.com wrote: A work around for environments that don't support theDELETErequest method is, I believe, to pass a parameter called _method with the value DELETE. In other words _method=DELETE. On Mon, Nov 2, 2009 at 11:26 PM, wilfred yau wld991...@gmail.com wrote: It there any method todeleteuser from list other then usingDELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call DELETE (which only GET and POST). So, will twitter provide POST or GET method API to delete? Thanks On Oct 16, 3:04 pm, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. You may notice this API is a bit of a departure from the rest of the API. It's a bit more, errr, REST than the rest. First off, here's the current payload for alist: ?xml version=1.0 encoding=UTF-8? list id1416/id nametall people/name full_name@noradio/tall-people/full_name slugtall-people/slug subscriber_count0/subscriber_count member_count3/member_count uri/noradio/tall-people/uri modepublic/mode user id3191321/id nameMarcel Molina/name screen_namenoradio/screen_name locationSan Francisco, CA/location descriptionEngineer at Twitter on the @twitterapi team, obsessed with rock climbing amp; running. In a past life I was a member of the Rails Core team./description profile_image_urlhttp://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no.../profile_image_url urlhttp://project.ioni.st/url protectedfalse/protected followers_count40059/followers_count profile_background_color9AE4E8/profile_background_color profile_text_color33/profile_text_color profile_link_color0084B4/profile_link_color profile_sidebar_fill_colorDDFFCC/profile_sidebar_fill_color profile_sidebar_border_colorBDDCAD/profile_sidebar_border_color friends_count354/friends_count created_atMon Apr 02 07:47:28 + 2007/created_at favourites_count131/favourites_count utc_offset-28800/utc_offset time_zonePacific Time (US amp; Canada)/time_zone profile_background_image_urlhttp://a1.twimg.com/profile_background_images/18156348/jessica_tiled/profile_background_image_url profile_background_tiletrue/profile_background_tile statuses_count3472/statuses_count notificationsfalse/notifications geo_enabledtrue/geo_enabled verifiedfalse/verified followingfalse/following /user /list === Lists === POST '/:user/lists.:format' Creates a newlistfor the authenticated user. Parameters: * name: the name of thelist. (required) * mode: whether yourlistis public of private. Values can be 'public' or 'private'. Public by default if not specified. (optional) Usage notes: :user in the url should be the screen name of the user making the request to create thelist Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=tall peoplemode=privatehttp://twitter.com/noradio/lists.xml POST/PUT '/:user/lists/:list_slug.:format' Updates the specifiedlist. Takes the same parameters as the create resource at POST '/:user/lists.:format' (:name and :mode). Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=giantsmode=publichttp://twitter.com/noradio/lists/tall-people.xml GET '/:user/lists.:format' Lists your lists. Supported format: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml GET '/:user/lists/memberships.:format'Listthe lists the specified user has been added to. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/memberships.xml DELETE'/:user/lists/:list_slug.:format' Deletethe specifiedlistowned by the authenticated user. Parameters: * list_slug: the slug of thelistyou want todelete. (required) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -XDELETEhttp://twitter.com/noradio/lists/tall-people.xml GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specifiedlist. Parameters: * list_slug: the slug of thelistyou want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml GET '/:users/lists/:list_slug.:format' Show a
[twitter-dev] Re: Search API: max_id and page parameters giving very weird results
Except now that I look at it a day later, the results have completely changed, and seem to be in order. Why would the results change over time when the same max_id is set, and was valid at the time of the query? Are the ids of tweets not generated in ascending order? On Nov 3, 3:17 pm, TripleM stephenmerri...@gmail.com wrote: I've been trying to write a script to use the max_id parameter to loop through all 15 pages of results (with 100 results per page) without getting in troubles with grabbing the same tweet multiple times. Every time I do so, I find that not only are there a couple of duplicates on page 1 and 2, but also that the last tweet on page 1 is well further into the future, and has a lower ID, than a bunch of tweets on page 2. For example, consider these two, both with the same max_id but page = 1 and page = 2 respectively: http://search.twitter.com/search?rpp=100page=1geocode=-40.900557,17...http://search.twitter.com/search?rpp=100page=2geocode=-40.900557,17... (Or if you prefer json links which are what I am actually using, but I see the same thing on the above ones which are easier to describe:http://search.twitter.com/search.json?q=rpp=100geocode=-40.900557,1... Request:http://search.twitter.com/search.json?q=rpp=100geocode=-40.900557,1...) The first result on page 2 above was posted about 4 hours before the last tweet on page 1. There are also duplicates, eg AshleyGray00: Fireworks! I've been trying to figure this bug out for a while as I'm sure I'm missing something obvious but I'm completely stumped. Does anyone have any clue what is going on here? The only other threads I have found are about people trying to combine since_id and max_id which I know is not allowed, so I can't find anyone else having similar problems.
[twitter-dev] Re: Streaming Api - Keywords matched
May I suggest a potentially much more efficient algorithm? Place all keywords in a HashMap that maps keywords to a list of subscribed users. Tokenize the status text, and look up each token in the hash table to deliver the status to each subscribed user. Within the user, apply a generational filter to prevent duplicate deliveries of the same status. The statusid as an opaque marker works just fine assuming single-threaded operation or an appropriately scoped critical section that atomically completes status delivery to all users. You cannot assume strictly increasing statusids, so arithmetic comparison other than equality is a doomed generational index. This is how the Streaming API implements track (among other things). Your client is performing the same streaming operations to demultiplex the stream into your client streams as the Streaming API does to the Firehose to create your stream. The cost is nearly fixed, as there are only so many tokens per status. You are limited entirely by memory, as you can quickly forward statuses to a large number of clients following a nearly limitless set of keywords. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 9:59 am, Fabien Penso fabienpe...@gmail.com wrote: I agree, however it would help a lot because instead of doing : for keyword in all_keywords if tweet.match(keyword) //matched, notify users end end we could do for keyword in keywords_matched // same as above end for matching 5,000 keywords, it would bring the first loop from 5,000 to probably 1 or 2. You know what you matched, so it's quiet easy for you just to include row data of matched keywords, I don't need anything fancy. Just space separated keywords would help _so much_. On Tue, Nov 3, 2009 at 3:15 PM, John Kalucki jkalu...@gmail.com wrote: The assumption is that client services will, in any case, have to parse and route statuses to potentially multiple end-users. Providing this sort of hint wouldn't eliminate the need to parse the status and would likely result in duplicate effort. We're aware that we are, in some use cases, externalizing development effort, but the uses cases for the Streaming API are so many, that it's hard to define exactly how much this feature would help and therefore how much we're externalizing. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 1:53 am, Fabien Penso fabienpe...@gmail.com wrote: Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Re: Suggestion: Ability to just search amongst a user's friends
This functionality would be *huge*. Likewise, it'd be great if we could search lists. Now that we have 'em, it'd be great to use lists as filters for search. So, in the current search API, we've got from:USER, it'd be great if we could have in:LIST or some such. Thanks! ~ yoni On Oct 27, 11:02 pm, Chad Etzel c...@twitter.com wrote: This is something that we're considering internally. I'll bring it up again, though. -Chad On Tue, Oct 27, 2009 at 11:33 PM, Jesse Stay jesses...@gmail.com wrote: I have a project in which it would be tremendously easier if I could just specify a search to take place amongst a particular user's Twitter friends, instead of across the entire site. Is there a way to do this currently? If not, is this something the team could consider? I can make it work by comparing the full results to a list of friends, but that seems like unnecessary work. Thanks, Jesse
[twitter-dev] Re: flagged as dupe post when string is unique (ideas?)
Is the posted status similar to any other status created by that user? Does the above imply that similar will trigger the dup detector? Argh! Please don't tell me that you're now rejecting similar tweets Url shorteners can easily generate similar urls, so if someone is in the habit of tweeting check this out followed by a shortened url, the tweet text is likely to be similar even though the actual url is different. Heck, urls that are similar often point to very different web pages. There are lots of other cases where similar tweets can actually be very different, and thus should not be rejected as duplicates. (I've heard of a project that tweets data that is guaranteed to be unique but is reasonably likely to be similar because of aggressive encoding.) On Nov 1, 6:22 am, John Kalucki jkalu...@gmail.com wrote: Is the posted status similar to any other status created by that user? -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Oct 31, 8:12 am, gembry gem...@gmail.com wrote: Hello Folks, (fishing for input) thx Not really sure what’s going on here. Below you will find what I am sending and what is coming back from the Twitter API. You can see that what is being sent doesn’t even come close to what is up there now. Am I missing something here? What am I doing wrong? Why is this completely different sting not posting? Sending method=post url=http://twitter.com/statuses/update.xml?status=Great%20Job%20for %20OAS%20TEST%20ONLY%20in%20California%2DAnaheim%2FHuntington%20Beach %2E%20http%3A%2F%2Flocalhost%2FAssignmentReady%2Findex%2Ecfm%3ForderID %3D2315510%26category%3DAllied%5FTravel%26ts%3D102809140819%20or %20800%2E469%2E5314 Result (from Twitter API) ?xml version=1.0 encoding=UTF-8? status created_atWed Oct 28 19:51:30 + 2009/created_at id5238791820/id textwhat/text sourceweb/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/ in_reply_to_user_id favoritedfalse/favorited in_reply_to_screen_name/in_reply_to_screen_name user id57127952/id nameLarp Master Flash/name screen_nameLarpMasterFlash/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/ 1256674706/images/default_profile_0_normal.png/profile_image_url url/url protectedfalse/protected followers_count4/ followers_count profile_background_color9ae4e8/ profile_background_color profile_text_color00/ profile_text_color profile_link_colorff/profile_link_color profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color profile_sidebar_border_color87bc44/profile_sidebar_border_color friends_count0/friends_count created_atWed Jul 15 20:31:16 + 2009/created_at favourites_count0/favourites_count utc_offset/ utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1256674706/images/ themes/theme1/bg.png/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count34/statuses_count notificationsfalse/ notifications geo_enabledfalse/geo_enabled verifiedfalse/ verified followingfalse/following /user geo/ /status Thanks for the input.- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Search API: max_id and page parameters giving very weird results
Apologies for the multiple posts, but as the above links no longer show the problem, you can replicate as follows: Go to http://search.twitter.com/search?rpp=100page=1geocode=-40.900557,174.885971,1000km Note how long ago the last tweet on that page was posted. Click 'Older' at the bottom. The first tweets on that page are much newer than the last ones on page 1. On Nov 3, 3:17 pm, TripleM stephenmerri...@gmail.com wrote: I've been trying to write a script to use the max_id parameter to loop through all 15 pages of results (with 100 results per page) without getting in troubles with grabbing the same tweet multiple times. Every time I do so, I find that not only are there a couple of duplicates on page 1 and 2, but also that the last tweet on page 1 is well further into the future, and has a lower ID, than a bunch of tweets on page 2. For example, consider these two, both with the same max_id but page = 1 and page = 2 respectively: http://search.twitter.com/search?rpp=100page=1geocode=-40.900557,17...http://search.twitter.com/search?rpp=100page=2geocode=-40.900557,17... (Or if you prefer json links which are what I am actually using, but I see the same thing on the above ones which are easier to describe:http://search.twitter.com/search.json?q=rpp=100geocode=-40.900557,1... Request:http://search.twitter.com/search.json?q=rpp=100geocode=-40.900557,1...) The first result on page 2 above was posted about 4 hours before the last tweet on page 1. There are also duplicates, eg AshleyGray00: Fireworks! I've been trying to figure this bug out for a while as I'm sure I'm missing something obvious but I'm completely stumped. Does anyone have any clue what is going on here? The only other threads I have found are about people trying to combine since_id and max_id which I know is not allowed, so I can't find anyone else having similar problems.
[twitter-dev] Re: Draft of List API documentation
On Fri, Oct 16, 2009 at 1:04 AM, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. Marcel, It would be nice if we could pass in either the user_id or the screen_name, wherever you are currently requiring a Twitter user id. This would be consistent with the rest of the REST API (and quite useful, saving an extra call). Thanks, -damon -- http://twitter.com/damon
[twitter-dev] Re: Draft of List API documentation
Seconding... In our app, whenever someone enters a screen name they want to add to a list, we have to do two API calls, to first get the id before adding the user to the list. Lee On Tue, Nov 3, 2009 at 11:38 PM, Damon Clinkscales sca...@pobox.com wrote: On Fri, Oct 16, 2009 at 1:04 AM, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. Marcel, It would be nice if we could pass in either the user_id or the screen_name, wherever you are currently requiring a Twitter user id. This would be consistent with the rest of the REST API (and quite useful, saving an extra call). Thanks, -damon -- http://twitter.com/damon
[twitter-dev] Re: List API : statuses timeline and count parameter
I pointed this out on Oct 24th. http://groups.google.com/group/twitter-development-talk/browse_frm/thread/de91a4569fb10e5d/f8fabf89447a85c9?lnk=gstq=briccetti#f8fabf89447a85c9 Glad you have spotted the trouble.
[twitter-dev] Re: Suggestion for User record
+1 This would very, very useful. On Oct 31, 10:10 pm, Dave Winer dave.wi...@gmail.com wrote: It would be useful if a user had a lists_count element, in addition to the other counts (followers, statuses, favourites).
[twitter-dev] Re: Problems getting other people's friend list or follower list
Problem solved.
On Nov 3, 7:03 am, lane.montgomery lane.montgom...@gmail.com
wrote:
Hi, just signed up for the forum and posting a new topic. Gotta love
people like me, but I really need the help.
When I make a call to the API like this:
$user1results = $to-OAuthRequest('https://twitter.com/friends/
ids/'.$user1.'.json', array(), 'GET');
or this:
$user1results = $to-OAuthRequest('https://twitter.com/followers/
ids/'.$user1.'.json', array(), 'GET');
and pass the $user1 variable from a form entry, no matter what it is,
it always returns MY username's friend list or follower list.
Am I crazy, I thought you could request other people's info as long as
your account had access to that information on Twitter. But no matter
what I do, even hard-coding somebody's username in there, it still
only pulls my information.
7am and headed out to work, but I was up to 3am this morning working
on this to no avail. I really am stuck.
Let me know if you want to help me but need more code examples. I am
using the standard OAuth library linked to from twitter's apikiwi by:
Abraham Williams (abra...@abrah.am)http://abrah.amif that helps any.
Thanks to anybody for any assistance you can offer!
[twitter-dev] Re: Problems getting other people's friend list or follower list
It would be useful to others if you posted more information about what
the solution was.
- h
On 2009-11-03, lane.montgomery lane.montgom...@gmail.com wrote:
Problem solved.
On Nov 3, 7:03 am, lane.montgomery lane.montgom...@gmail.com
wrote:
Hi, just signed up for the forum and posting a new topic. Gotta love
people like me, but I really need the help.
When I make a call to the API like this:
$user1results = $to-OAuthRequest('https://twitter.com/friends/
ids/'.$user1.'.json', array(), 'GET');
or this:
$user1results = $to-OAuthRequest('https://twitter.com/followers/
ids/'.$user1.'.json', array(), 'GET');
and pass the $user1 variable from a form entry, no matter what it is,
it always returns MY username's friend list or follower list.
Am I crazy, I thought you could request other people's info as long as
your account had access to that information on Twitter. But no matter
what I do, even hard-coding somebody's username in there, it still
only pulls my information.
7am and headed out to work, but I was up to 3am this morning working
on this to no avail. I really am stuck.
Let me know if you want to help me but need more code examples. I am
using the standard OAuth library linked to from twitter's apikiwi by:
Abraham Williams (abra...@abrah.am)http://abrah.amif that helps any.
Thanks to anybody for any assistance you can offer!
