[twitter-dev] Re: is this steet legal??
You're only reading... why would authorization be needed? On Sep 2, 12:45 am, clearmedia ch...@clearmedia.com.au wrote: not sure. I'm not using any authorization etc...?
[twitter-dev] Re: is this steet legal??
Thanks guys - thats all I needed to hear!
[twitter-dev] Twitter IP Whitelisting
So here's the deal. We've had the Twitter API integrated into Pwned.com for many months now. One problem we keep running into is that it updates our members Twitter WAY later. For example, it says so and so is playing on-line, but we processed that request hours ago and then it finally shows up on their feed. I have requested whitelisting before, but they claimed it was approved and I don't think that it is. We've had to severely limit our integration with Twitter because of this reason. Any help would be greatly appreciated. Thanks Andy
[twitter-dev] Re: Twitter IP Whitelisting
To see what the status of your IP is regarding rate limit, issue the following from that IP address: curl -I http://twitter.com/users/show.xml?screen_name=dougw | grep X- RateLimit-Limit If it's well above 150 then you're whitelisted. On Sep 1, 11:28 pm, Andy Pirate piratea...@gmail.com wrote: So here's the deal. We've had the Twitter API integrated into Pwned.com for many months now. One problem we keep running into is that it updates our members Twitter WAY later. For example, it says so and so is playing on-line, but we processed that request hours ago and then it finally shows up on their feed. I have requested whitelisting before, but they claimed it was approved and I don't think that it is. We've had to severely limit our integration with Twitter because of this reason. Any help would be greatly appreciated. Thanks Andy
[twitter-dev] Re: Twitter IP Whitelisting
I don't think white-listing is going to help with a latency problem. It only gets ya way more API GET requests per hour. Latency issues are probably due to twitter infrastructure problems, i.e., delays in the back-end DB servers posting updates from the front-end UI servers. We've been seeing this recently with follow / un-follow requests. Your issue may be another symptom of the same root problem. Hope this helps. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Andy Pirate Sent: Wednesday, September 02, 2009 01:28 To: Twitter Development Talk Cc: ma...@pwned.com Subject: [twitter-dev] Twitter IP Whitelisting So here's the deal. We've had the Twitter API integrated into Pwned.com for many months now. One problem we keep running into is that it updates our members Twitter WAY later. For example, it says so and so is playing on-line, but we processed that request hours ago and then it finally shows up on their feed. I have requested whitelisting before, but they claimed it was approved and I don't think that it is. We've had to severely limit our integration with Twitter because of this reason. Any help would be greatly appreciated. Thanks Andy
[twitter-dev] Re: Can't enter full name, character limit
This list is for discussion of the API. Please see http://help.twitter.comfor issues with the Twitter website. Thanks, Abraham On Tue, Sep 1, 2009 at 16:46, Martin Klein Schaarsberg martink...@gmail.com wrote: Hello, Under Twitter / Settings I've tried to enter my full name, Martin Klein Schaarsberg, but I can only enter Martin Klein Schaars. Is there a possibility to enter my full name or can the problem be fixed? The character limit is quite low in my opinion. There are quite a lot of people with longer names. Best regards, Martin Klein Schaarsberg -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: Twitter IP Whitelisting
Well I checked it out, and it says 150 is the rate limit on any random member, except my actual account is set 2. Now this seems like it only whitelisted my actual account. I obviously can't ask all the members to request a whitelist from twitter, that would thousands upon thousands of requests. Maybe it's a combination of latency and the rate limit? Is the rate limit only for users and not for the particular address that it's coming from? Or is it also limiting it on based where the feed update is coming from? Some more background for help. We rarely actually pull in their feeds, all we do is just post. Does this affect the rate limit at all? Thanks for all the replies guys! I really appreciate it :D On Sep 1, 11:35 pm, jmathai jmat...@gmail.com wrote: To see what the status of your IP is regarding rate limit, issue the following from that IP address: curl -Ihttp://twitter.com/users/show.xml?screen_name=dougw| grep X- RateLimit-Limit If it's well above 150 then you're whitelisted. On Sep 1, 11:28 pm, Andy Pirate piratea...@gmail.com wrote: So here's the deal. We've had the Twitter API integrated into Pwned.com for many months now. One problem we keep running into is that it updates our members Twitter WAY later. For example, it says so and so is playing on-line, but we processed that request hours ago and then it finally shows up on their feed. I have requested whitelisting before, but they claimed it was approved and I don't think that it is. We've had to severely limit our integration with Twitter because of this reason. Any help would be greatly appreciated. Thanks Andy
[twitter-dev] account/update_profile API call fails if original screen name has uppercase characters and login don't match exactly
I filed this a few weeks ago and the ticket wasn't commented on nor discussed here, so I replicate it here to bring some attention to it. It's an obscure bug: == Calls to account/update_profile API fails if the original screen name (the one that was signed up with, eg. User1, instead of user1) has uppercase characters and login don't match exactly (e.g user1 and not User1). Most, if not all other Twitter API calls, including the authenticating call is case-insensitive. But if the user has a screen name which has at least an uppercase character, account/update_profile will fail unless the authenticated screen name is spelled exactly the same. http://code.google.com/p/twitter-api/issues/detail?id=926
[twitter-dev] Re: Twitter IP Whitelisting
While we occasionally have update latency events (I think there was one yesterday afternoon for a bit of extra latency over a few tens of minutes), nearly all updates are applied to nearly timelines within a few seconds. The common case is even less latency. Some variance can be expected when a user with millions of followers updates -- there may be a period of many seconds before the last follower gets updated -- but not typically hours. I suspect that something else is wrong. Is the timestamp on the status correct, or is it delayed too? If it's delayed, perhaps you are running into a posting limit and there's a corner-case error condition that your HTTP client isn't logging and alerting? -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 1, 11:28 pm, Andy Pirate piratea...@gmail.com wrote: So here's the deal. We've had the Twitter API integrated into Pwned.com for many months now. One problem we keep running into is that it updates our members Twitter WAY later. For example, it says so and so is playing on-line, but we processed that request hours ago and then it finally shows up on their feed. I have requested whitelisting before, but they claimed it was approved and I don't think that it is. We've had to severely limit our integration with Twitter because of this reason. Any help would be greatly appreciated. Thanks Andy
[twitter-dev] Would like to have a database of tweets for a filter
Is there a predefined way to get results from a search into a table? Getting data from a search into a file, now need to get file into table. curl http://twitter.com/#search.atom?q=missuniverse -o v:\twittersts \searchmsu2.xml To get all past tweets about #missuniverse, I would do a search. To get all future tweets I can do a stream filter and/or search. correct?
[twitter-dev] Re: Would like to have a database of tweets for a filter
Search will give you results for the last several days. Then switch over to stream.twitter.com and use the track parameter on stream.twitter.com/1/statuses/filter.format. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 2, 8:06 am, Stuart stut...@gmail.com wrote: 2009/9/2 Mark Mason idtw...@gmail.com: Is there a predefined way to get results from a search into a table? Getting data from a search into a file, now need to get file into table. curlhttp://twitter.com/#search.atom?q=missuniverse-o v:\twittersts \searchmsu2.xml To get all past tweets about #missuniverse, I would do a search. To get all future tweets I can do a stream filter and/or search. correct? You need to use the search API and not URLs from the main site. http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search -Stuart --http://stut.net/projects/twitter/
[twitter-dev] Re: Developer Preview: Geolocation API
so an opted-in user will have latLong data automatically attached to her/his updates, taken from the browser/client W3c geolocation capabilities or is it necessary to explicitly include them in the message content? On Aug 21, 6:44 pm, Ryan Sarver rsar...@twitter.com wrote: Ben, Currently we geocode your user.location data to get an idea of where you are. That gets attached to each tweet as it comes in, but its not usually a representation of where you were when you actually sent the tweet. The new functionality will allow you to geotag the actual update without modifying the user.location field. When it comes to search, we'll use both and give priority to the tweet-level geotag. Make sense? Best, Ryan On Fri, Aug 21, 2009 at 4:06 AM, Ben Eliottben.apperr...@googlemail.com wrote: Hi, Please could you advise on the differences between this and the current location based searching facility? Is the current location search based on the users location in their settings whilst this is a exact location for each tweet? Thanks, Ben On 20 Aug 2009, at 21:46, Ryan Sarver wrote: We wanted to give you all a heads up on a cool new feature that is coming soon - Geolocation. The Geolocation API will give us the ability to attach geographic metadata to tweets to provide additional context with your update. Along with the option to tag updates, we will be able to search for nearby tweets and view the geo metadata in user timelines. The additional context allows for us to deliver more meaningful and localized experiences to users. We are also really excited about a unique facet of this release in that it will be API-only initially. This means that Twitter.com won't surface the functionality and we look forward to seeing the new and interesting experiences that will grow out of the ecosystem. As part of our Geolocation efforts we will soon be publishing Geolocation Best Pracitices to guide everyone through issues like security and privacy as well as discussing some ideal experiences for users. Topics will include things like storage of location data, what to do with a user's historical data, how to present the concept of geotagging and more. The guide will create a framework from which we can address the challenges that come about when dealing with something as sensitive as someone's location while hopefully allowing everyone enough creative freedom to create their own experiences around it. It is important to note that the feature is going to be strictly opt-in. It will be disabled until a user chooses to switch it on. We will provide a read-only attribute geo_enabled on the user object so an app can detect if the user has it disabled and let them know if they need to turn it on before using a geolocation feature. While we can't provide an exact date for launch, you should plan on having a few weeks of development time before the new API is officially launched. With that being said, lets get to it... Example: Geotagging a Tweet --- curl -d lat=37.780467long=-122.396762status=I have arrived -u user:pass http://twitter.com/statuses/update.xml; ?xml version=1.0 encoding=UTF-8? status created_atTue Apr 07 22:52:51 + 2009/created_at ... geo xmlns:georss=http://www.georss.org/georss; georss:point37.780467 -122.396762/georss:point /geo user id1401881/id nameDoug Williams/name ... geo_enabledtrue/geo_enabled ... /user /status We have also updated the wiki to reflect what the API will look like when it launches, so check it out and let us know if you have any questions: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u... http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve... We'll also be in our recently announced IRC channel (#twitterapi on irc.freenode.net) if you want to discuss the announcement with the team. Ryan PM, Platform Team http://twitter.com/rsarver
[twitter-dev] Either destroy is/was failing, or my understanding of destroy is/was failing
I've been hacking on the Twitter API, and I'm running into some serious weirdness with destroy. I post a message: C:\ curl -u name:pass -d status=Testing http://twitter.com/statuses/update.xml ?xml version=1.0 encoding=UTF-8? status created_atWed Sep 02 10:10:23 + 2009/created_at id3708721364/id textTesting/text sourcelt;a href=quot;http://apiwiki.twitter.com/quot; rel=quot;nofollowquot;gt;APIlt;/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 id70927096/id nameTed Neward/name screen_nameTestingScitter/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no rmal.png/profile_image_url url/url protectedfalse/protected followers_count1/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_count6/friends_count created_atWed Sep 02 09:49:13 + 2009/created_at favourites_count0/favourites_count utc_offset/utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/ theme1/bg.gif/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count4/statuses_count notificationsfalse/notifications verifiedfalse/verified followingfalse/following /user /status . which is all good, but then I try to delete that message: C:\ curl -u name:pass --http-request DELETE http://twitter.com/statuses/destroy/3708721364.xml ?xml version=1.0 encoding=UTF-8? hash request/statuses/destroy/3708721364.xml/request errorWe could not delete that status for some reason./error /hash What gives? Is this something that I'm doing wrong on my end? Momentary server weirdness? (Though it seems to have been pretty consistent all night.) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.com http://www.tedneward.com
[twitter-dev] Re: Twitter IP Whitelisting
We've experienced this at random, whether the user has 1+ million followers or whether they have 20 followers. I generally don't mind if the post has the timestamp of 15~ minutes past the time we actually sent the request. As far as the timestamp being posted, that is also delayed as well. I can guess we are running into a posting limit. I've actually had to cut back on our 20 minute cron jobs that checks whether a user is playing a game on steam/xbox etc.. We really ran into big latency issues when the cron was still posting the updates. We generally saw the updates coming many hours later, and sometimes days later. I suspect that it's were running into a posting limit like you mentioned. Is there a posting limit? When we post the updates, we don't receive any errors. This has plagued me because I'm always assuming the problem is on our end, but I can never find any good reason for it not to be working. On Sep 2, 6:48 am, John Kalucki jkalu...@gmail.com wrote: While we occasionally have update latency events (I think there was one yesterday afternoon for a bit of extra latency over a few tens of minutes), nearly all updates are applied to nearly timelines within a few seconds. The common case is even less latency. Some variance can be expected when a user with millions of followers updates -- there may be a period of many seconds before the last follower gets updated -- but not typically hours. I suspect that something else is wrong. Is the timestamp on the status correct, or is it delayed too? If it's delayed, perhaps you are running into a posting limit and there's a corner-case error condition that your HTTP client isn't logging and alerting? -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 1, 11:28 pm, Andy Pirate piratea...@gmail.com wrote: So here's the deal. We've had the Twitter API integrated into Pwned.com for many months now. One problem we keep running into is that it updates our members Twitter WAY later. For example, it says so and so is playing on-line, but we processed that request hours ago and then it finally shows up on their feed. I have requested whitelisting before, but they claimed it was approved and I don't think that it is. We've had to severely limit our integration with Twitter because of this reason. Any help would be greatly appreciated. Thanks Andy
[twitter-dev] Re: Developer Preview: Geolocation API
its up to the API client to send that extra data along -- its not in the tweet's textual content, if that is what you're asking. its metadata that is attached to the tweet. so an opted-in user will have latLong data automatically attached to her/his updates, taken from the browser/client W3c geolocation capabilities or is it necessary to explicitly include them in the message content? Ben, Currently we geocode your user.location data to get an idea of where you are. That gets attached to each tweet as it comes in, but its not usually a representation of where you were when you actually sent the tweet. The new functionality will allow you to geotag the actual update without modifying the user.location field. When it comes to search, we'll use both and give priority to the tweet-level geotag. Make sense? Best, Ryan Hi, Please could you advise on the differences between this and the current location based searching facility? Is the current location search based on the users location in their settings whilst this is a exact location for each tweet? Thanks, Ben On 20 Aug 2009, at 21:46, Ryan Sarver wrote: We wanted to give you all a heads up on a cool new feature that is coming soon - Geolocation. The Geolocation API will give us the ability to attach geographic metadata to tweets to provide additional context with your update. Along with the option to tag updates, we will be able to search for nearby tweets and view the geo metadata in user timelines. The additional context allows for us to deliver more meaningful and localized experiences to users. We are also really excited about a unique facet of this release in that it will be API-only initially. This means that Twitter.com won't surface the functionality and we look forward to seeing the new and interesting experiences that will grow out of the ecosystem. As part of our Geolocation efforts we will soon be publishing Geolocation Best Pracitices to guide everyone through issues like security and privacy as well as discussing some ideal experiences for users. Topics will include things like storage of location data, what to do with a user's historical data, how to present the concept of geotagging and more. The guide will create a framework from which we can address the challenges that come about when dealing with something as sensitive as someone's location while hopefully allowing everyone enough creative freedom to create their own experiences around it. It is important to note that the feature is going to be strictly opt- in. It will be disabled until a user chooses to switch it on. We will provide a read-only attribute geo_enabled on the user object so an app can detect if the user has it disabled and let them know if they need to turn it on before using a geolocation feature. While we can't provide an exact date for launch, you should plan on having a few weeks of development time before the new API is officially launched. With that being said, lets get to it... Example: Geotagging a Tweet --- curl -d lat=37.780467long=-122.396762status=I have arrived -u user:pass http://twitter.com/statuses/update.xml; ?xml version=1.0 encoding=UTF-8? status created_atTue Apr 07 22:52:51 + 2009/created_at ... geo xmlns:georss=http://www.georss.org/georss; georss:point37.780467 -122.396762/georss:point /geo user id1401881/id nameDoug Williams/name ... geo_enabledtrue/geo_enabled ... /user /status We have also updated the wiki to reflect what the API will look like when it launches, so check it out and let us know if you have any questions: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u ... http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve ... We'll also be in our recently announced IRC channel (#twitterapi on irc.freenode.net) if you want to discuss the announcement with the team. Ryan PM, Platform Team http://twitter.com/rsarver -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Followers count
Hello, I have spent a good portion of today reading through closed, merged, and open issues on http://code.google.com/p/twitter-api/issues/list I am trying to figure out the best way to get an accurate followers count. Initially, I was using /users/show which returns the full user object, including the followers_count item. However, I have noticed that this number only updates when the user posts a tweet. If the user has no new tweets, the follower count is not updated. Data I was pulling in was many days old. I understand the need to cache data, but being unable to pull up an approximate count of followers from the past several days is a problem. I have seen this issue posted many times, but it is always merged into issue 474, which appears to only deal with the following flag, and not the followers_count. There was one issue (which I can't find anymore) where there was acknowledgment that the users/show data was cached until a new post was made but no mention of any fix or solution. My next approach was to use the statuses/user_timeline. I wasn't sure if the user object for each status would have the current value or the value at the time of the status update. When I grabbed the xml formatted response, I got (starting from the most recent status and going back): 1686, 1653, 1685, 1685, 1685, 1685, 1685... Through the rest of the statuses, it stayed the same. Interestingly, 1686 is the current value listed on the website. 1653 was the value I got from /users/show. And I'm quite certain that the followers count did not stay constant at 1685. Moreover, when I grabbed the json version of statuses/user_timeline, I got entirely different results: 1653, 1653, 1683, 1675, 1652, 1661, 1644... This seems to reflect the current number of followers at the time of the status update, unlike the XML feed. Anyways, to get back to my original question. How do I get an accurate followers count for a user? Also, why are there still XML/ JSON discrepancies (I came across a few reported issues that said they had been resolved). Any help or suggestions would be very much appreciated! Thanks, Jason P.S. The account I was using for the above examples was DailyPHP
[twitter-dev] tweeting with oauth
Hi, Are there any examples of how to post tweet using an oauth token rather than username:password? I'm trying to do this in php. Thanks
[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing
There's a note on the Status blog that we're having some delays in processing a proportion of new statuses. This issue looks to largely be resolved, and all the subsequent backlogs have been processed -- except there's still a bit of a backlog pushing statuses to Facebook that should resolve soon enough. I'd imagine that your test status was delayed. Then, when you tried to delete it, it wasn't available. You should try again now. The queues look to be empty. -John On Sep 2, 9:38 am, Ted Neward ted.new...@gmail.com wrote: I've been hacking on the Twitter API, and I'm running into some serious weirdness with destroy. I post a message: C:\ curl -u name:pass -d status=Testinghttp://twitter.com/statuses/update.xml ?xml version=1.0 encoding=UTF-8? status created_atWed Sep 02 10:10:23 + 2009/created_at id3708721364/id textTesting/text sourcelt;a href=quot;http://apiwiki.twitter.com/; rel=quot;nofollowquot;gt;APIlt;/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 id70927096/id nameTed Neward/name screen_nameTestingScitter/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no rmal.png/profile_image_url url/url protectedfalse/protected followers_count1/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_count6/friends_count created_atWed Sep 02 09:49:13 + 2009/created_at favourites_count0/favourites_count utc_offset/utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/ theme1/bg.gif/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count4/statuses_count notificationsfalse/notifications verifiedfalse/verified followingfalse/following /user /status . which is all good, but then I try to delete that message: C:\ curl -u name:pass --http-request DELETEhttp://twitter.com/statuses/destroy/3708721364.xml ?xml version=1.0 encoding=UTF-8? hash request/statuses/destroy/3708721364.xml/request errorWe could not delete that status for some reason./error /hash What gives? Is this something that I'm doing wrong on my end? Momentary server weirdness? (Though it seems to have been pretty consistent all night.) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.comhttp://www.tedneward.com
[twitter-dev] Retweet API and multiple retweets in timeline
Hi all, this questions might have been asked already, but a quick search in this mailing list did not lead me to a clear response... so I apologize if this topic was discussed in detail already. My question: - if a tweet is retweeted several timese, e.g. tweet X is retweeted by my friend A and my friend B, it is likely these retweets are not taking place the same time. - my assumption and question is if the 2 retweets in this case show up as two tweets in the home timeline. What troubles me is how I can detect that a tweet was retweeted. I intend to save the last pulled statusId and then just pull tweets from the home_timeline from the last statusId. I hope to get the 'new retweets' as they happen as new people are retweeting. If the api will aggregate the retweets under the stausId of the original message, I will not be updated of new retweets in this case. On the other side, if a new retweet will add the original status a second time (possibly with the new total retweets, e.g. several retweet_details) then I track the retweet count. What do you think? Cheers Sven
[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing
Pushing statuses to Facebook ? can you clarify this? On Wed, Sep 2, 2009 at 11:25 AM, John Kaluckijkalu...@gmail.com wrote: There's a note on the Status blog that we're having some delays in processing a proportion of new statuses. This issue looks to largely be resolved, and all the subsequent backlogs have been processed -- except there's still a bit of a backlog pushing statuses to Facebook that should resolve soon enough. I'd imagine that your test status was delayed. Then, when you tried to delete it, it wasn't available. You should try again now. The queues look to be empty. -John On Sep 2, 9:38 am, Ted Neward ted.new...@gmail.com wrote: I've been hacking on the Twitter API, and I'm running into some serious weirdness with destroy. I post a message: C:\ curl -u name:pass -d status=Testinghttp://twitter.com/statuses/update.xml ?xml version=1.0 encoding=UTF-8? status created_atWed Sep 02 10:10:23 + 2009/created_at id3708721364/id textTesting/text sourcelt;a href=quot;http://apiwiki.twitter.com/; rel=quot;nofollowquot;gt;APIlt;/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 id70927096/id nameTed Neward/name screen_nameTestingScitter/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no rmal.png/profile_image_url url/url protectedfalse/protected followers_count1/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_count6/friends_count created_atWed Sep 02 09:49:13 + 2009/created_at favourites_count0/favourites_count utc_offset/utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/ theme1/bg.gif/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count4/statuses_count notificationsfalse/notifications verifiedfalse/verified followingfalse/following /user /status . which is all good, but then I try to delete that message: C:\ curl -u name:pass --http-request DELETEhttp://twitter.com/statuses/destroy/3708721364.xml ?xml version=1.0 encoding=UTF-8? hash request/statuses/destroy/3708721364.xml/request errorWe could not delete that status for some reason./error /hash What gives? Is this something that I'm doing wrong on my end? Momentary server weirdness? (Though it seems to have been pretty consistent all night.) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.comhttp://www.tedneward.com -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] [ANN] statuses/home_timeline resource now available (though it doesn't include retweets yet)
We mentioned in our early preview email about the retweet API (http://groups.google.com/group/twitter-api-announce/browse_thread/thread/1e07e332ec3d449d) that the statuses/friends_timeline resource wasn't going to include retweets for backwards compatibility so we don't break clients that aren't planning to add retweet support. The upgrade path is entirely opt-in. To that end we're adding a statuses/home_timeline resource that is in all ways identical to statuses/friends_timeline except the home_timeline resource *will* include retweets as demonstrated in the example payload in the documentation at http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-home_timeline. The statuses/home_timeline resource is now available though it won't include any retweets until the retweeting feature is fully launched. To be clear, until the full retweet launch, statuses/home_timeline will be 100% identical to statuses/friends_timeline and will *not* include retweets. We wanted to make the resource available early though so that clients who will be incorporating retweets into their timelines can update the resource that they reference and have requests succeed. When the full retweet launch happens, retweets will start to appear in statuses/home_timeline as per the documentation. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Retweet API and multiple retweets in timeline
If you take a look at the payload of a retweet in the examples, each retweet has the id of the original tweet as well as details about the retweet (who retweeted it, when and what the id of the retweet is). That information, specifically the retweet's id, should be sufficient for your purposes. On Wed, Sep 2, 2009 at 2:58 PM, hansamannsven.hai...@googlemail.com wrote: Hi all, this questions might have been asked already, but a quick search in this mailing list did not lead me to a clear response... so I apologize if this topic was discussed in detail already. My question: - if a tweet is retweeted several timese, e.g. tweet X is retweeted by my friend A and my friend B, it is likely these retweets are not taking place the same time. - my assumption and question is if the 2 retweets in this case show up as two tweets in the home timeline. What troubles me is how I can detect that a tweet was retweeted. I intend to save the last pulled statusId and then just pull tweets from the home_timeline from the last statusId. I hope to get the 'new retweets' as they happen as new people are retweeting. If the api will aggregate the retweets under the stausId of the original message, I will not be updated of new retweets in this case. On the other side, if a new retweet will add the original status a second time (possibly with the new total retweets, e.g. several retweet_details) then I track the retweet count. What do you think? Cheers Sven -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: [ANN] statuses/home_timeline resource now available (though it doesn't include retweets yet)
The current friends_timeline and home_timeline both include mentions already. The friends_timeline will continue to not include retweets since the payload for a retweeted status is slightly different. At some future time, though, the friends_timeline will be removed in favor of the home_timeline, which will include retweets. Having both parallel timelines, with one that does not include retweets is just a stop gap measure to ease the upgrade path. On Wed, Sep 2, 2009 at 4:56 PM, TjLluo...@gmail.com wrote: from the API page Twitter REST API Method: statuses/home_timeline [COMING SOON] Returns the 20 most recent statuses, including retweets, posted by the authenticating user and that user's friends. This is the equivalent of /timeline/home on the Web. Usage note: This home_timeline is identical to statuses/friends_timeline except it also contains retweets, which statuses/friends_timeline does not (for backwards compatibility reasons). In a future version of the API, statuses/friends_timeline will go away and be replaced by home_timeline. Does this mean that in a future version of the API there won't be any way to get a friends timeline without retweets? Because the ability to ignore retweets ought to be a Day 1 feature, IMO. I would put a much higher value on a unified feed which includes *mentions* and friends than *retweets* and friends FWIW TjL -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: New ReTweet API
I'd also like to know this. The examples on the twitter API page all just show one retweet_details section, this would mean that if multiple of your friends to retwee the same status, it will be added multiple times to the home timeline. this way, there is also no problem wiht tracking retweets of the same status over time, as you get new statuses into the timeline. Cheers Sven On Aug 14, 11:35 am, Houshang Nayeb shang...@gmail.com wrote: I have the following question: If one of my tweets is retweeted multiple times, what will be the return value of “retweets_of_me.format” ? Will it be one record with multiple “retweet_details” sections? If yes, will there be a “count” for the number of times it has been retweeted? If no, then what happens? Thanks!
[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing
We optionally push your statuses to Facebook to allow you to update your Facebook status automatically. This has been supported for about 14+ months. -John On Sep 2, 4:16 pm, Kevin Mesiab ke...@mesiablabs.com wrote: Pushing statuses to Facebook ? can you clarify this? On Wed, Sep 2, 2009 at 11:25 AM, John Kaluckijkalu...@gmail.com wrote: There's a note on the Status blog that we're having some delays in processing a proportion of new statuses. This issue looks to largely be resolved, and all the subsequent backlogs have been processed -- except there's still a bit of a backlog pushing statuses to Facebook that should resolve soon enough. I'd imagine that your test status was delayed. Then, when you tried to delete it, it wasn't available. You should try again now. The queues look to be empty. -John On Sep 2, 9:38 am, Ted Neward ted.new...@gmail.com wrote: I've been hacking on the Twitter API, and I'm running into some serious weirdness with destroy. I post a message: C:\ curl -u name:pass -d status=Testinghttp://twitter.com/statuses/update.xml ?xml version=1.0 encoding=UTF-8? status created_atWed Sep 02 10:10:23 + 2009/created_at id3708721364/id textTesting/text sourcelt;a href=quot;http://apiwiki.twitter.com/; rel=quot;nofollowquot;gt;APIlt;/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 id70927096/id nameTed Neward/name screen_nameTestingScitter/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no rmal.png/profile_image_url url/url protectedfalse/protected followers_count1/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_count6/friends_count created_atWed Sep 02 09:49:13 + 2009/created_at favourites_count0/favourites_count utc_offset/utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/ theme1/bg.gif/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count4/statuses_count notificationsfalse/notifications verifiedfalse/verified followingfalse/following /user /status . which is all good, but then I try to delete that message: C:\ curl -u name:pass --http-request DELETEhttp://twitter.com/statuses/destroy/3708721364.xml ?xml version=1.0 encoding=UTF-8? hash request/statuses/destroy/3708721364.xml/request errorWe could not delete that status for some reason./error /hash What gives? Is this something that I'm doing wrong on my end? Momentary server weirdness? (Though it seems to have been pretty consistent all night.) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.comhttp://www.tedneward.com -- Kevin Mesiab CEO, Mesiab Labs L.L.C.http://twitter.com/kmesiabhttp://mesiablabs.comhttp://retweet.com
[twitter-dev] since_retweet_id needed?
To track retweets over time and to not waste resources, I believe it would be great to get a since_retweet_id parameter for the new retweet status methods like statuses retweeted_to_me If we just have a status_id, you cannot pull for new retweets over time I believe. If you use the statusId, once you pulled a status with that Id, you should theoretically no longer get any more retweets for that status. Now having a since_retweet_id makes a lot of sense in this case. You can poll for new retweets without having to pull in the last 50 or so all the time, which saves resources. What do you think? Cheers Sven
[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing
We've got a fix for this going out tomorrow. On Wed, Sep 2, 2009 at 09:38, Ted Newardted.new...@gmail.com wrote: I’ve been hacking on the Twitter API, and I’m running into some serious weirdness with destroy. I post a message: C:\ curl -u name:pass -d status=Testing http://twitter.com/statuses/update.xml ?xml version=1.0 encoding=UTF-8? status created_atWed Sep 02 10:10:23 + 2009/created_at id3708721364/id textTesting/text sourcelt;a href=quot;http://apiwiki.twitter.com/quot; rel=quot;nofollowquot;gt;APIlt;/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 id70927096/id nameTed Neward/name screen_nameTestingScitter/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_normal.png/profile_image_url url/url protectedfalse/protected followers_count1/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_count6/friends_count created_atWed Sep 02 09:49:13 + 2009/created_at favourites_count0/favourites_count utc_offset/utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/theme1/bg.gif/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count4/statuses_count notificationsfalse/notifications verifiedfalse/verified followingfalse/following /user /status … which is all good, but then I try to delete that message: C:\ curl -u name:pass --http-request DELETE http://twitter.com/statuses/destroy/3708721364.xml ?xml version=1.0 encoding=UTF-8? hash request/statuses/destroy/3708721364.xml/request errorWe could not delete that status for some reason./error /hash What gives? Is this something that I’m doing wrong on my end? Momentary server weirdness? (Though it seems to have been pretty consistent all night.) Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.com -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Linking to the twitter UI for retweeting with the new retweet API
to allow users on another website to retweet (e.g. update status previously) one could use links liek these: http://twitter.com/home/?status=RT+%40aalmiray%3A+%40wmacgyver+yup.+Groovy+MOP+%2B+static+factory+method Question to the Twitter API team: Will there be a similar URL format for the new retweet api? e.g. http://twitter.com/home/?retweet_id=status_id If the logged in user would follow that link, the twitter ui would need to ask the user if he wants to retweet the tweet specified via the retweet_id. Related to this, some clients (and I was asked to add this to @ttytter) are threading RTs by using in_reply_to_status_id. Are those tweets showing up as replies (i.o.w., people who don't follow the re-tweeted user are NOT seeing the RTs), or are they showing up as regular tweets with i_r_t_s_i as a bonus? And should that be done anymore? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Commodore on desk/Power light glowing brightly/The computer waits -- T. Lake
[twitter-dev] Re: if you will be using the Geolocation API ...
Raffi: Great discussion, the geolocation code is exciting opens up so many possibilities. 1. Would you guys consider the geolocation code, opt-in on a tweet basis? It would be an optional input on a tweet basis with the default=off; This way users can choose, Hey, I am walking down market street for the next 45 minutes, and I am open to getting marketing offers. The bet= Users will want this on for a % of the time based on specific tweets and this would eliminate the need for them to turn the global geolocation default on and then off again, 2 steps vs. 1. 2. Any idea of approximate time frame we can start playing around with this? Thanks, Abir On Sep 2, 4:01 pm, Raffi Krikorian ra...@twitter.com wrote: hi jim. yup! http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve... Raffi, Another question came up as I was thinking about support for this in my web-site (http://twxlate.com): Will the user elements returned in the responses to API requests include information that indicates whether or not the user has opted- in to geo-coding of their tweets? I would like to see this right from the get go so that client web- sites / applications know whether or not to prompt their users for location information to be geo-coded with a tweet that is being created. If this isn't there, I think there will be unnecessary confusion and possibly wrong actions taken on behalf of the user. Please seriously consider this for inclusion in the initial deployment, if it is not already there. Thanks in advance. Comments welcome and expected. Jim Renkel On Sep 1, 6:08 pm, Raffi Krikorian ra...@twitter.com wrote: hey jim. 1. the user.location is a completely separate entity (for now) implies that maybe sometime in the future it may be used, e.g., to provide a default geo-coded location for a tweet. I would suggest that if the user's profile location if ever geo-coded, that geo-codeshould be added to the user objects returned by API calls, at least the users/show method. Users will want to know what may be, e.g., added to their tweets without having to generate a test tweet to find out. 2. Having the user's profile location geo-coded and returned in API calls would be very useful now. Yeh, twitter client web-sites / applications can do it for themselves (Mine certainly will if twitter doesn't do it.), but may come up with different / inconsistent results. And, trust me, it ain't as easy to get good results as it might first appear. To maximize use and consistency, it would be great if twitter did the geo-coding and supplied it to everyone. these are both great ideas. right now, thegeolocationAPI is really focused on tweet-level information -- but we're actively thinking about what's next. 3. Will twitter client web-sites / applications be able to turn the geo-location feature on for their users, or do the users have to go to twitter.com with a browser to do this? My concern here is that twitter.com only supports two languages (English and Japanese) for its UI, where my site (http://twxlate.com) supports these and over 40 more. Unless the user is fluent in English or Japanese, they won't be able to turn it on. I've already run into similar problems as I'm rolling out test versions of OAuth support. unfortunately not. as we're pretty sensitive to our user's privacy, for now, a user will have to go to twitter.com with a browser to turn on the setting (remember, by default it is off). if you have any suggestions on how to make this user interaction better in the future, i would be eager to hear them! As I've written some pretty spiffy geo-coding applications for other purposes, I plan on doing some pretty spiffy geo-coding stuff with twxlate.com. But it needs to be usable, or users won't use it and / or may be annoyed by it. I would hate for that to happen to what promises to be a really neat feature. cool! well - i hope what we're doing is usable! if not, just keep blasting me about it. threads like these on the mailing list are awesome. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: if you will be using the Geolocation API ...
Raffi, Is it only the account/verify_credentials method that will return the geo_enabled sub-element in the user element, or all methods that return a user element? While having only account/verify_credentials return it is better than nothing, I would hope that all methods that return a user element would include a geo_enabled sub-element. For consistency, if nothing else. With the issues associated with account/verify_credentials requests and the DOS attack, I have been avoiding using the method: Basic Authentication credentials can be, and in fact are, verified with any and every authenticated request; OAuth credentials (access token and token secret) are by their nature pre-authenticated, and are, again, re-verified with each and every use. So this may require me to issue an account/verify_credentials request where I would otherwise not have to do so, just to get the geo_enabled flag. I can, and will if necessary, do that, but would prefer not to. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Raffi Krikorian Sent: Wednesday, September 02, 2009 18:01 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: if you will be using the Geolocation API ... hi jim. yup! http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verif y_credentials Raffi, Another question came up as I was thinking about support for this in my web-site (http://twxlate.com): Will the user elements returned in the responses to API requests include information that indicates whether or not the user has opted- in to geo-coding of their tweets? I would like to see this right from the get go so that client web- sites / applications know whether or not to prompt their users for location information to be geo-coded with a tweet that is being created. If this isn't there, I think there will be unnecessary confusion and possibly wrong actions taken on behalf of the user. Please seriously consider this for inclusion in the initial deployment, if it is not already there. Thanks in advance. Comments welcome and expected. Jim Renkel On Sep 1, 6:08 pm, Raffi Krikorian ra...@twitter.com wrote: hey jim. 1. the user.location is a completely separate entity (for now) implies that maybe sometime in the future it may be used, e.g., to provide a default geo-coded location for a tweet. I would suggest that if the user's profile location if ever geo-coded, that geo-code should be added to the user objects returned by API calls, at least the users/show method. Users will want to know what may be, e.g., added to their tweets without having to generate a test tweet to find out. 2. Having the user's profile location geo-coded and returned in API calls would be very useful now. Yeh, twitter client web-sites / applications can do it for themselves (Mine certainly will if twitter doesn't do it.), but may come up with different / inconsistent results. And, trust me, it ain't as easy to get good results as it might first appear. To maximize use and consistency, it would be great if twitter did the geo-coding and supplied it to everyone. these are both great ideas. right now, the geolocation API is really focused on tweet-level information -- but we're actively thinking about what's next. 3. Will twitter client web-sites / applications be able to turn the geo-location feature on for their users, or do the users have to go to twitter.com with a browser to do this? My concern here is that twitter.com only supports two languages (English and Japanese) for its UI, where my site (http://twxlate.com) supports these and over 40 more. Unless the user is fluent in English or Japanese, they won't be able to turn it on. I've already run into similar problems as I'm rolling out test versions of OAuth support. unfortunately not. as we're pretty sensitive to our user's privacy, for now, a user will have to go to twitter.com with a browser to turn on the setting (remember, by default it is off). if you have any suggestions on how to make this user interaction better in the future, i would be eager to hear them! As I've written some pretty spiffy geo-coding applications for other purposes, I plan on doing some pretty spiffy geo-coding stuff with twxlate.com. But it needs to be usable, or users won't use it and / or may be annoyed by it. I would hate for that to happen to what promises to be a really neat feature. cool! well - i hope what we're doing is usable! if not, just keep blasting me about it. threads like these on the mailing list are awesome. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: Followers count
I hope you find out. I long ago gave up. If I really needed the feature, I would scrape that one out of the html, which I know is frowned upon, however, as your data shows, this is pretty all over the map. On Sep 2, 2009, at 2:44 PM, Jason Tan wrote: Anyways, to get back to my original question. How do I get an accurate followers count for a user? Also, why are there still XML/ JSON discrepancies (I came across a few reported issues that said they had been resolved). -- Scott * If you contact me off list replace talklists@ with scott@ *
[twitter-dev] Bump Issue 949 - Deleting status returns error
Still waiting to get some kind of acknowledgment... http://code.google.com/p/twitter-api/issues/detail?id=949
[twitter-dev] Twitter Open Connect
Hi all, Does Twitter support Open Connect which like the Facebook does? Thanks,
[twitter-dev] Find twitter account from email address?
If I have an email address, can I query somehow to find a person's twitter page?
[twitter-dev] Re: Find twitter account from email address?
Short answer: no. Ok, the long answer is no too. On Wed, Sep 2, 2009 at 21:18, Eric Zhang really...@gmail.com wrote: If I have an email address, can I query somehow to find a person's twitter page? -- Internets. Serious business.
[twitter-dev] Re: Can you speak in plain english
false On Sep 2, 6:50 pm, Dante Soiu dsoiual...@gmail.com wrote: And not computer language, Dante Soiu
[twitter-dev] Re: tweeting with oauth
Could use Abraham or my library. https://github.com/abraham/twitteroauth/tree https://github.com/jmathai/twitter-async/tree I have some blog posts that might help as well. http://www.jaisenmathai.com/blog/2009/03/31/how-to-quickly-integrate-with-twitters-oauth-api-using-php/ http://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-in-with-twitter-with-oauth/ On Sep 2, 1:58 pm, root root892...@yahoo.com wrote: Hi, Are there any examples of how to post tweet using an oauth token rather than username:password? I'm trying to do this in php. Thanks
