[twitter-dev] Re: How Does TwittPic Works ?
Hi Raffi No worries - hope you're feeling better soon! If we can be of any help with getting this out the door, please let me know! Cheers -N -- twitter.com/nikf
[twitter-dev] Re: How Does TwittPic Works ?
This is awesome news. Kudos to your pragmatic approach with xAuth and looking forward to your recursive delegation plans. Blogged it here: http://aralbalkan.com/3057 I hope the UX community supports Twitter in this. Aral On Feb 4, 4:57 pm, isaiah isa...@mac.com wrote: Oh wow, oh wow, oh wow! On Feb 3, 11:49 am, Raffi Krikorian ra...@twitter.com wrote: it will be available publicly soon! On Wed, Feb 3, 2010 at 11:43 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Have you tried it? There is no OAuth flow. I.e., the user types in his Twitter username and password. That's it. If it is indeed using OAuth, does that mean that the background requesting of tokens when you have the Twitter credentials is now available? Meaning, I can also now use it to convert all existing Twitter accounts to OAuth in one fell swoop? On Feb 3, 3:02 pm, Raffi Krikorian ra...@twitter.com wrote: seesmic look, i believe, is using oauth talking to api.twitter.com. On Tue, Feb 2, 2010 at 8:09 PM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, What's going on here? Your credibility is at stake here. You've been telling us in many posts that new apps must use OAuth to get a source attribution, and only old grandfathered apps have source attribution with Basic Auth. On Feb 2, 11:18 pm, Dewald Pretorius dpr...@gmail.com wrote: At first I thought they must have changed the old Seesmic source to Seesmic Look. But no. Here's a recent tweet from Seesmic: http://twitter.com/CathyBrooks/status/8570217879 And here's a recent one from Seesmic Look: http://twitter.com/adamse/status/8565271563 Seesmic Look uses Basic Auth. Does anyone else spot Mt Everest on this level playing field of ours? On Feb 2, 10:41 pm, Pedro Junior v.ju.ni.o...@gmail.com wrote: *Seesmic Look is old? * - Pedro Junior 2010/2/2 Lukas Müller webmas...@muellerlukas.de Only old apps can do this. New apps cannot use it. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Query About Direct Messages
In Twitter,showing 250 per day limit.i want know to that,250 means message or 250 users.I want to develop a tool to send direct messages to my friends at a time.So,any body help me to solve my problem. Thank u. Kiran
[twitter-dev] Retweets and location problems in search API
In the search API, if you query for RT in the San Francisco area using the geocode parameter it returns both official retweets (ones created by hitting the retweet button) and unofficial retweets (retweets where either the user or the client has simply inserted the text RT). Official retweets keep the location field of the original tweet. Unofficial retweets take on the location of the user who retweeted the message. The problem I'm having is that this makes geolocation searches for retweets from a certain area very confusing. It's impossible to search for what/who people in a certain city, say San Francisco are rtweeting the most. Users in San Francisco who use the official retweet feature and retweet something from NY don't show up in a query for San Francisco Retweets. Likewise, if one was interested in who from San Francisco was being retweeted the most, they would also be stymied b/c the results are polluted with unofficial RT's that look text-wise like an official RT (same message text format). So they would get a lot of results of San Franciscans retweeting people from New York. The only way to check against that would be to do a show/user lookup on the from_user, and the rate limit on that API would be eaten up very quickly for any persistant search. Is there any plan to address these issues? Has anyone in the development community found a work around? Thanks, Matt
Re: [twitter-dev] Twitter based bug tracker/feedback system, anyone?
What is Tender? Anton On Thu, Feb 4, 2010 at 4:04 PM, Michael Ivey michael.i...@gmail.com wrote: Cotweet has some of this, but it's a more general manage responses system than bug tracking. I'd love to see Tender add Twitter features. -- ivey On Wed, Feb 3, 2010 at 1:03 PM, Anton Krasovsky anton.krasov...@gmail.com wrote: I wonder if anyone has a twitter based bugtracker / feedback system? Of course, there are many web based systems like that (uservoice, etc), but given that many of my users seem to have mostly mobile-based net access, leaving feedback for them is harder than it should be. Or if I start using twitter as a main feedback channel, it's going to be difficult to me to keep track of all these tweets. So, is there anything out there that could help me keep track of user feedback via twitter? Regards, Anton http://pavo.me j2me Twitter client
[twitter-dev] Re: OAuth Photo Support Now Available at TweetPhoto
Hello! So, this means if I login with oauth to tweetphoto I am also logged in to twitter? This is important, thank you very much! On Feb 5, 2:02 am, Sean Callahan seancalla...@gmail.com wrote: All the other functionality in the TweetPhoto API is also supported using OAuth as well. Let me know if you have any questions. Sean On Jan 31, 9:01 pm, Sean Callahan seancalla...@gmail.com wrote: TweetPhoto now supports photo uploads using OAuth for all 3rd party application developers. http://groups.google.com/group/tweetphoto/web/oauth-signin Basic Auth may be depreciated soon so we created a way for you to allow your users to continue to uploadphotos. Please let me know if you have any questions or if I can help in any way. Sean
[twitter-dev] Incoming User-Objects are blank ?
Hi guys,
i am using the Twitterscript Libary for as3-Developing...I want to
search twitter (exp: Apple) and show the results in a List. There i
wanna display the image/name of each author...
My problem ist, that the twitterUser object of the twitterStatus
object is totally empty / all vars are empty..
this.twitt = new Twitter();
this.tSearch= new TwitterSearch();
this.twitt.addEventListener(TwitterEvent.ON_SEARCH, onSearch);
//this.tSearch.lang = de;
this.tSearch.addKeyword(Apple);
//this.tSearch.addKeyword(Unfall, false,
true);
this.twitt.search(this.tSearch);
}
protected function onSearch(event:TwitterEvent):void
{
trace(event.data );
_tweetArray = event.data as Array;
var twitterStatus:TwitterStatus;
for (var i : int = 0; i event.data.length;
i++)
{
twitterStatus = event.data[i];
trace( twitterStatus.user.id) // = Empty
}
Any idea? I think that Twitterscript is a great lib, so i really
regret it, if i can't use it. :/
greetings, nico
Re: [twitter-dev] Twitter based bug tracker/feedback system, anyone?
Thanks, it looks interesting. Regards, Antont On Thu, Feb 4, 2010 at 4:04 PM, Michael Ivey michael.i...@gmail.com wrote: Cotweet has some of this, but it's a more general manage responses system than bug tracking. I'd love to see Tender add Twitter features. -- ivey On Wed, Feb 3, 2010 at 1:03 PM, Anton Krasovsky anton.krasov...@gmail.com wrote: I wonder if anyone has a twitter based bugtracker / feedback system? Of course, there are many web based systems like that (uservoice, etc), but given that many of my users seem to have mostly mobile-based net access, leaving feedback for them is harder than it should be. Or if I start using twitter as a main feedback channel, it's going to be difficult to me to keep track of all these tweets. So, is there anything out there that could help me keep track of user feedback via twitter? Regards, Anton http://pavo.me j2me Twitter client
[twitter-dev] Re: Mobile OAuth fix is LIVE
Ryan, Thanks for both the attempted fix and the announcement. Unfortunately, where the previous version was kind of a crapshoot for mobile users because the buttons appeared black (see my screenshot in the bug report at http://code.google.com/p/twitter-api/issues/detail?id=395), this new version doesn't work at all on many mobile browsers. Because this breaks mobile Twitter support completely for many (most? all?) phones using older browsers, can you please revert to the previous version, and then stage a new version somewhere else that we can help you test? -- Charles On Feb 3, 3:16 pm, Ryan Sarver rsar...@twitter.com wrote: FINALLY! An update has just gone live that fixes rendering of the OAuth screens for most mobile devices. We also fixed a few small nagging things like the default action is now allow instead of deny if you just hit go on an iPhone. I've attached two screenshots so you can see the updated screens. Please test it out with your various mobile web apps and let us know if you run into any problems or edge cases. Ryan IMG_0739.png 93KViewDownload IMG_0738.png 75KViewDownload
Re: [twitter-dev] Re: Mobile OAuth fix is LIVE
In fact, I'd recommend that you only show the new version for devices you have actually tested against... Mobile browser support is a crap shoot and you really can't assume that something that works on one device, works on another... You need to test each and every one of them (or at least each family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS, Motorola V3 series, etc.) I've been in mobile development for 15 years... Let me know if you need some pointers off list... Happy to assist. On 2/5/10 8:40 AM, CharlesW cwilt...@gmail.com wrote: Ryan, Thanks for both the attempted fix and the announcement. Unfortunately, where the previous version was kind of a crapshoot for mobile users because the buttons appeared black (see my screenshot in the bug report at http://code.google.com/p/twitter-api/issues/detail?id=395), this new version doesn't work at all on many mobile browsers. Because this breaks mobile Twitter support completely for many (most? all?) phones using older browsers, can you please revert to the previous version, and then stage a new version somewhere else that we can help you test? -- Charles On Feb 3, 3:16 pm, Ryan Sarver rsar...@twitter.com wrote: FINALLY! An update has just gone live that fixes rendering of the OAuth screens for most mobile devices. We also fixed a few small nagging things like the default action is now allow instead of deny if you just hit go on an iPhone. I've attached two screenshots so you can see the updated screens. Please test it out with your various mobile web apps and let us know if you run into any problems or edge cases. Ryan IMG_0739.png 93KViewDownload IMG_0738.png 75KViewDownload
Re: [twitter-dev] Twitter based bug tracker/feedback system, anyone?
Anton, We have a system that bridges a Twitter ID to Best Practical's Request Tracker help desk. This is development grade stuff right now, not at all ready for paying customers, but I'm looking for early adopters. We could have a credible offering by the end of first quarter. Neal On Wed, Feb 3, 2010 at 1:03 PM, Anton Krasovsky anton.krasov...@gmail.comwrote: I wonder if anyone has a twitter based bugtracker / feedback system? Of course, there are many web based systems like that (uservoice, etc), but given that many of my users seem to have mostly mobile-based net access, leaving feedback for them is harder than it should be. Or if I start using twitter as a main feedback channel, it's going to be difficult to me to keep track of all these tweets. So, is there anything out there that could help me keep track of user feedback via twitter? Regards, Anton http://pavo.me j2me Twitter client -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717
[twitter-dev] Re: user_timeline returns too few values
See: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline Note: For backwards compatibility reasons, retweets are stripped out of the user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and Atom). If you'd like them included, you can merge them in from statuses retweeted_by_me. (http://apiwiki.twitter.com/Twitter- REST-API-Method%3A-statuses-retweeted_by_me) On Feb 2, 7:15 am, Horse chris.horsn...@meloncreative.co.uk wrote: For some reason when I request myuser_timelineit is only returning 7 results. Also if I use count to try and get 1 or 2 results it doesnt show any. I definitely have more than 7 tweets, so can someone point me in the right direction? http://twitter.com/statuses/user_timeline.xml?screen_name=meloncreative Also on my personal account it returns 18 http://twitter.com/statuses/user_timeline.xml?screen_name=h0rseh0rse Is it doing something strange with the RT's, as it could be extracting them from the 20 but not actually showing a full 20 results. Bit confused, can someone confirm?
Re: [twitter-dev] Re: Making the twitter user the default user of your application
On Thu, Feb 4, 2010 at 11:13 AM, hernangarcia hernan.gar...@gmail.com wrote: Hey man, good morning. If you are developing a web app, OAUTH is the way to go. I am using Twitter4J but for sure oauth-python-twitter has methods to do the same, this is what I do: after investigating a little more it seems python-twitter is kind of unmaintained. tweepy on the other hand support everything I need. it even has some nice example apps for the workflow. 1) Generate the authorization url using the twitter account of the app 2) I redirect the user to that URL which is twitter login form 3) Twitter redirects the user to a callback url I set up in the app account with the authentication tokens 4) I store those auth token in a DB where I also have the user profile So far so good. 5) Whenever I want to communicate with Twitter I retrieve those tokens from the storage and use them. This is where I get confused. Do you get one auth token per user and you have to link those to their profile? If I want to implement a remember me type of thing will I just pick the username check against the tokens storage and call the twitter API to see if he is a valid user? This is the app I am working on in case you wanna check the flow. Cheers!!! On Feb 4, 7:34 am, Jorge Vargas jorge.var...@gmail.com wrote: Hello, I'm a bit confused about how to go with this. Normally i'll expect a openID provider and then I'll code a consumer, howeverhttp://apiwiki.twitter.com/Sign-in-with-Twitterpoints out I need to run oauth. Also several searches point out that twitter will not be an openID provider anytime soon. So my question is how will you handle twitter-only accounts, for this particular app you *must* have a twitter account and I want to store additional info regarding each user in my app. In order words all I need to know is that you are who you claim to be on twitter to attribute actions on you. Should I got with oauth even though that's overkill in this particular application? If that is the case any one has usedhttp://code.google.com/p/oauth-python-twitteris it a good implementation?
Re: [twitter-dev] Re: Making the twitter user the default user of your application
On 2/5/2010 11:00 AM, Jorge Vargas wrote: On Thu, Feb 4, 2010 at 11:13 AM, hernangarciahernan.gar...@gmail.com wrote: Hey man, good morning. If you are developing a web app, OAUTH is the way to go. I am using Twitter4J but for sure oauth-python-twitter has methods to do the same, this is what I do: after investigating a little more it seems python-twitter is kind of unmaintained. tweepy on the other hand support everything I need. it even has some nice example apps for the workflow. 1) Generate the authorization url using the twitter account of the app 2) I redirect the user to that URL which is twitter login form 3) Twitter redirects the user to a callback url I set up in the app account with the authentication tokens 4) I store those auth token in a DB where I also have the user profile So far so good. 5) Whenever I want to communicate with Twitter I retrieve those tokens from the storage and use them. This is where I get confused. Do you get one auth token per user and you have to link those to their profile? If I want to implement a remember me type of thing will I just pick the username check against the tokens storage and call the twitter API to see if he is a valid user? Can users have multiple accounts associated with an IP address?
[twitter-dev] Re: Mobile OAuth fix is LIVE
That's an amazingly great recommendation, Michael. -- Charles On Feb 5, 9:22 am, Michael Steuer mste...@gmail.com wrote: In fact, I'd recommend that you only show the new version for devices you have actually tested against... Mobile browser support is a crap shoot and you really can't assume that something that works on one device, works on another... You need to test each and every one of them (or at least each family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS, Motorola V3 series, etc.) I've been in mobile development for 15 years... Let me know if you need some pointers off list... Happy to assist. On 2/5/10 8:40 AM, CharlesW cwilt...@gmail.com wrote: Ryan, Thanks for both the attempted fix and the announcement. Unfortunately, where the previous version was kind of a crapshoot for mobile users because the buttons appeared black (see my screenshot in the bug report athttp://code.google.com/p/twitter-api/issues/detail?id=395), this new version doesn't work at all on many mobile browsers. Because this breaks mobile Twitter support completely for many (most? all?) phones using older browsers, can you please revert to the previous version, and then stage a new version somewhere else that we can help you test? -- Charles On Feb 3, 3:16 pm, Ryan Sarver rsar...@twitter.com wrote: FINALLY! An update has just gone live that fixes rendering of the OAuth screens for most mobile devices. We also fixed a few small nagging things like the default action is now allow instead of deny if you just hit go on an iPhone. I've attached two screenshots so you can see the updated screens. Please test it out with your various mobile web apps and let us know if you run into any problems or edge cases. Ryan IMG_0739.png 93KViewDownload IMG_0738.png 75KViewDownload
Re: [twitter-dev] Re: Mobile OAuth fix is LIVE
Ill talk with the team and figure out if it's better to roll it back or just limit it to the known, working user agents On Fri, Feb 5, 2010 at 3:42 PM, CharlesW cwilt...@gmail.com wrote: That's an amazingly great recommendation, Michael. -- Charles On Feb 5, 9:22 am, Michael Steuer mste...@gmail.com wrote: In fact, I'd recommend that you only show the new version for devices you have actually tested against... Mobile browser support is a crap shoot and you really can't assume that something that works on one device, works on another... You need to test each and every one of them (or at least each family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS, Motorola V3 series, etc.) I've been in mobile development for 15 years... Let me know if you need some pointers off list... Happy to assist. On 2/5/10 8:40 AM, CharlesW cwilt...@gmail.com wrote: Ryan, Thanks for both the attempted fix and the announcement. Unfortunately, where the previous version was kind of a crapshoot for mobile users because the buttons appeared black (see my screenshot in the bug report athttp:// code.google.com/p/twitter-api/issues/detail?id=395), this new version doesn't work at all on many mobile browsers. Because this breaks mobile Twitter support completely for many (most? all?) phones using older browsers, can you please revert to the previous version, and then stage a new version somewhere else that we can help you test? -- Charles On Feb 3, 3:16 pm, Ryan Sarver rsar...@twitter.com wrote: FINALLY! An update has just gone live that fixes rendering of the OAuth screens for most mobile devices. We also fixed a few small nagging things like the default action is now allow instead of deny if you just hit go on an iPhone. I've attached two screenshots so you can see the updated screens. Please test it out with your various mobile web apps and let us know if you run into any problems or edge cases. Ryan IMG_0739.png 93KViewDownload IMG_0738.png 75KViewDownload
