[twitter-dev] twitter legal
for group interest: http://news.bbc.co.uk/1/hi/technology/8285954.stm usually the reg gets these stories about a week before the beeb, maybe i missed it. On 1 Oct 2009, at 21:22, Christian Nunciato wrote: Has anyone had any trouble sending strings containing line breaks to Twitter through OAuth? I realize line breaks don't necessarily make sense in a Twitter update, but it still seems reasonable to be able to send them anyway, leaving the formatting up to Twitter, but in my case, I keep getting incorrect signature responses from /statuses/ update when I send them. Tweetdeck, by comparison, uses basic-auth, and is sending them through URL-encoded, without error. (Twitter, of course, replaces the line breaks with spaces.) But with OAuth, I'm not having any luck. It might just be my code, but things seem to be getting encoded properly (%0D), so I figured I'd check with the group to see whether anyone else had had a similar experience before going any further. Thanks in advance -- Chris
[twitter-dev] Re: Draft: Twitter Rules for API Use
My reading is that twitter can blacklist an app at any time for any reason - Twitter may suspend or terminate your access to the API - That being true, effectively it means that's the rule and the other points are really guidelines. It provides total freedom for the Platform team. That's also my understanding of the current rules/TOS. It's not obvious how to make an investable app on this basis. Am i wrong about this. Or can anyone confirm experience of successfully negotiating around this caveat for a due diligence? Ben On 11 Sep 2009, at 13:43, Dewald Pretorius wrote: I guess the lawyers wrote this draft as an extension of the modified Twitter TOS. Alex, you will need to jump on this draft from a dizzy height and get all your Platform rules in there. Once the API Rules are published as The Rules you will have no grounds to blacklist an application for other than what is written in The Rules. Unless the rules also state that, we can blacklist an app for any other reason as we deem fit, which will fly like a lead balloon. If the rules are not clear and comprehensive, they will become a ball and chain around the ankles of the Platform team. Dewald
[twitter-dev] Re: Problem in past 48 hours: friendships/create severe lag or loss
I haven't tested right through yet but issues relating to the POST/ auth requests from over the w/e and yesterday look largely resolved for me with all actions queued up and executed in the end. Thank-you for getting onto that and sorting. Ben On 31 Aug 2009, at 20:07, PJB wrote: Thanks Jon... can you let us know if past friendships/create (etc) calls that haven't yet worked, will eventually work? Since we database all of these actions, we're worried that we're going to have bad data for the past, e.g., 48 hours, unless those non-error calls actually go through. On Aug 31, 12:03 pm, John Kalucki jkalu...@gmail.com wrote: We're on this. Updates from the usual sources soon. On Aug 31, 11:57 am, David Dellanave david.dellan...@gmail.com wrote: I am pretty sure I am experiencing this issue as well. I can't verify it, yet. I assumed it was an issue with OAuth, but it seems like that it is the same issue.
[twitter-dev] Re: Problem in past 48 hours: friendships/create severe lag or loss
Thank-you, good to know. On 31 Aug 2009, at 20:03, John Kalucki wrote: We're on this. Updates from the usual sources soon. On Aug 31, 11:57 am, David Dellanave david.dellan...@gmail.com wrote: I am pretty sure I am experiencing this issue as well. I can't verify it, yet. I assumed it was an issue with OAuth, but it seems like that it is the same issue.
[twitter-dev] Re: /friendships/destroy.json /blocks/blocking /blocking/ids
Ok, further to email below, i'm not able to post follow requests
either, it comes back with success, but no database update seems to
have occurred.
Pretty much looks like any POST request just isn't happening, even
though twitter is coming back with friendly responses.
Ben
On 29 Aug 2009, at 17:35, ben wrote:
Couple of issues sprouting, i have been editing the code so i'm going
back and back over for some error at my end, but it's looking mighty
odd.
It looks like:
/friendships/destroy.json is not being updated
blocks/blocking.json is not returning the same users as /blocks/
blocking/ids.json
Logging below. My ip for is 67.23.28.168 and times Europe/London.
logging for friendships/destory:
2009-08-29 17:10:56,702 - twitterauth.utils - INFO - twitter api exe.
- https://twitter.com/friendships/destroy.json. kwargs={'screen_name':
u'arthurcooke'} method=POST is_auth=True
2009-08-29 17:10:57,166 - twitterauth.utils - DEBUG - api auth
response, {u'id': 16612822, u'verified': False,
u'profile_sidebar_fill_color': u'252429', u'profile_text_color':
u'66', u'followers_count': 14, u'protected': True, u'location':
u'Leeds, UK', u'profile_background_color': u'1A1B1F', u'status':
{u'favorited': False, u'truncated': False, u'text': u'Relaxing in
Aspen.', u'created_at': u'Mon Aug 10 22:45:51 + 2009', u'source':
u'web', u'in_reply_to_status_id': None, u'in_reply_to_screen_name':
None, u'in_reply_to_user_id': None, u'id': 3233921143}, u'utc_offset':
0, u'statuses_count': 46, u'description': u'Runner, Mountain Biker,
Science Teacher, Film Fan', u'friends_count': 18,
u'profile_link_color': u'2FC2EF', u'profile_image_url': u'http://
a3.twimg.com/profile_images/81150781/IMG_0320_normal.JPG',
u'notifications': False, u'profile_background_image_url': u'http://
s.twimg.com/a/1251493570/images/themes/theme9/bg.gif', u'screen_name':
u'arthurcooke', u'profile_background_tile': False,
u'favourites_count': 0, u'name': u'arthur cooke', u'url': None,
u'created_at': u'Mon Oct 06 12:07:50 + 2008', u'time_zone':
u'London', u'profile_sidebar_border_color': u'181A1E', u'following':
True}
then..not long later
2009-08-29 17:10:59,746 - twitterauth.utils - INFO - twitter api exe.
- https://twitter.com/statuses/friends.json. kwargs={'screen_name':
u'b_e_n_', 'page': 1} method=GET is_auth=False
the response is parsed and friends username listed in log..note
including the one who was just destroyed.
2009-08-29 17:11:00,206 - twittersearch.models - DEBUG - get current
friends for b_e_n_ - [u'TomChivers', u'Love_London', u'Fast140',
u'performativeweb', u'bbcbreaking', u'rhonafwelsh', u'danifromCO',
u'elliottzone', u'maustyn', u'unstuckdesign', u'arthurcooke',
u'jools2']
logging for blocks/blocking, last few logs show 3 blocked users from
blocking.json and 2 from ids.json:
009-08-29 17:11:39,268 - twitterauth.utils - INFO - twitter api exe. -
https://twitter.com/blocks/blocking.json. kwargs={'page': 1}
method=GET is_auth=True
2009-08-29 17:11:39,608 - twitterauth.utils - DEBUG - api auth
response, [{u'id': 16803782, u'verified': False,
u'profile_sidebar_fill_color': u'e0ff92', u'profile_text_color':
u'00', u'followers_count': 8, u'protected': False, u'location':
u'United States', u'profile_background_color': u'9ae4e8',
u'utc_offset': -32400, u'statuses_count': 0, u'description': u':spends
a lot of hours surfing the net', u'friends_count': 111,
u'profile_link_color': u'ff', u'profile_image_url': u'http://
a3.twimg.com/profile_images/
62184497/212297864a2022621782b584997122l_normal.jpg',
u'notifications': False, u'profile_background_image_url': u'http://
s.twimg.com/a/1251493570/images/themes/theme1/bg.gif', u'screen_name':
u'SARAH161008', u'profile_background_tile': False,
u'favourites_count': 0, u'name': u'SARAH161008', u'url': u'http://MY-
OWN-PAGE.TK', u'created_at': u'Thu Oct 16 07:03:12 + 2008',
u'time_zone': u'Alaska', u'profile_sidebar_border_color': u'87bc44',
u'following': False}, {u'id': 16804065, u'verified': False,
u'profile_sidebar_fill_color': u'e0ff92', u'profile_text_color':
u'00', u'followers_count': 7, u'protected': False, u'location':
u'', u'profile_background_color': u'9ae4e8', u'utc_offset': -32400,
u'statuses_count': 0, u'description': u':wants to GAIN weight!wants to
try bungee jumping amp; sky diving (but im acrophobic)',
u'friends_count': 84, u'profile_link_color': u'ff',
u'profile_image_url': u'http://a1.twimg.com/profile_images/
62185674/212297864a2698743034b849032084l_normal.jpg',
u'notifications': False, u'profile_background_image_url': u'http://
s.twimg.com/a/1251493570/images/themes/theme1/bg.gif', u'screen_name':
u'JOYCE161008', u'profile_background_tile': False,
u'favourites_count': 0, u'name': u'JOYCE161008', u'url': u'http://MY-
OWN-PAGE.TK', u'created_at': u'Thu Oct 16 07:40:38 + 2008',
u'time_zone': u'Alaska', u'profile_sidebar_border_color': u'87bc44',
u'following': False},
[twitter-dev] Re: /friendships/destroy.json /blocks/blocking /blocking/ids
Hmm, no, a good idea though. i'm using a python wrapper, it's pretty
exposed, i've cut out any cacheing in the course of debugging this
issue.
Well, this looks like a bug with me, otherwise this list would be a
whole lot more alive today.
On 30 Aug 2009, at 16:22, J. Dale wrote:
How are you calling twitter? Directly or via a wrapper like
EpiTwitter. I had problems with EpiTwitter effectively caching
requests. I had to go after particular elements in the result for it
to actually make/return the request.
On Aug 30, 4:47 am, Ben Eliott ben.apperr...@googlemail.com wrote:
Ok, further to email below, i'm not able to post follow requests
either, it comes back with success, but no database update seems to
have occurred.
Pretty much looks like any POST request just isn't happening, even
though twitter is coming back with friendly responses.
Ben
On 29 Aug 2009, at 17:35, ben wrote:
Couple of issues sprouting, i have been editing the code so i'm
going
back and back over for some error at my end, but it's looking mighty
odd.
It looks like:
/friendships/destroy.json is not being updated
blocks/blocking.json is not returning the same users as /blocks/
blocking/ids.json
Logging below. My ip for is 67.23.28.168 and times Europe/London.
logging for friendships/destory:
2009-08-29 17:10:56,702 - twitterauth.utils - INFO - twitter api
exe.
-https://twitter.com/friendships/destroy.json.
kwargs={'screen_name':
u'arthurcooke'} method=POST is_auth=True
2009-08-29 17:10:57,166 - twitterauth.utils - DEBUG - api auth
response, {u'id': 16612822, u'verified': False,
u'profile_sidebar_fill_color': u'252429', u'profile_text_color':
u'66', u'followers_count': 14, u'protected': True, u'location':
u'Leeds, UK', u'profile_background_color': u'1A1B1F', u'status':
{u'favorited': False, u'truncated': False, u'text': u'Relaxing in
Aspen.', u'created_at': u'Mon Aug 10 22:45:51 + 2009',
u'source':
u'web', u'in_reply_to_status_id': None, u'in_reply_to_screen_name':
None, u'in_reply_to_user_id': None, u'id': 3233921143},
u'utc_offset':
0, u'statuses_count': 46, u'description': u'Runner, Mountain Biker,
Science Teacher, Film Fan', u'friends_count': 18,
u'profile_link_color': u'2FC2EF', u'profile_image_url': u'http://
a3.twimg.com/profile_images/81150781/IMG_0320_normal.JPG',
u'notifications': False, u'profile_background_image_url': u'http://
s.twimg.com/a/1251493570/images/themes/theme9/bg.gif',
u'screen_name':
u'arthurcooke', u'profile_background_tile': False,
u'favourites_count': 0, u'name': u'arthur cooke', u'url': None,
u'created_at': u'Mon Oct 06 12:07:50 + 2008', u'time_zone':
u'London', u'profile_sidebar_border_color': u'181A1E', u'following':
True}
then..not long later
2009-08-29 17:10:59,746 - twitterauth.utils - INFO - twitter api
exe.
-https://twitter.com/statuses/friends.json. kwargs={'screen_name':
u'b_e_n_', 'page': 1} method=GET is_auth=False
the response is parsed and friends username listed in log..note
including the one who was just destroyed.
2009-08-29 17:11:00,206 - twittersearch.models - DEBUG - get current
friends for b_e_n_ - [u'TomChivers', u'Love_London', u'Fast140',
u'performativeweb', u'bbcbreaking', u'rhonafwelsh', u'danifromCO',
u'elliottzone', u'maustyn', u'unstuckdesign', u'arthurcooke',
u'jools2']
logging for blocks/blocking, last few logs show 3 blocked users from
blocking.json and 2 from ids.json:
009-08-29 17:11:39,268 - twitterauth.utils - INFO - twitter api
exe. -
https://twitter.com/blocks/blocking.json. kwargs={'page': 1}
method=GET is_auth=True
2009-08-29 17:11:39,608 - twitterauth.utils - DEBUG - api auth
response, [{u'id': 16803782, u'verified': False,
u'profile_sidebar_fill_color': u'e0ff92', u'profile_text_color':
u'00', u'followers_count': 8, u'protected': False, u'location':
u'United States', u'profile_background_color': u'9ae4e8',
u'utc_offset': -32400, u'statuses_count': 0, u'description':
u':spends
a lot of hours surfing the net', u'friends_count': 111,
u'profile_link_color': u'ff', u'profile_image_url': u'http://
a3.twimg.com/profile_images/
62184497/212297864a2022621782b584997122l_normal.jpg',
u'notifications': False, u'profile_background_image_url': u'http://
s.twimg.com/a/1251493570/images/themes/theme1/bg.gif',
u'screen_name':
u'SARAH161008', u'profile_background_tile': False,
u'favourites_count': 0, u'name': u'SARAH161008', u'url': u'http://
MY-
OWN-PAGE.TK', u'created_at': u'Thu Oct 16 07:03:12 + 2008',
u'time_zone': u'Alaska', u'profile_sidebar_border_color': u'87bc44',
u'following': False}, {u'id': 16804065, u'verified': False,
u'profile_sidebar_fill_color': u'e0ff92', u'profile_text_color':
u'00', u'followers_count': 7, u'protected': False, u'location':
u'', u'profile_background_color': u'9ae4e8', u'utc_offset': -32400,
u'statuses_count': 0, u'description': u':wants to GAIN weight!
wants to
try bungee jumping amp; sky diving (but im acrophobic)',
u'friends_count': 84
[twitter-dev] Re: Developer Preview: Geolocation API
Hi Ryan, Thank-you for the fast response. That makes sense, thanks a lot for clarifying. Wow, this is a really exciting feature. Best Regards, Ben On 21 Aug 2009, at 17:44, Ryan Sarver 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%A0update http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials 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] Re: Developer Preview: Geolocation API
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%A0update http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials 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] Re: available languages
Hi Michael, Thank you very much for this. Going back to look again at that page again the ISO link is right there, as you say. I don't know why my eye skipped over it like that. I guess too much/not enough caffeine. Thanks again, sorry for the time waster. Ben On 17 Aug 2009, at 15:24, Michael Paladino wrote: According to the documentation of the lang parameter under Parameters at http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search , the language codes should be provided using the ISO 639-1 code (actual list at http://www.loc.gov/standards/iso639-2/php/code_list.php) . Those codes are two letter such as “en” for English and “es” for Spanish. Hope this helps. Michael Paladino http://tidytweet.com -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com ] On Behalf Of ben Sent: Monday, August 17, 2009 3:35 AM To: Twitter Development Talk Subject: [twitter-dev] available languages I can't spot information on languages in the wiki. Please can someone advise what values are in the language parameter in tweets from the search api. All possible iso language codes? two and four codes, e.g. en-us and en, or just the two-letter codes? Whatever the user wants? Thanks a lot, Ben
