[twitter-dev] Re: Double Basic Authentication When Post Follows Get
OK, done. thx :)
On Apr 12, 5:58 am, Abraham Williams 4bra...@gmail.com wrote:
Well the API is what it is. I don't know of any open issues about supporting
sessions. I suppose you could open one.
On Sat, Apr 11, 2009 at 19:19, Adrian spiritpo...@gmail.com wrote:
It adds more complexity to my side. Sessions would be better atm.
On Apr 12, 3:10 am, Cameron Kaiser spec...@floodgap.com wrote:
..I can't and dont' want to access user credentials.
I'd love session support.
Then you will love OAuth.
--
personal:
http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com*
ckai...@floodgap.com
-- I'm a dyslexic amateur orthinologist. I just love word-botching.
---
--
Abraham Williams |http://the.hackerconundrum.com
Hacker |http://abrah.am|http://twitter.com/abraham
Web608 | Community Evangelist |http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States
[twitter-dev] Re: I get new follower mails, but I'm not followed
Hi Alex. Here's another one, just in. I wont send any more, I'm sure you get the point :-) Terry From: Twitter twitter-follow-terry=jon...@postmaster.twitter.com Subject: Mike Melnick is now following you on Twitter! Date: Sun, 12 Apr 2009 12:26:49 + Hi, Terry Jones (terrycojones). Mike Melnick (Houstonchirodoc) is now following your updates on Twitter. Check out Mike Melnick's profile here: http://twitter.com/Houstonchirodoc You may follow Mike Melnick as well by clicking on the follow button. Best, Twitter -- Turn off these emails at: http://twitter.com/account/notifications
[twitter-dev] Re: I get new follower mails, but I'm not followed
Hi Andrew Out of curiosity, have you signed up for any of those autofollower apps or bots or programs? No. This could all just be coincidence - that people are in fact following me, and then unfollowing soon after for some reason. We don't know how much latency there is in Twitter's outgoing SMTP notifications. Twitter could presumably look at the examples I've given and see what those users did - did they follow many and unfollow them all (the last one I got was from someone (now) not following anyone)? Or did they just follow me in particular and then unfollow me? Anyway, this is not API related, so I'll let it drop until/unless there's news back from Alex. Terry
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
2009/4/12 Cmdr J0hn kazuhiro.is...@gmail.com: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) [...] status=%E3%81%82 (It's utf-8, I guess. 3 bytes needed for one Japanese charactor) I think you're not encoding this properly. You're sending one character, so you should send just one code, not three. Sure, Twitter should not break if you do this but, at the same time, your encoding is not right. Looking at your example, it seems you're converting your UTF-8 to a string of bytes and sending each byte separately, which should not be the case. (I have the slight impression that it should be something like status=%4054 or some other very right value, but, again, just one character, not three.) -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
(I have the slight impression that it should be something like status=%4054 or some other very right value, but, again, just one character, not three.) Correcting myself: status=#12354; http://www.danshort.com/HTMLentities/index.php?w=hirag NO! The original poster is correct -- you encode the Unicode point as UTF-8, then send the bytes. From RFC 3986: When a new URI scheme defines a component that represents textual data consisting of characters from the Universal Character Set [UCS], the data should first be encoded as octets according to the UTF-8 character encoding [STD63]; then only those octets that do not correspond to characters in the unreserved set should be percent- encoded. For example, the character A would be represented as A, the character LATIN CAPITAL LETTER A WITH GRAVE would be represented as %C3%80, and the character KATAKANA LETTER A would be represented as %E3%82%A2. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- He is rising from affluence to poverty. -- Mark Twain --
[twitter-dev] Update API (with OAuth) failed on Unicode tweet
Hello, fellow twitters, My app encountered errors on twitter update API when I try to send Unicode string. My app is writtin in Python, I made a slight modification in a library that is found on http://oauth.net/ My code is not prepared to be opened to public, but I can say that when I send ASCII string, it works. It's like this, when I say %= (a percent sign, and an equal), my app try to sign on a string like this, POSThttp%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.xml oauth_consumer_key%3D...(omit)...%26status%3D%2525%253D A request body is like this, status=%25%3D And, it works, like this: http://twitter.com/khopkun/status/1502555481 Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string: POSThttp%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 And a body is: status=%E3%81%82 (It's utf-8, I guess. 3 bytes needed for one Japanese charactor) then got an error, Failed to validate oauth signature or token status 401. I am wondering why ASCII charactors are okay, and Unicode are not. Any suggestion anyone?
[twitter-dev] Re: Deprecation of source parameter registration
Hi Doug, On Apr 9, 4:14 am, Doug Williams d...@twitter.com wrote: Beginning late this week or early next week, application developers will no longer be able to request API source parameters. Instead, new source parameters will only be available for OAuth applications, and will be managed by the developer through the registration and management interface (http://twitter.com/oauth_clients). This seems a little premature don't you think? The source parameter is important for marketing applications as well as gauging popularity - OAuth is both still in beta and unsupported by many clients/ applications. I've just started developing a Twitter app using python-twitter that is to run on Google AppEngine, but it will be some time after the next release before we have OAuth support (and even then it's dependent on a major overhaul of the HTTP layer)[1]. Sam 1. http://code.google.com/p/python-twitter/issues/detail?id=37q=oauth#c4
[twitter-dev] Re: update_profile_image not updating user's profile_image_url
I have same problem, any news yet? On 2 apr, 19:38, Alex Payne a...@twitter.com wrote: It is most likely a Twitter bug. We've been oscillating between two image uploading libraries, trying to deal with issues in each. On Wed, Apr 1, 2009 at 22:50, pianoben piano...@gmail.com wrote: I've Googled around a bit, and haven't found anything that talks about this issue, so I humbly submit my problem to the Twitter wizards. Here's the problem - when I call the API function update_profile_image, the upload succeeds, and Twitter returns status code 200. If I go to my actual profile image page (http://twitter.com/ account/profile_image/pianoben), the updated image (let's say O_RLY.jpg) is present. However, the rest of my profile still retains links to the scaled-down version of the former profile image, i.e. instead of http://amazonWS/o_rly_normal.jpg, everywhere a profile image is needed still links to http://amazonWS/ old_picture_normal.jpg. The latter is the URL returned as profile_image_url when calling /users/show/pianoben.xml. I'm pretty sure I've got my library code down pat, as the image itself verifiably uploads - it looks like Twitter is barfing on updating my user info after the API call completes. It is worth noting that none of this happens if I upload an image via the web interface. Has anyone else encountered this? What did you do to solve this? Or is this a Twitter bug? Thanks, Ben -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Using OAuth or API can u monitor Tweets have 3rd party app react
Hi Im wondering if our users whom have given us their Twitter name either via OAuth or API would be able to Twitter a command or even a word and when they do have it call to our app to take action? If this can not be done then could we monitor our users Twitter account every four hours to see if they have stated this action and if so then we would take action? Is there a limit to how many hits an app can hit Twitter a day? If the above was not clear here is an example Im Joe and Im on Twitter and this new thing a mo bob service. Joe is selling a couch in Murfreesboro, TN and Tweets Im selling a couch. The word sell is what would trigger this thing a mo bob 3rd party app and the app would search the web (craigslist and other sites) to find buyers and send joe an email listing those buyers. Thanks
[twitter-dev] Limit for following new people (per hour)?
I am on the whitelist for the Twitter API and use the friendships/ create method to follow new people. But now I cannot follow a user any more. So is there a limit which controls how many users you can follow (per hour/day...)? I hope you can help me. Thanks in advance!
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
On Apr 12, 8:08 am, Cmdr J0hn kazuhiro.is...@gmail.com wrote: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string: POSThttp%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 And a body is: status=%E3%81%82 Any suggestion anyone? I have exactly the same problem. I have checked with the OAuth signing guide at http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html, which even considers the case of non-English parameters that lead to multibyte characters, and their signature matches mine. I think this is a bug in the way Twitter verifies signatures when multibyte characters are present, and I've filed a bug report with them. Guan
[twitter-dev] Friendship Exsits Method
Hello, I am using the following method: http://twitter.com/friendships/exists.xml?user_a=aliceuser_b=bob When I check to see if user_a follows user_b it returns false but when I look at the list of people who user_a follows through the web, I see user_b. Is there a lag? Does it matter that user_a has a protected feed? Thank you for your help, Jeremy
[twitter-dev] Do any of the libraries implement a method for returning statuses_count?
If so, which one? If not, what is the best way to extract this piece of info? I'm a beginning programmer here, but I need this bit to accomplish my goal. -- You can choose your friends, you can choose the deals. - Equity Private AlphaGuy - http://alphaguy.blogspot.com On Twitter - @khyron4eva
[twitter-dev] autenticating user using OAuth
Hello Twitterers, I have been building my application and everything is working fine, just I am stuck on one thing. What is the correct way to authenticate user when they come back to my site for using my application, I want to authenticate them and using Oauth, but if I Request a toaken and send them to authorization URL they have to click on the Accept button, this is okay for the first time, but if they will have to do that everytime they login to my application this will not be good. May be I am missing something, so if someone can guide me I would really appreciate it. Thanks, Hameedullah Khan.
[twitter-dev] Limit for following new people (per hour)?
Hello! I'm on whitelist for the Twitter API. I used the friendships/create method to follow new people automatically. But now I can't follow a user any more. Is there a limit which says how many users you can follow per hour? I hope you can help me. Thanks in advance!
