[twitter-dev] Re: Are geotagged tweets visually apparent?
Use a Twitter service that does, such ashttp://bccth.is, to confirm successful tagging of your tweets. Gotcha, thanks much. Jeffrey
[twitter-dev] It's been three months since the truncation change.... can't the docs be updated?
RE this thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cd95ce07be341223/e174915c3ea94e69?lnk=gstq=140 It's been three months since an apparently-silent not-backwards- compatible API change went into effect that causes tweets longer than 140 characters to be ignored, but generate a success reply with no way to know for sure whether the tweet was actually accepted, or why it might have been ignored if it was. The docs haven't even been updated... they still say that too-long tweets will be forcefully truncated (and marked as such in the reply). Since Twitter can diddle the text of the tweet, and it's apparently unclear exactly what Twitter might count as a character, there seems to be no way that an app can know ahead of time whether a tweet is within the limits, and no easy way to find out whether it's actually been accepted. Sigh.
[twitter-dev] Re: How to show An application would like to connect to your account EACH TIME users login into my service?
Abraham and others, Switching from oauth/authenticate to oauth/authorize was a solution for me... Thank you very much! On Feb 3, 6:59 am, Andy Freeman ana...@earthlink.net wrote: Huh? http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize does not mention force_login. http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate does. However, /oauth/authenticate leaves the user logged into twitter. On Feb 2, 12:00 pm, lalit goklani lgokl...@gmail.com wrote: You can also use 'force_login=true' parameter passed along with token while you are getting the authorization url for the link. That will always make user to login to twitter irrespective of they are logged in. -- Thanks. Lalit Twitter Facebook Application -http://www.twitsfb.com Article Directory -http://www.ezinearticles.biz Indian Mutual Funds -http://www.mutualfundsnavindia.com
Re: [twitter-dev] Mobile java client - happy with OAuth as it is
On Wed, Feb 3, 2010 at 5:02 AM, Jeff Enderwick jeff.enderw...@gmail.com wrote: App-engine is free to a point, and you do get (little) more than you pay for. But that scheme carries a heavy price: personally engraved downloads: one heavyweight op per subscriber (one-time though), That's not strictly necessary, as the app could potentially be downloaded untagged and then it could contact server on once it run for a first time to get it's ID. There are two problems though: 1. User has to go throuh a website to perform the OAuth authorization. 2. There should be a way to establish the link between user's OAuth tokens saved on the server, and an app. For example a PIN code could be used. having server-side resources proxy all mobile twitter interaction: way, way to heavy for no real functional benefit (and also less fault tolerant). That depends on the platform the app is written for. It would be an overkill for iPhone or Android, but j2me? I think the Snaptu which currenlty is the biggest j2me client out threre does it exactly like this. Also, it the mobile app is doing OAuth itself, it has to be given the application token and secret with all the security implications of doing this. Anton On Tue, Feb 2, 2010 at 1:02 PM, Abraham Williams 4bra...@gmail.com wrote: With the proliferation of services like Google App Engine finding free or cheap sever resources is easy. Abraham On Tue, Feb 2, 2010 at 06:09, ryan alford ryanalford...@gmail.com wrote: Another problem with this approach is that you are now required to have a server. So now a developer would have the added expense of paying for a server. Now if the developer already had a server, then it's a moot point, but not all developers have their own hosted servers. What happens when your server goes down, or your hosting provider has connectivity problems? Your app is now dead, even though Twitter is still functioning normally. Ryan On Tue, Feb 2, 2010 at 7:08 AM, Anton Krasovsky anton.krasov...@gmail.com wrote: With all that talk about OAuth, I thought I might share my experience using it in for a mobile (j2me) twitter client. I guess my approach is nothing new, and probably is not applicable to iPhone apps because of the appstore distribution process, but anyways. So the way I handle OAuth is as follows: All application downloads are handled by my own server. Before allowing user to download the app I initiate OAuth authorization with Twitter and then, save user tokens along with generated unique id for a user. Once authorized, user is permitted to download the application which is tagged with that unique user id I generated earlier. Once user starts the app, it uses it's id to authenticate itself to my server. All communicatin between Twitter and user's appication is handled/proxied by the server that performs all necessary oauth signing on behalf of the user. So, this way I have all benefits of using OAuth in a mobile app. The only drawback really, is that user must visit my web site at least once to perform authorization. Regards, Anton http://pavo.me -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Getting statuses/retweets in reverse order or getting more than the allowed 100 statuses count
Hello there, I couldn't found a way to get the retweets for a status in ASC order, right now it returns up to the 100 latest retweets and I want to get the X first ones, maybe paginated if allowed. Does anyone have an idea for this? Thanks in advance.
Re: [twitter-dev] It's been three months since the truncation change.... can't the docs be updated?
hi jeff. yup - we're definitely guilty for not yet putting an error code for when we reject a tweet due to length. we do, however, have this page http://apiwiki.twitter.com/Counting-Characters that we put up a month ago that explains how to count your characters correctly and to help define what twitter means by 140. On Wed, Feb 3, 2010 at 2:00 AM, Jeffrey Friedl jfri...@gmail.com wrote: RE this thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cd95ce07be341223/e174915c3ea94e69?lnk=gstq=140 It's been three months since an apparently-silent not-backwards- compatible API change went into effect that causes tweets longer than 140 characters to be ignored, but generate a success reply with no way to know for sure whether the tweet was actually accepted, or why it might have been ignored if it was. The docs haven't even been updated... they still say that too-long tweets will be forcefully truncated (and marked as such in the reply). Since Twitter can diddle the text of the tweet, and it's apparently unclear exactly what Twitter might count as a character, there seems to be no way that an app can know ahead of time whether a tweet is within the limits, and no easy way to find out whether it's actually been accepted. Sigh. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: How Does TwittPic Works ?
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 Team http://twitter.com/raffi
[twitter-dev] generate valid user id for twitter
hi. I'm doing a server context, which make calls to API methods and I would love to know how can I know user ID in general, without any prior id, or how to generate valid user id. I would serve very helpful, thanks
[twitter-dev] Twitter based bug tracker/feedback system, anyone?
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: How Does TwittPic Works ?
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
Re: [twitter-dev] Re: How Does TwittPic Works ?
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 Team http://twitter.com/raffi
[twitter-dev] Re: How Does TwittPic Works ?
Thanks! I installed Seesmic Look, but never thought of checking the Connections tab in Twitter. Crow does not taste all that bad with a thick layer of mustard and spices. On Feb 3, 3:49 pm, 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] False positives for uploading Image
Hello all
I've been using twitter functionality in my sites for a while now and
wanted to expand to uploading images to the users Background. After
following the oauth Spec for twitter background I was able to
successfully upload an image. Unfortuneatly, this does not always
work. Lately, more and more calls up to twitter are returning false
positives. Meaning that I make the request, and according to twitter
it executes successfully, however my BG Image does not change.
My response is as follows:
{verified:false,followers_count:
8,url:null,description:null,profile_text_color:0C3E53,status:
{in_reply_to_screen_name:null,favorited:false,in_reply_to_status_id:null,truncated:false,created_at:Wed
Feb 03 21:29:02 + 2010,source:a href=\http://www.webfetti.com
\ rel=\nofollow\Webfetti/a,in_reply_to_user_id:null,id:
8603955578,text:I just updated my twitter background using Webfetti
Check it out!
http://bit.ly/9joxaG},profile_background_image_url:http://a1.twimg.com/profile_background_images/72229696/image,created_at:Tue
Oct 20 21:55:54 +
2009,profile_link_color:FF,statuses_count:
76,profile_background_tile:false,notifications:false,profile_background_color:BADFCD,profile_image_url:http://
a3.twimg.com/profile_images/673971289/
image_normal,contributors_enabled:false,favourites_count:
1,lang:en,time_zone:null,friends_count:
7,profile_sidebar_fill_color:FFF7CC,protected:false,screen_name:whombaWork,following:false,location:null,name:andrew,geo_enabled:false,profile_sidebar_border_color:F2E195,id:
83934696,utc_offset:null}
So the problem is that According to twitter, everything went
perfectly, however according to my actual twitter profile, nothing
worked as it should have. Also, if you look at my
'profile_background_image_url' this shows my OLD background image, not
my new one.
I use exactly the same code to update my profile picture and it works
every time. The BG image size is within the size requirement and
dimensions.
Any help would be awesome. Thank you in advanced
[twitter-dev] Problems
Hello! I have such problem: my account http://twitter.com/MoscowTwestival has become suspended. I can't understand why? We decided to organize Twestival in Russia, and i have discussed all things with Amanda Rose about it. I think it is a mistake, can you improve it? Vadim Grekov
[twitter-dev] Re: Combining multiple API Searches into the Streaming API
Thanks for the feedback. Implementing the API was a lot easier then expected, my code is rather modular, so replacing the search component is easy. I only need one more step that actually breaks down the single stream output into matches per search I want to do. While it's an extra step in my process it's not a big deal in the end.
[twitter-dev] Re: Combining multiple API Searches into the Streaming API
I'll second Dewald's advice with one caveat. If you ever expect your search results to increase to a point where you're getting regular rate limiting (as :) and :( can certainly do that), I'd recommend looking into the Streaming API now. You'll have to add a lot of extra parsing and joining on your end, but it's the only way for your app to scale past the rate-limit point. If the app is simple, the collection volume isn't large, and you don't mind loosing tweets, the search api is way easier. On the other hand, you have to deal with all the additional logic for polling, handling rate limits, etc... you could put that effort into working on the merge operations for use with the raw streaming api. Jason (@jmstriegel) On Feb 2, 4:06 pm, Dewald Pretorius dpr...@gmail.com wrote: Ronald, In my opinion, if: a) You don't so much care about getting every single tweet that contains the keywords, but can live with the tweets being filtered and ranked for relevance (not a bad thing at all); b) You don't mind now and again getting a rate limit error; and c) You have search needs that the Streaming API does not satisfy, such as NEAR: and others. Then ___ continue to use the Search API For some uses, the Streaming API is a perfectly square hole. Don't try and force a round peg down the square hole. On Feb 2, 4:52 pm, Ronald ronald.bradf...@gmail.com wrote: I'm presently migrating some of my code base to the Streaming API, and I have a question regarding the filter/track syntax. Currently I run multiple searches on frequencies from 1 minute to 1 hour (based on output volume). Let's say for example the following 2 searches. happy OR sad and :) OR :( http://search.twitter.com/search?q=happy+OR+sadhttp://search.twitter With the streaming API filter and only one connection, it seems my only option is to combine these in to one filter i.e. track=happy,sad,:),:( I'm then required to do my own parsing to determine the actual source of the result. Hopefully I'm missing something here and I can separate track input and better identify the right result for the right search. Any help appreciated. Ronald
[twitter-dev] Re: Efficiency of Search VS Streaming API for some apps
That wasn't the answer I was hoping for, but thanks for the guidance. :) We're working on adding a new process that will use the streaming api to pull in tweets, then apply a merge operation for phrases and multi- term searches that produces an output similar to what the search api provided. There's more work to do on our end, but so far it looks like it's going to function on the existing hardware. I'll know for sure once we start pulling in the full term feed. Looking forward to consuming more tweets with the streaming api in the near future. Thanks for the push in the right direction! Jason (@jmstriegel) On Jan 28, 10:50 pm, John Kalucki j...@twitter.com wrote: The track resource on theStreamingAPI is intended for just this sort of application. Yes, there will be some over delivery, especially if you intend to logically AND low frequency words with high frequency words. In the end, this is a minor amount of additional bandwidth and processing cost. Processing 1, 10, or 100 per second costs about the same. You should be able to do this volume post-processing at your end on a single core. Searchresults will be increasingly filtered and ranked for relevance, which sounds like is not the results that you want. Whitelisting won't prevent this filtering. Additional track terms are not supported by opening additional connections to theStreamingAPI. Instead, you place more predicates on the same stream. The higher access levels support hundreds of thousands of predicates. Opening many connections to theStreamingAPI will appear like an attempt to circumvent existing rate limits and you are likely to be banned from all twitter.com access. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Jan 28, 2010 at 6:15 PM, Jason Striegel jason.strie...@gmail.com wrote: We started running into rate limiting issues today with one of our applications that uses theSearchAPI (squawq.com). We're using it to track user-defined queries for a bunch of folks and provide analytics on those searches. It seems like developers are being asked to migrate to theStreamingAPI, but I'm worried it's going to be _way_ less efficient than how we're currently using theSearchAPI. Most of the terms we are tracking are relatively low volume and contain complexsearchAND type keyword phrases. ex: [twitter development OR twitterdev OR twitter api]. Most of these are low volume and we can poll a couple times an hour very efficiently. The problem is that as we gain more users, the number of these low- volume terms increases. So a second user might be tracking [coke OR coca cola], and a third user might track [first lego league OR legoleague], and so on. To be able to support this with theStreaming API we would either have to pull a gigantor amount of tweets in through the firehose (assuming we had access) and implement another layer of indexing, or we'd have to set up a stream for eachsearcha user has created, again pulling in way more data than we do currently, but also requiring many concurrent connections and needing to do the join behavior after the fact. Long story short, I totally see how thestreamingapi has made things super efficient for a number of applications. For our Squawq app, however, it seems to be the worst possible scenario: way more bandwidth intensive, requiring more connections to support all the different searches we are running on behalf of our users, and adding a huge amount of processing, storage and software complexity to the process. All for what seemed like a relatively lightweight, low- bandwidth process with thesearchapi. Anyone have any ideas for making thestreamingapi work well in this scenario? Can the Twitter team still whitelistsearchapi users that have this sort of need? Thanks in advance for any feedback or recommendations. @jmstriegel
Re: [twitter-dev] Re: How Does TwittPic Works ?
That is definitely good news, thanks for the update. -Ted On Wed, Feb 3, 2010 at 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.comwrote: 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. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: How Does TwittPic Works ?
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? it will be available publicly soon! Excellent! -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Two rules for ultimate life satisfaction: 1) Don't tell people everything. -
[twitter-dev] Re: Problems
Hi Vadim, I see that you've filed a ticket about this too, and our Support team should reply there soon. Brian On Feb 3, 11:10 am, Vadim Grekov vgi...@gmail.com wrote: Hello! I have such problem: my accounthttp://twitter.com/MoscowTwestival has become suspended. I can't understand why? We decided to organize Twestival in Russia, and i have discussed all things with Amanda Rose about it. I think it is a mistake, can you improve it? Vadim Grekov
[twitter-dev] Re: Mobile OAuth fix is LIVE
w0t! :D
[twitter-dev] Re: Mobile OAuth fix is LIVE
thank you x1000 This is great and works well too! On Feb 3, 11:25 pm, Swap rh.swar...@gmail.com wrote: w0t! :D
[twitter-dev] Re: Unable to register this application. Check your registration settings.I am
This is likely an issue related to your Twitter account. Please file a ticket at http://help.twitter.com/tickets/new and our Support team will take a look. Brian On Feb 2, 3:53 pm, kprobe goo...@kprobe.com wrote: I am finally going to upgrade my existing Twitter application to use OAuth and in trying to register that app I get the message Unable to register this application. Check your registration settings. What on earth does this mean? There is no additional information as to what is wrong. Mark
Re: [twitter-dev] Re: Mobile OAuth fix is LIVE
ZOMG *faints* one small nit: the redirect back to the app seemed to take longer than it should. not sure what the redirect timeout is, but it might do well to shorten it up by a second or two... otherwise ppl might start to get click-happy while nothing is happening. -Chad On Wed, Feb 3, 2010 at 3:26 PM, Rich rhyl...@gmail.com wrote: thank you x1000 This is great and works well too! On Feb 3, 11:25 pm, Swap rh.swar...@gmail.com wrote: w0t! :D
[twitter-dev] Bulk User Look Up - any progress?
Hi Raffi et al, Is there any word on when we might see a bulk user lookup API, as promised repeatedly in this group? For those of us using the social graph APIs, it¹s incredibly painful to then have to fetch the full user object based on the ID one-by-one. Anyway, would just love to know if this is on the horizon or if we should all continue to dream about this... Thanks, Michael
[twitter-dev] .NET and oAuth update problems
has anybody on a .NET library had problems with doing an oAuth connection and then posting an update with special characters such as !? We're having that problem on TwitterVB and I wanted to know if somebody has gotten it fixed yet?
Re: [twitter-dev] .NET and oAuth update problems
Are you following the proper URL encoding? Basic .NET URLEncode doesn't meet OAuth's encoding spec. I forget what it is offhand, but they aren't 100% equivalent. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Feb 3, 2010 at 6:50 PM, John Meyer john.l.me...@gmail.com wrote: has anybody on a .NET library had problems with doing an oAuth connection and then posting an update with special characters such as !? We're having that problem on TwitterVB and I wanted to know if somebody has gotten it fixed yet?
Re: [twitter-dev] Mobile OAuth fix is LIVE
Thanks for finally fixing this! One small detail: would be nice if the username field didn't automatically capitalize the first character. Ianiv Schweber ia...@blogaholics.ca Twitter: @ianiv Skype: ianivs Public Key: http://www.blogaholics.ca/ianivpubkey.asc On 2010-02-03, at 3:16 PM, Ryan Sarver 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.pngIMG_0738.png
[twitter-dev] Re: Mobile OAuth fix is LIVE
Thank you so much. This looks much better. On Feb 3, 4: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
[twitter-dev] Re: It's been three months since the truncation change.... can't the docs be updated?
we do, however, have this pagehttp://apiwiki.twitter.com/Counting-Charactersthat we put up a month ago that explains how to count your characters correctly and to help define what twitter means by 140. But can't you at least update the official API docs (where developers look for the final word on things)? Not doing so is just another way you show that you have no respect for third-party developers, essentially telling them to get lost. You don't have to have respect for third-party developers -- it's your site and you can do as you like -- but common sense should tell you that it behooves you to at least *try* to hide your contempt.
[twitter-dev] Re: OAuth on i products
An iPhone OS app can launch its own child browser control (UIWebView). On Feb 3, 11:24 am, Scott Herbert scott.a.herb...@googlemail.com wrote: Firstly I'm not an iPhone/iPad/iPod developer nore do I even own one, however I belive neigther of the two devices has the ablity to multi-task, so surely that would make oAuth on either impossabul, as the application couldn't call up a browser window/page. Hopefuly someone more skilled in Apple development can point out the error in my logic here.
[twitter-dev] Order of rate limiting with multiple predicates (Streaming API)
Is there any order or precedence to how tweets are selected for rate limiting when using the streaming api with many (hundreds to thousands) of filter predicates. I'm curious if rate limiting is applied to the higher volume predicates in a filter, before it's applied to lower volume ones. We collect tweets for many users based on search terms supplied by those users. With the search API, I could be sure that lower volume searches always returned complete results. I might miss results on extremely high volume searches, but most of the users would see no effects of rate limiting. With the streaming api, we have to combine all of the users' search terms into a single streaming filter. I'm worried that if one or two of those predicates has a super high volume which causes rate-limits, we could be missing tweets that match the lower volume predicates. Can one bad user supplied predicate spoil results for all of our other users? I'm concerned because I'm seeing a lot of limit events coming through and I can't tell which results we're missing. Is there a better way for me to be approaching this problem? Thanks! Jason (@jmstriegel)
[twitter-dev] Re: Mobile OAuth fix is LIVE
I've started testing it and it looks good. One comment, though. Is there any chance to move the PIN above the instructions?
Re: [twitter-dev] OAuth on i products
It is actually pretty easy. You save the request_token in your application and send the user to the browser to authorized access. When the user has finished authorizing the application they get directed back to the application by the iPhone through a custom protocol handler used as your callback URL. The user is now back in your application and the access_token can be retrieved. Abraham On Wed, Feb 3, 2010 at 11:24, Scott Herbert scott.a.herb...@googlemail.comwrote: Firstly I'm not an iPhone/iPad/iPod developer nore do I even own one, however I belive neigther of the two devices has the ablity to multi-task, so surely that would make oAuth on either impossabul, as the application couldn't call up a browser window/page. Hopefuly someone more skilled in Apple development can point out the error in my logic here. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] .NET and oAuth update problems
I have it working and have had it working for months. My code is open-source and written in C#. http://twiteclipseapi.codeplex.com/ I haven't tried every special character, though I haven't run across a character that didn't work. Ryan Sent from my DROID On Feb 3, 2010 6:53 PM, Andrew Badera and...@badera.us wrote: Are you following the proper URL encoding? Basic .NET URLEncode doesn't meet OAuth's encoding spec. I forget what it is offhand, but they aren't 100% equivalent. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Feb 3, 2010 at 6:50 PM, John Meyer john.l.me...@gmail.com wrote: has anybody on a .NE...
[twitter-dev] Re: Mobile OAuth fix is LIVE
Did the element id change? I was using this piece of code (iphone) to
get the oauth_id, and it's no longer working since around when these
new changes got pushed -
NSString*authPin = [[_webView
stringByEvaluatingJavaScriptFromString:
@document.getElementById('oauth_pin').innerHTML]
stringByTrimmingCharactersInSet: [NSCharacterSet
whitespaceAndNewlineCharacterSet]];
On Feb 3, 3:53 pm, Fernando Olivares aeris@gmail.com wrote:
I've started testing it and it looks good. One comment, though. Is
there any chance to move the PIN above the instructions?
Re: [twitter-dev] generate valid user id for twitter
I'm not entirely sure what you mean but have a look at http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Abraham On Wed, Feb 3, 2010 at 11:14, noelia martin amarali...@gmail.com wrote: hi. I'm doing a server context, which make calls to API methods and I would love to know how can I know user ID in general, without any prior id, or how to generate valid user id. I would serve very helpful, thanks -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] .NET and oAuth update problems
Interesting, for some reason I thought there were a few explicit exceptions that had to be made, but your solution looks pretty elegant. --ab On Wed, Feb 3, 2010 at 7:48 PM, ryan alford ryanalford...@gmail.com wrote: I have it working and have had it working for months. My code is open-source and written in C#. http://twiteclipseapi.codeplex.com/ I haven't tried every special character, though I haven't run across a character that didn't work. Ryan Sent from my DROID On Feb 3, 2010 6:53 PM, Andrew Badera and...@badera.us wrote: Are you following the proper URL encoding? Basic .NET URLEncode doesn't meet OAuth's encoding spec. I forget what it is offhand, but they aren't 100% equivalent. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Feb 3, 2010 at 6:50 PM, John Meyer john.l.me...@gmail.com wrote: has anybody on a .NE...
Re: [twitter-dev] Re: It's been three months since the truncation change.... can't the docs be updated?
we do, however, have this pagehttp:// apiwiki.twitter.com/Counting-Charactersthat we put up a month ago that explains how to count your characters correctly and to help define what twitter means by 140. But can't you at least update the official API docs (where developers look for the final word on things)? Not doing so is just another way you show that you have no respect for third-party developers, essentially telling them to get lost. where would you like me to put that information? its linked off the http://apiwiki.twitter.com/FAQ page since we wrote it? proactively, i'm changing the statuses over 140 characters on the status/update page to link to that page as well. You don't have to have respect for third-party developers -- it's your site and you can do as you like -- but common sense should tell you that it behooves you to at least *try* to hide your contempt. i'm not going to bother responding to this one, except to say that i'm at home, stuck in bed with a nasty cold, and i'm still monitoring the mailing list to see if i can help developers out :P -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] .NET and oAuth update problems
I don't want to take credit for it as it is from Shannon Whitley's OAuth library. Ryan Sent from my DROID On Feb 3, 2010 7:53 PM, Andrew Badera and...@badera.us wrote: Interesting, for some reason I thought there were a few explicit exceptions that had to be made, but your solution looks pretty elegant. --ab On Wed, Feb 3, 2010 at 7:48 PM, ryan alford ryanalford...@gmail.com wrote: I have it working ...
Re: [twitter-dev] .NET and oAuth update problems
From Shannon's original stuff, or something more recent? I'd worked with OAuthBase.cs in the past, but seemed to recall there were explicit exceptions in that ver of that stuff ... maybe a year ago now? --ab On Wed, Feb 3, 2010 at 7:57 PM, ryan alford ryanalford...@gmail.com wrote: I don't want to take credit for it as it is from Shannon Whitley's OAuth library. Ryan Sent from my DROID On Feb 3, 2010 7:53 PM, Andrew Badera and...@badera.us wrote: Interesting, for some reason I thought there were a few explicit exceptions that had to be made, but your solution looks pretty elegant. --ab On Wed, Feb 3, 2010 at 7:48 PM, ryan alford ryanalford...@gmail.com wrote: I have it working ...
[twitter-dev] non-ASCII Twitter screen names
Just FYI, Twitter screen names are not (or, apparently, didn't use to be) restricted to 0-9A-Z-_ id6295462/id screen_nameMagic carpet1/screen_name id3939231/id screen_nameWalking the dog2/screen_name id92595586/id screen_nameIts mine\nM2/screen_name We're also seeing non-ASCII in some other screen names. (Though we don't currently know what they are... we just know they exist! ;) We're assuming this is a vestige of long ago coding? It does screw up our desire to use ascii char(15) in db... Maybe Twitter can fix?
[twitter-dev] Re: Mobile OAuth fix is LIVE
'oauth_pin' element id got changed to 'oauth-pin' for anyone else who's stuff broke On Feb 3, 3:53 pm, Fernando Olivares aeris@gmail.com wrote: I've started testing it and it looks good. One comment, though. Is there any chance to move the PIN above the instructions?
Re: [twitter-dev] .NET and oAuth update problems
I don't know which version(if there are multiple versions). I downloaded it in October I believe. Ryan Sent from my DROID On Feb 3, 2010 7:59 PM, Andrew Badera and...@badera.us wrote: From Shannon's original stuff, or something more recent? I'd worked with OAuthBase.cs in the past, but seemed to recall there were explicit exceptions in that ver of that stuff ... maybe a year ago now? --ab On Wed, Feb 3, 2010 at 7:57 PM, ryan alford ryanalford...@gmail.com wrote: I don't want to tak...
[twitter-dev] Re: non-ASCII Twitter screen names
Hm, wait... this account was created in Nov 2009 and has spaces and a \n in his screen_name?? http://twitter.com/users/show.xml?user_id=92595586 On Feb 3, 4:59 pm, PJB pjbmancun...@gmail.com wrote: Just FYI, Twitter screen names are not (or, apparently, didn't use to be) restricted to 0-9A-Z-_ id6295462/id screen_nameMagic carpet1/screen_name id3939231/id screen_nameWalking the dog2/screen_name id92595586/id screen_nameIts mine\nM2/screen_name We're also seeing non-ASCII in some other screen names. (Though we don't currently know what they are... we just know they exist! ;) We're assuming this is a vestige of long ago coding? It does screw up our desire to use ascii char(15) in db... Maybe Twitter can fix?
Re: [twitter-dev] Re: Mobile OAuth fix is LIVE
It is working correctly on a G1 running Android, but getting the non mobile version on a Nexus One. User-Agent is *Mozilla/5.0 (Linux; U; Android 2.1; en-us; Nexus One Build/ERD79) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17*
Re: [twitter-dev] False positives for uploading Image
hi!
hmm - you may be tripping over a known issue where we don't update the
status objects coming from the api correctly. if you do a users/show call
and look at your account, did that get updated after you upload?
just to give some background - we embed the user object inside the status
object in the API (if you call any one of the timelines and get an array of
status objects back, you'll notice that each has the full details of the
user inside). its actually an expensive-ish operation for us to invalidate
all those objects in your entire timeline when you change something in your
user object. we're currently still working out ways around that issue.
On Wed, Feb 3, 2010 at 1:51 PM, whomba andrew.l...@gmail.com wrote:
Hello all
I've been using twitter functionality in my sites for a while now and
wanted to expand to uploading images to the users Background. After
following the oauth Spec for twitter background I was able to
successfully upload an image. Unfortuneatly, this does not always
work. Lately, more and more calls up to twitter are returning false
positives. Meaning that I make the request, and according to twitter
it executes successfully, however my BG Image does not change.
My response is as follows:
{verified:false,followers_count:
8,url:null,description:null,profile_text_color:0C3E53,status:
{in_reply_to_screen_name:null,favorited:false,in_reply_to_status_id:null,truncated:false,created_at:Wed
Feb 03 21:29:02 + 2010,source:a href=\http://www.webfetti.com
\ rel=\nofollow\Webfetti/a,in_reply_to_user_id:null,id:
8603955578,text:I just updated my twitter background using Webfetti
Check it out!
http://bit.ly/9joxaG},profile_background_image_url:;
http://a1.twimg.com/profile_background_images/72229696/image
,created_at:Tue
Oct 20 21:55:54 +
2009,profile_link_color:FF,statuses_count:
76,profile_background_tile:false,notifications:false,profile_background_color:BADFCD,profile_image_url:http://
a3.twimg.com/profile_images/673971289/
image_normal,contributors_enabled:false,favourites_count:
1,lang:en,time_zone:null,friends_count:
7,profile_sidebar_fill_color:FFF7CC,protected:false,screen_name:whombaWork,following:false,location:null,name:andrew,geo_enabled:false,profile_sidebar_border_color:F2E195,id:
83934696,utc_offset:null}
So the problem is that According to twitter, everything went
perfectly, however according to my actual twitter profile, nothing
worked as it should have. Also, if you look at my
'profile_background_image_url' this shows my OLD background image, not
my new one.
I use exactly the same code to update my profile picture and it works
every time. The BG image size is within the size requirement and
dimensions.
Any help would be awesome. Thank you in advanced
--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
[twitter-dev] Re: Mobile OAuth fix is LIVE
this broke my code - in case anyone needs it and didn't notice, the oauth element id changed from 'oauth_pin' to 'oauth-pin'. On Feb 3, 4:56 pm, Will Fleming wflemin...@gmail.com wrote: It is working correctly on a G1 running Android, but getting the non mobile version on a Nexus One. User-Agent is *Mozilla/5.0 (Linux; U; Android 2.1; en-us; Nexus One Build/ERD79) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17*
Re: [twitter-dev] Re: non-ASCII Twitter screen names
Huh. I wonder if they can still sign in... You can also see one of them on the web here http://twitter.com/account/redirect_by_id?id=92595586 Other then an account here and there, from what was probably a bug in the validation code, there should be no accounts being created with such characters. crosses fingers Abraham On Wed, Feb 3, 2010 at 17:03, PJB pjbmancun...@gmail.com wrote: Hm, wait... this account was created in Nov 2009 and has spaces and a \n in his screen_name?? http://twitter.com/users/show.xml?user_id=92595586 On Feb 3, 4:59 pm, PJB pjbmancun...@gmail.com wrote: Just FYI, Twitter screen names are not (or, apparently, didn't use to be) restricted to 0-9A-Z-_ id6295462/id screen_nameMagic carpet1/screen_name id3939231/id screen_nameWalking the dog2/screen_name id92595586/id screen_nameIts mine\nM2/screen_name We're also seeing non-ASCII in some other screen names. (Though we don't currently know what they are... we just know they exist! ;) We're assuming this is a vestige of long ago coding? It does screw up our desire to use ascii char(15) in db... Maybe Twitter can fix? -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Re: non-ASCII Twitter screen names
Crumbs. This has the potential to really jerk me around. On Feb 3, 9:03 pm, PJB pjbmancun...@gmail.com wrote: Hm, wait... this account was created in Nov 2009 and has spaces and a \n in his screen_name?? http://twitter.com/users/show.xml?user_id=92595586 On Feb 3, 4:59 pm, PJB pjbmancun...@gmail.com wrote: Just FYI, Twitter screen names are not (or, apparently, didn't use to be) restricted to 0-9A-Z-_ id6295462/id screen_nameMagic carpet1/screen_name id3939231/id screen_nameWalking the dog2/screen_name id92595586/id screen_nameIts mine\nM2/screen_name We're also seeing non-ASCII in some other screen names. (Though we don't currently know what they are... we just know they exist! ;) We're assuming this is a vestige of long ago coding? It does screw up our desire to use ascii char(15) in db... Maybe Twitter can fix?
Re: [twitter-dev] Bulk User Look Up - any progress?
Michael, It is definitely on our near-term roadmap, but we've gotten backed up on a few other things. So it is still coming, but I don't have an exact date for you. Social graph relief is neigh :) Best, Ryan On Wed, Feb 3, 2010 at 3:39 PM, Michael Steuer mste...@gmail.com wrote: Hi Raffi et al, Is there any word on when we might see a bulk user lookup API, as promised repeatedly in this group? For those of us using the social graph APIs, it’s incredibly painful to then have to fetch the full user object based on the ID one-by-one. Anyway, would just love to know if this is on the horizon or if we should all continue to dream about this... Thanks, Michael
[twitter-dev] Limit on number of concurrent requests
Hi there, Is there a limit on the number of requests that will be processed per IP concurrently? I've been playing about and it seems to make 100 requests, the responses come back in roughly the same total time whether I use 10 or 100 threads. Still digging to see if it's something at my end holding things back. Tim.
[twitter-dev] Re: non-ASCII Twitter screen names
I'm speculating, but I wonder if you do a blind form post to change usernames with non-ascii characters whether it will accept them? I think part of the validation by Twitter is done client-side (or so it appears), and that the Twitter databases store screen_name in utf-8 rather than ascii. I searched my database and found a number of Twitter screen names with spaces. But we have been getting a number of warnings about non-ascii characters... no idea what these are yet (as our database won't hold them as we (wrongly) assumed that they would only be ascii). But I am warn'ing them out and will report what I find. It would be rather crazy to find, say, a single character Chinese Twitter screen name! On Feb 3, 5:49 pm, Abraham Williams 4bra...@gmail.com wrote: Huh. I wonder if they can still sign in... You can also see one of them on the web herehttp://twitter.com/account/redirect_by_id?id=92595586 Other then an account here and there, from what was probably a bug in the validation code, there should be no accounts being created with such characters. crosses fingers Abraham On Wed, Feb 3, 2010 at 17:03, PJB pjbmancun...@gmail.com wrote: Hm, wait... this account was created in Nov 2009 and has spaces and a \n in his screen_name?? http://twitter.com/users/show.xml?user_id=92595586 On Feb 3, 4:59 pm, PJB pjbmancun...@gmail.com wrote: Just FYI, Twitter screen names are not (or, apparently, didn't use to be) restricted to 0-9A-Z-_ id6295462/id screen_nameMagic carpet1/screen_name id3939231/id screen_nameWalking the dog2/screen_name id92595586/id screen_nameIts mine\nM2/screen_name We're also seeing non-ASCII in some other screen names. (Though we don't currently know what they are... we just know they exist! ;) We're assuming this is a vestige of long ago coding? It does screw up our desire to use ascii char(15) in db... Maybe Twitter can fix? -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Re: False positives for uploading Image
Awesome, well thank you for responding back so quickly! No, if i call
a users / show call new info is not updated. the response back from
the success call is also incorrect. I have expereinced this before
with other calls, and the way i've gotten around it in the past, and
implemented it here also, has been by adding an extra variable to the
end of multipart request and signing it. Timestamp seems to work
well. We here figured you guys just cached items during peak times.
Thank you very much once again for responding. Is there a bug ticket
to watch for this issue? Thanks!
-Andrew
On Feb 3, 8:09 pm, Raffi Krikorian ra...@twitter.com wrote:
hi!
hmm - you may be tripping over a known issue where we don't update the
status objects coming from the api correctly. if you do a users/show call
and look at your account, did that get updated after you upload?
just to give some background - we embed the user object inside the status
object in the API (if you call any one of the timelines and get an array of
status objects back, you'll notice that each has the full details of the
user inside). its actually an expensive-ish operation for us to invalidate
all those objects in your entire timeline when you change something in your
user object. we're currently still working out ways around that issue.
On Wed, Feb 3, 2010 at 1:51 PM, whomba andrew.l...@gmail.com wrote:
Hello all
I've been using twitter functionality in my sites for a while now and
wanted to expand to uploading images to the users Background. After
following the oauth Spec for twitter background I was able to
successfully upload an image. Unfortuneatly, this does not always
work. Lately, more and more calls up to twitter are returning false
positives. Meaning that I make the request, and according to twitter
it executes successfully, however my BG Image does not change.
My response is as follows:
{verified:false,followers_count:
8,url:null,description:null,profile_text_color:0C3E53,status:
{in_reply_to_screen_name:null,favorited:false,in_reply_to_status_id:null,truncated:false,created_at:Wed
Feb 03 21:29:02 + 2010,source:a href=\http://www.webfetti.com
\ rel=\nofollow\Webfetti/a,in_reply_to_user_id:null,id:
8603955578,text:I just updated my twitter background using Webfetti
Check it out!
http://bit.ly/9joxaG},profile_background_image_url:;
http://a1.twimg.com/profile_background_images/72229696/image
,created_at:Tue
Oct 20 21:55:54 +
2009,profile_link_color:FF,statuses_count:
76,profile_background_tile:false,notifications:false,profile_background_color:BADFCD,profile_image_url:http://
a3.twimg.com/profile_images/673971289/
image_normal,contributors_enabled:false,favourites_count:
1,lang:en,time_zone:null,friends_count:
7,profile_sidebar_fill_color:FFF7CC,protected:false,screen_name:whombaWork,following:false,location:null,name:andrew,geo_enabled:false,profile_sidebar_border_color:F2E195,id:
83934696,utc_offset:null}
So the problem is that According to twitter, everything went
perfectly, however according to my actual twitter profile, nothing
worked as it should have. Also, if you look at my
'profile_background_image_url' this shows my OLD background image, not
my new one.
I use exactly the same code to update my profile picture and it works
every time. The BG image size is within the size requirement and
dimensions.
Any help would be awesome. Thank you in advanced
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Limit on number of concurrent requests
Cancel that. 100 threads gives a much better result than 10 threads on my production servers in the states (Ubuntu). I wonder why it makes no/little difference on OSX Leopard from Australia.. Tim. On Thu, Feb 4, 2010 at 3:45 PM, Tim Haines tmhai...@gmail.com wrote: Hi there, Is there a limit on the number of requests that will be processed per IP concurrently? I've been playing about and it seems to make 100 requests, the responses come back in roughly the same total time whether I use 10 or 100 threads. Still digging to see if it's something at my end holding things back. Tim.
[twitter-dev] Re: Mobile OAuth fix is LIVE
Rocks! On Feb 3, 5: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] Order of rate limiting with multiple predicates (Streaming API)
We don't support per-keyword rate limiting, although this sounds like a fine feature. It might be best for uncurated keyword terms to hit the Search API until you understand their frequency, and then migrate them to Streaming. Perhaps if you save your high-access level account for your low-frequency terms, and then use a single default access account for high-frequency terms, you'll get the effect you are looking for -- full fidelity on most words, and a sampling on the high-frequency words -- and you can husband your Search API hits for testing new terms, complex queries, etc. Note that opening more than a handful of default access streams will appear as an attempt to circumvent the rate limit, so tread gently. We're trying to move automated repetitive searches over to Streaming keywords -- not all use cases -- although the more the better. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Feb 3, 2010 at 3:49 PM, Jason Striegel jason.strie...@gmail.comwrote: Is there any order or precedence to how tweets are selected for rate limiting when using the streaming api with many (hundreds to thousands) of filter predicates. I'm curious if rate limiting is applied to the higher volume predicates in a filter, before it's applied to lower volume ones. We collect tweets for many users based on search terms supplied by those users. With the search API, I could be sure that lower volume searches always returned complete results. I might miss results on extremely high volume searches, but most of the users would see no effects of rate limiting. With the streaming api, we have to combine all of the users' search terms into a single streaming filter. I'm worried that if one or two of those predicates has a super high volume which causes rate-limits, we could be missing tweets that match the lower volume predicates. Can one bad user supplied predicate spoil results for all of our other users? I'm concerned because I'm seeing a lot of limit events coming through and I can't tell which results we're missing. Is there a better way for me to be approaching this problem? Thanks! Jason (@jmstriegel)
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Ryan: If posting Hello World works and posting Hello world! fails, then the problem is not the presence or absence of the status parameter. These are libraries that were working until recently; it appears that something has changed on Twitter's end. Multiple users of multiple libraries are now reporting the issue. On Feb 2, 11:09 pm, ryan alford ryanalford...@gmail.com wrote: Remember that the status update is different from most of the other requests, because it adds the status parameter that is not in the other requests. This means that it needs to be part of the query string and also the signature. Leaving this out could cause an issue. Ryan Sent from my DROID On Feb 2, 2010 10:03 PM, ohauske ovonhau...@gmail.com wrote: Hi Ryan, I tried getting the home timeline and a couple of other methods and everything works, everything except the update status here's my request: http://twitter.com/statuses/update.xml?oauth_consumer_key=**oaut... I'm using this library http://code.google.com/p/oauth/ On Jan 29, 6:10 am, ryan alford ryanalford...@gmail.com wrote: Try getting the home timeline and... On Jan 28, 2010 11:14 PM, arian cabezas arian.cabe...@gmail.com wrote: Hi Ryan. I´m havi...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
And please forgive my obnoxious tone; I'm tired and frustrated. :) On Feb 4, 12:05 am, Duane Roelands duane.roela...@gmail.com wrote: Ryan: If posting Hello World works and posting Hello world! fails, then the problem is not the presence or absence of the status parameter. These are libraries that were working until recently; it appears that something has changed on Twitter's end. Multiple users of multiple libraries are now reporting the issue. On Feb 2, 11:09 pm, ryan alford ryanalford...@gmail.com wrote: Remember that the status update is different from most of the other requests, because it adds the status parameter that is not in the other requests. This means that it needs to be part of the query string and also the signature. Leaving this out could cause an issue. Ryan Sent from my DROID On Feb 2, 2010 10:03 PM, ohauske ovonhau...@gmail.com wrote: Hi Ryan, I tried getting the home timeline and a couple of other methods and everything works, everything except the update status here's my request: http://twitter.com/statuses/update.xml?oauth_consumer_key=**oaut... I'm using this library http://code.google.com/p/oauth/ On Jan 29, 6:10 am, ryan alford ryanalford...@gmail.com wrote: Try getting the home timeline and... On Jan 28, 2010 11:14 PM, arian cabezas arian.cabe...@gmail.com wrote: Hi Ryan. I´m havi...
[twitter-dev] statuses/mentions for other users?
http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses-mentions: Returns the 20 most recent mentions (status containing @username) for the authenticating user. Is it possible to get this info for any other user than the authenticating one? I was expecting to be able to give this method user_id like to statuses/user_timeline and was surprised I can't do that. How should I get @replies to other people? Should I just do a search?
Re: [twitter-dev] Re: streaming apis + oauth
* John Kalucki jkalu...@gmail.com [091030 06:41]: Currently the Streaming APIs are not intended for use by clients, but mostly for use by services. Therefore oauth is not yet supported. There's little need to pass an end-user's credentials on to the Streaming API as all data currently available is public. Rather, your service can request all required data on behalf of your end users with a single account. The Streaming API uses Basic Authentication over a non-encrypted connection, only, right? This frightens me, a bit. Seems anyone with the ability to sniff traffic on the hosting provider's network could hijack my twitter account causing me no end of grief. Is there, or will there be, a more secure method of authentication for the Streaming API? -Marc
Re: [twitter-dev] Re: streaming apis + oauth
We have plans to support OAuth, but at the moment the Streaming API is mostly concerned with service integrations, so the password issue is far less of an issue there. Stay tuned. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Feb 3, 2010 at 9:46 PM, Marc Mims marc.m...@gmail.com wrote: * John Kalucki jkalu...@gmail.com [091030 06:41]: Currently the Streaming APIs are not intended for use by clients, but mostly for use by services. Therefore oauth is not yet supported. There's little need to pass an end-user's credentials on to the Streaming API as all data currently available is public. Rather, your service can request all required data on behalf of your end users with a single account. The Streaming API uses Basic Authentication over a non-encrypted connection, only, right? This frightens me, a bit. Seems anyone with the ability to sniff traffic on the hosting provider's network could hijack my twitter account causing me no end of grief. Is there, or will there be, a more secure method of authentication for the Streaming API? -Marc
Re: [twitter-dev] Re: It's been three months since the truncation change.... can't the docs be updated?
On Wed, Feb 3, 2010 at 2:53 PM, Jeffrey Friedl jfri...@gmail.com wrote: Not doing so is just another way you show that you have no respect for third-party developers, essentially telling them to get lost. I find it terribly ironic when people complain that it is somehow contempt when a company does not document - 100% accurately - every last minute detail of its freely available and actively maintained API for third party developers. In my book, contempt is when they do not have one in the first place.
