Re: a simple workaround for lack of OAuth
This is a good method to verify (claim) an account, yes... but if you wanted them to be able to do any sort of authenticated request (like tweeting or sending a direct message), you'd still need their password. That is, unless you are asking twitter to change the way their API works. By future logins, do you mean to twitter? or to your service? -Chad On Sat, Nov 22, 2008 at 12:22 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, One could just have the user enter an assigned code into the bio/url or even in a post (which would also help promote your service). Doing so would allow the user to claim the twitter account and associate it with his/her account in your service. Unlike OAuth, this would even make future logins simpler. Is this a reasonable way to go? Amir
Re: a simple workaround for lack of OAuth
On Nov 22, 12:26 pm, Chad Etzel [EMAIL PROTECTED] wrote: This is a good method to verify (claim) an account, yes... but if you wanted them to be able to do any sort of authenticated request (like tweeting or sending a direct message), you'd still need their password. That is, unless you are asking twitter to change the way their API works. By future logins, do you mean to twitter? or to your service? -Chad It would simplify future logins to my service over even OAuth. The problem for me though is that without user-specific authentication (i.e., I use authentication under my account always), IP-based rate limiting is a severe problem making this at best a temporary solution. Amir On Sat, Nov 22, 2008 at 12:22 PM, Amir Michail [EMAIL PROTECTED] wrote: Hi, One could just have the user enter an assigned code into the bio/url or even in a post (which would also help promote your service). Doing so would allow the user to claim the twitter account and associate it with his/her account in your service. Unlike OAuth, this would even make future logins simpler. Is this a reasonable way to go? Amir
Re: Are there any limitations on storing twitter data in a database?
Any restrictions on what you can store that's consumed via the REST API or Search API is in our Terms of Service: http://twitter.com/terms On Sat, Nov 22, 2008 at 09:34, Amir Michail [EMAIL PROTECTED] wrote: Hi, Can we store whatever we like in a database? Are there any limitations on what can be stored and for how long? Are there any rules against using stale data? Amir -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Is update_profile_background_image not working?
Hey guys - Working with the newish APIs for setting themes, and for some reason update_profile_background_image is not setting the image. A couple of things: - I believe my multipart is correct because I can use the exact same request body to update my avatar using update_profile_image - The response coming back is the equivalant of a show (that is, I am not getting any response other than a 200). Also is there any timeline on the tile bit from October? Thanks guys - -Max
Python Twitter API Wrapper problem w/ Google app engine
Hi, I'm stuck on the authorization part: if self._username and self._password: self._AddAuthorizationHeader(self._username, self._password) print self._request_headers = +`self._request_headers` requestBody = urllib.urlencode(self._request_headers) url_data = urlfetch.fetch(url, method=urlfetch.POST, headers={'Content-type': 'application/x-www-form- urlencoded', 'Content-Length': str(len(requestBody))}, payload=requestBody).content This gives the following exception when a username and password are supplied: ...\src\twitter.py in NewFromJsonDict(data=u'request') 547 else: 548 status = None 549 return User(id=data.get('id', None), 550 name=data.get('name', None), 551 screen_name=data.get('screen_name', None), global User = class 'twitter.User', builtin id = built-in function id, data = u'request', data.get undefined, builtin None = None, name undefined, screen_name undefined, location undefined, description undefined, profile_image_url undefined, url undefined, status = None type 'exceptions.AttributeError': 'unicode' object has no attribute 'get' Any ideas on how to get this to work? Amir
Re: User Method Show Friends Down
Hmm... seems to be working now. Could this have had something to do with the special characters in peoples bios? Like the stars and faces and such? On Nov 22, 3:46 pm, DustyReagan [EMAIL PROTECTED] wrote: It seems thathttp://twitter.com/statuses/friends/bob.xml?page=1is not working. I'm getting lots of complaints on FriendOrFollow.com from users seeing incorrect results. So it's not just bob with a broken page. Also, it doesn't appear to always be page 1. Sometimes it's a page in the middle like this example: WORKS =http://twitter.com/statuses/friends/cesart.xml?page=2 BROKEN =http://twitter.com/statuses/friends/cesart.xml?page=3 WORKS =http://twitter.com/statuses/friends/cesart.xml?page=4 I'm not sure if this is related to the show_users problem being discussed now also in the group. Dusty
Re: User Method Show Friends Down
Could you provide examples? On Sat, Nov 22, 2008 at 20:24, DustyReagan [EMAIL PROTECTED] wrote: Hmm... seems to be working now. Could this have had something to do with the special characters in peoples bios? Like the stars and faces and such? On Nov 22, 3:46 pm, DustyReagan [EMAIL PROTECTED] wrote: It seems thathttp://twitter.com/statuses/friends/bob.xml?page=1is not working. I'm getting lots of complaints on FriendOrFollow.com from users seeing incorrect results. So it's not just bob with a broken page. Also, it doesn't appear to always be page 1. Sometimes it's a page in the middle like this example: WORKS =http://twitter.com/statuses/friends/cesart.xml?page=2 BROKEN =http://twitter.com/statuses/friends/cesart.xml?page=3 WORKS =http://twitter.com/statuses/friends/cesart.xml?page=4 I'm not sure if this is related to the show_users problem being discussed now also in the group. Dusty -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Is update_profile_background_image not working?
This is the first I've heard of it not working. Please email me off-list with full request/response output and I'll investigate. On Sat, Nov 22, 2008 at 14:46, Max [EMAIL PROTECTED] wrote: Hey guys - Working with the newish APIs for setting themes, and for some reason update_profile_background_image is not setting the image. A couple of things: - I believe my multipart is correct because I can use the exact same request body to update my avatar using update_profile_image - The response coming back is the equivalant of a show (that is, I am not getting any response other than a 200). Also is there any timeline on the tile bit from October? Thanks guys - -Max -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: show_users down?
This looks to be working now - did you guys do something to fix it? Also, why were we not getting XML or JSON output back on the error through the API? Jesse On Nov 22, 2008, at 11:31 AM, Alex Payne wrote: I'll ask our team about this one. Very odd. On Sat, Nov 22, 2008 at 09:23, Chad Etzel [EMAIL PROTECTED] wrote: I can verify this also. Actually, it looks like you can't even see guykawasaki's twitter page.. http://twitter.com/guykawasaki he probably posted one too many alltop.com links and broke the system :) -chad On Sat, Nov 22, 2008 at 3:21 AM, Jesse Stay [EMAIL PROTECTED] wrote: Further info - so far I'm only able to reproduce it with the user guykawasaki. Other users do seem to work. Jesse On Nov 22, 2008, at 1:16 AM, Jesse Stay wrote: I'm getting the something is technically wrong error when loading show_users right now when I try to authenticate it with any username but the user themselves - is something going on?: http://twitter.com/users/show/guykawasaki.json What's even odder is that it's returning plain HTML as the error and not JSON or XML as expected, which is breaking my app. Thanks, Jesse -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x