Re: [twitter-dev] Twitter trends
Open a connection to the Streaming API (filter stream) and count the amount of incoming tweets. More information on http://dev.twitter.com/ Tom On 7/11/11 12:22 PM, Mohit T wrote: Hi there, I am doing research on how the gold prices in the market are affected by number of tweets. Hence does anybody know how I can get data on how many times gold is tweeted (preferably to lowest frequency, maybe 1 minute) or even 1 hour? If anybody can help me I would appreciate it very very much -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter trends
Yes, but you will have to do that by getting all the tweets and doing a count on them. The best way to get all these tweets is to use the streaming api (which will simply send all these tweets to you). I'm afraid I cannot reach dev.twitter.com atm - look for Streaming or filter.json. Tom On 7/11/11 3:08 PM, Mohit T wrote: You will have to break it down further. Sorry I am new to this area and my programming is not strong. Essentially I want a word count per minute of a keyword which is in a tweet I enter for the last 1 year. Can this be done? On Jul 11, 2:01 pm, Tom van der Woerdti...@tvdw.eu wrote: Open a connection to the Streaming API (filter stream) and count the amount of incoming tweets. More information onhttp://dev.twitter.com/ Tom On 7/11/11 12:22 PM, Mohit T wrote: Hi there, I am doing research on how the gold prices in the market are affected by number of tweets. Hence does anybody know how I can get data on how many times gold is tweeted (preferably to lowest frequency, maybe 1 minute) or even 1 hour? If anybody can help me I would appreciate it very very much -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Scheduled tweets
Start by using @abraham's TwitterOAuth (https://github.com/abraham/twitteroauth). Use the SSO tokens on dev.twitter.com so you don't have to authenticate with OAuth. To schedule the tweets: use a crontab entry or something like that. Tom On 7/11/11 12:39 PM, santhosh kumar wrote: Hi, I wonder if there is anyway to post tweets in a scheduled basis. I am creating an application from which I want the users to share their thoughts in twitter exactly at the time they set in publish on field. I guess I can do it using the curl library in PHP. Is there anyother better work around? Thanks. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter trends
No, the search API only goes a few (2-3) days back. Maybe some company has kept track of that information over the past years, but you can't do it with the tools Twitter gives you. Tom On 7/11/11 5:47 PM, Mohit T wrote: Say if I do not want streaming but I want historical tweets since creation of twitter? Is this possible? On Jul 11, 2:11 pm, Tom van der Woerdti...@tvdw.eu wrote: Yes, but you will have to do that by getting all the tweets and doing a count on them. The best way to get all these tweets is to use the streaming api (which will simply send all these tweets to you). I'm afraid I cannot reach dev.twitter.com atm - look for Streaming or filter.json. Tom On 7/11/11 3:08 PM, Mohit T wrote: You will have to break it down further. Sorry I am new to this area and my programming is not strong. Essentially I want a word count per minute of a keyword which is in a tweet I enter for the last 1 year. Can this be done? On Jul 11, 2:01 pm, Tom van der Woerdti...@tvdw.euwrote: Open a connection to the Streaming API (filter stream) and count the amount of incoming tweets. More information onhttp://dev.twitter.com/ Tom On 7/11/11 12:22 PM, Mohit T wrote: Hi there, I am doing research on how the gold prices in the market are affected by number of tweets. Hence does anybody know how I can get data on how many times gold is tweeted (preferably to lowest frequency, maybe 1 minute) or even 1 hour? If anybody can help me I would appreciate it very very much -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter trends
I do not. Tom On 7/11/11 5:57 PM, Mohit T wrote: Ok if I cannot do it with tools twitter gives me, maybe you know any such companies like you mentioned? It would be a great help. On Jul 11, 4:49 pm, Tom van der Woerdti...@tvdw.eu wrote: No, the search API only goes a few (2-3) days back. Maybe some company has kept track of that information over the past years, but you can't do it with the tools Twitter gives you. Tom On 7/11/11 5:47 PM, Mohit T wrote: Say if I do not want streaming but I want historical tweets since creation of twitter? Is this possible? On Jul 11, 2:11 pm, Tom van der Woerdti...@tvdw.euwrote: Yes, but you will have to do that by getting all the tweets and doing a count on them. The best way to get all these tweets is to use the streaming api (which will simply send all these tweets to you). I'm afraid I cannot reach dev.twitter.com atm - look for Streaming or filter.json. Tom On 7/11/11 3:08 PM, Mohit T wrote: You will have to break it down further. Sorry I am new to this area and my programming is not strong. Essentially I want a word count per minute of a keyword which is in a tweet I enter for the last 1 year. Can this be done? On Jul 11, 2:01 pm, Tom van der Woerdti...@tvdw.eu wrote: Open a connection to the Streaming API (filter stream) and count the amount of incoming tweets. More information onhttp://dev.twitter.com/ Tom On 7/11/11 12:22 PM, Mohit T wrote: Hi there, I am doing research on how the gold prices in the market are affected by number of tweets. Hence does anybody know how I can get data on how many times gold is tweeted (preferably to lowest frequency, maybe 1 minute) or even 1 hour? If anybody can help me I would appreciate it very very much -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Telephone
There has never been a short code for the NL: we had to send texts to the UK (+44) and weren't able to receive any texts. I'm surprised to see it gone though. Tom On 7/7/11 10:33 PM, Scott Wilcox wrote: Whereas I thought there used to be a short code for Holland, seems there no longer/wasn't: https://support.twitter.com/articles/14226-how-to-find-your-twitter-short-code-or-long-code Twitter rarely comments on expansion of products like this, so for the mean time you're out of luck. On 7 Jul 2011, at 21:12, j_...@live.nl wrote: Well, I tried to set up ma number to ma twitter account, and I saw that you guys have the option, Afghanistan but not the netherlands? I dont get it they dont even have internet, I kniow that I ve bin there Well, can you guys add the option THE NETHERLANDS (+31) to? -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Fetching a user's entire timeline
Check for whether you include retweets. Tom On 7/4/11 12:34 PM, Adriaan Pelzer wrote: I'm not paging, but rather using a combination of max_id and count=200. Also - not getting nearly 200 every time, mostly below 100 Adriaan Pelzer putting you in touch with your crowds http://www.wewillraakyou.com twitter: http://www.twitter.com/adriaan_pelzer linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ skype: adriaan_pelzer +4478 7978 1743 On Mon, Jul 4, 2011 at 11:18 AM, Correa Denzil mcen...@gmail.com mailto:mcen...@gmail.com wrote: I am unable to reproduce the following error. I am able to paginate 200 tweets for 16 times. I am using OAuth for authentication. --Regards, Denzil On Mon, Jul 4, 2011 at 2:43 PM, Adriaan Pelzer adri...@wewillraakyou.com mailto:adri...@wewillraakyou.com wrote: We realise that we're not supposed to get 3200 (but 3200 minus spammed tweets), but we're only getting at most 2000 tweets. We don't want to retry too aggressively, it eats into the rate limits, and we're concerned the account might be flagged as abusive. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Application not getting R/W/DM access
1) Don't use xAuth 2) Don't use /oauth/authenticate but /oauth/authorize Tom On 7/5/11 1:20 AM, DaveH wrote: Twitter Team: My application was changed weeks ago to request DM permission. My understanding was all we needed to do was edit the settings for the app, and then re-authenticate the application. Which I did. When I look at the app settings it shows that Read, Write, Direct Messages is selected. However, when I go to authorize the application, I see that my application will not not be able to access DMs. This is a white listed app that needs access to DMs to work. From what I can tell, it should be able to authenticate and get DM access as the application is registered as needed DM level. So why is it not being allowed the correct access level? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Authentication dilemma
OAuth, but using the SSO keys provided to you on dev.twitter.com. Tom On 7/3/11 12:48 AM, george wrote: We have a website for internal use within our company. When a certain action occurs on the site, such as a survey being completed, we would like to have the app (our website) post a status update on our company's Twitter account. This process is supposed to be invisible to the user and cannot involve several steps (several requests being made by the browser). What is the proper authentication method for this? It used to be very easy with Basic Auth, but now I am confused. OAuth seems to be designed for Twitter user agents, which is not our case. The visitor of our website does not interact with Twitter in any way. Thanks, George -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Feedback wanted on Twitter + iOS
First of all, I think Twitter should make it more clear that this implementation is focused on providing Twitter access for non-client apps. Think of this implementation as a 'post on Twitter' feature that doesn't require any API knowledge or other very complicated stuff. That, and you have the ability to get some information about the user. I think it would be a very bad thing if this gave the app DM level access as that kind of access is either abused or for client apps and this framework isn't for either of those. What I noticed while studying the framework (and I'll avoid violating the Apple NDA here) is that the requests are signed using a fixed pair of credentials and always say 'from iOS'. It would be very nice to be able to make that say something like 'from appname on iOS' or something. I think that a LOT of devs are going to ask for that. I have some other ideas but they are improvements over the current framework and if I posted them on a public list I'd have to shoot you ;-) Tom On Jun 29, 2011, at 1:44 AM, Ryan Sarver rsar...@twitter.com wrote: Hey all, With iOS 5 and the Twitter integration coming in a few months, we have been getting a ton of inbound interest and questions around how to effectively leverage the Twitter integration. We wanted to get your feedback on how we can best support you and your users in developing meaningful experiences. I also hope you have had a chance to dig into the documentation and watch the WWDC session video. We've heard that it would be helpful for us to provide some standard graphics for use with your upcoming iOS integrations. We wanted to understand what types of buttons and styles would be most helpful. We think the most common use case is going to be Sign in with Twitter (SSO) but let us know what formats would be helpful. The two use cases that we're hearing the most interest around are: 1. Instant personalization - frictionless Single Sign-on (SSO) and social graph will allow apps to provide a personalized experience to their users with one click. What things can we provide to make this more effective for you. 2. Distribution - using the build-in Tweet Sheet functionality to post great content from your app out to the Twitter stream where it will drive engagement and clicks back to your application. Let us know if there are any other resources that would help make your Twitter iOS integrations easier on you or help you provide more value to your users on iOS. We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Ryan -- Ryan Sarver @rsarver -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Feedback wanted on Twitter + iOS
Absolutely disagree. No DM access via twitter.framework. Would be a major threat to the user's privacy. Tom On Jun 29, 2011, at 2:05 AM, Sean Heber s...@spiffytech.com wrote: Ryan, On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote: We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Simple, open up access to DMs via the API. This. l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Cannot connect to app that has same name as Account
I've seen @TweetDeck tweet from TweetDeck... Tom On 6/25/11 7:48 AM, modemlooper wrote: Say my account name is @MyApp and my app name is MyApp, it seems like you cannot sign into an app with OAuth if this is the case. Has anyone ever have this problem and if so what can I do about it? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Best practice for notifying users they need to re-authenticate before June 30th?
If you currently have no contact at all with your users, I can see how it might be a problem. However, almost all other apps have a way to do this: by simply asking them on the website / app. For example: my own app is a desktop client and it simply checks for permission and asks for a re-authentication via a modal popup on startup. A webapp wouldn't need this because a user simply re-authenticates on each login. Tom On 6/22/11 8:31 PM, Ryan wrote: Would love to get some guidance from Twitter or any other developers as I know there are plenty of other 3rd party apps out there that are in similar situations. I don't want to come across as Spammish, but is it possible to Spam your authenticated users? Not sure if I have many alternatives other than just waiting for people to email me angrily/confused why the app is no longer working. Thats going to be fun! Can't wait for June 30th! :) At least the fix is easy enough as simply re-authenticating. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Couldn't resolve host 'stream.twitter.com
Toms-MacBook-Pro:~ tom$ host stream.twitter.com stream.twitter.com has address 199.59.148.138 You should probably check your server's DNS settings. Tom On 6/15/11 10:47 PM, Perez2, Rocio (GE, Corporate, consultant) wrote: Hi!! I was using the Search API but now I want to change to Sream API. I have this doubt, I hope you can help me: First I try this: curlhttp://stream.twitter.com/1/statuses/sample.json?delimited=length -uAnyTwitterUser:Password Since prompt, but it return this: Couldn't resolve host 'stream.twitter.com Is there something wrong with my instruction? Or I'm missing something? I'd appreciated your help. Thank you J -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Needs object from desktop application ?
Woah there - sounds like you are hitting a rate limit. If you don't authenticate your calls, you may only make 150 API calls per hour. Tom On 6/10/11 12:54 AM, ari_endo wrote: Hello, I am developing Twitter AP with Excel VBA. When accessing with an object generated from twitter class, it works. But only with XMLHttpRequest (without object) it gets Woah there message. Is object-oriented programming needed when developing desktop applications? I need reference for desktop application. I appreciate if any site is introduced. Thank you in advance, Ari Endo -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Needs object from desktop application ?
I just checked and I was wrong - Woah there! can mean a lot of thnigs. 1. Make sure that your time is right 2. Make sure that the signature you make is right 3. Make sure that your endpoint starts with https://api.twitter.com/1/ 4. Make sure that you use valid credentials 5. Make sure that you are supplying all the required parameters 6. Make sure that your nonce is correct 7. Make sure everything else is correct Tom On 6/10/11 10:45 AM, Ari Endo wrote: Dear Tom, Never ever did I hit the rate limit. I call only once to get the authentication token. At most, only several times for trials. Thank you for your reply, Ari Tom van der Woerdt wrote (2011/06/10 17:38): Woah there - sounds like you are hitting a rate limit. If you don't authenticate your calls, you may only make 150 API calls per hour. Tom On 6/10/11 12:54 AM, ari_endo wrote: Hello, I am developing Twitter AP with Excel VBA. When accessing with an object generated from twitter class, it works. But only with XMLHttpRequest (without object) it gets Woah there message. Is object-oriented programming needed when developing desktop applications? I need reference for desktop application. I appreciate if any site is introduced. Thank you in advance, Ari Endo -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] When will we be able to upload images?
I documented the API in my post at https://groups.google.com/forum/#!topic/twitter-development-talk/mbRRzl2CWc4 I think that the API endpoint I documented is only available to those who can use the photo upload on the web and all iOS 5 users. I cannot tell you when the API is available to everyone, but I think it'll be slowly released to everyone, and when everyone can use it, the API will probably be officially announced. Tom PS: I found out that if you want to add several images to one post you should name all of those entities media[] - but that should go into that other topic. On 6/10/11 12:53 PM, Terence Eden wrote: I see that the new Official iOS Twitter App allows users of the Sainted iDevice to post photos (http://twitter.com/mariazverina/status/79134307079303168/) Any idea when this will be available to us lowly developers? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] How many tweets per day come through the Twitter firehose?
With 1 billion tweets per 6 days, I'd say about 150 million. Tom On 6/10/11 8:11 PM, Sam Jordan wrote: Hi, Just curious if anyone knows how many tweets per day come through the Twitter firehose on a daily basis, average? Thanks Sam -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter Mentions since_id
There's a : after oauth_consumer_key while there should be an =. There's
also an = (in oauth_signature) which should be URLencoded.
Tom
On 6/10/11 9:15 PM, Paul wrote:
This is my headers thats being send.
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth oauth_consumer_key: 0RaXE4T4CuMFJHI1jViEQ,
oauth_signature_method=HMAC-
SHA1,oauth_timestamp=1307733172,oauth_nonce=F0F2B456BC9606278FB345323D753CEC,oauth_version=1.0,
oauth_token=291935165-WqP8tSDqJyTewmsabMV7fiS7Y3ahxTXh60LSzFNb,
oauth_signature=VbTbuDqv+IZZQQoO1CUuvPXYGKo=
Host: api.twitter.com
Accept: text/html, */*
Accept-Encoding: identity
User-Agent: Mozilla/3.0 (compatible; Indy Library)
On May 23, 8:22 pm, Arnaud Meunierarn...@twitter.com wrote:
Hey Paul,
If you can, I recommend you use header-based OAuth (passing OAuth related
parameters in an Authorization header, instead of the query string).
Which signature base string are you using? Are you using a library? If yes,
could you share the code you're using? :)
Arnaud / @rnohttp://twitter.com/rno
On Sun, May 22, 2011 at 11:58 PM, Pauljpb@gmail.com wrote:
Im trying to get mentions using the since_id parameter. If I leave out
the since_id parameter I get all my mentions, which is correct, but as
soon as I add the since_id, I get 401, unauthorised. Since Im VERY new
to the twitter and oAuth API, it might be the way my string is made
up, but I need some help please.
http://api.twitter.com/1/statuses/mentions.json?since_id=1oauth_cons...{key}oauth_nonce={key}oauth_signature_method=HMAC-SHA1oauth_signature={key}oauth_timestamp=1306132513oauth_token={key}oauth_version=1.0
Where {key} are the correct values. I've tried adding the since_id at
the back but without any luck. From the source code it seems that the
signature is created on the base code of :
http://api.twitter.com/1/statuses/mentions.json?since_id=1and
afterwards the rest is added to that string.
Any ideas?
Thank you
--
Twitter developer documentation and resources:https://dev.twitter.com/doc
API updates via Twitter:https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Unwanted T.CO shortening
You can't with web intents and I believe that soon all links will be t.co links. Basically, live with it. If a bit.ly link gets wrapped in a t.co link, people will see the bit.ly link, not the t.co link, except for some clients which don't implement t.co links yet. Get used to it. Tom On 6/10/11 10:00 PM, Mo wrote: How do I register my domain as a URL shortener (like bit.ly or ow.ly) so that the links I post do not get shortened with a T.CO domain when I use intents? I just looked through some old tweets and apparently even those URLs have been replaced with T.CO. When someone looks at my tweet stream they should see the domains I post, not T.CO. If I want to talk about a friend or partners site, they should see that URL, not T.CO. If I want to help promote a non- profit like the Red Cross, Oil Spill Relief, Joplin, Missouri Tornado Relief, etc., they should see their URLs not T.CO. There was a time when developers were really rooting for Twitter. Moves like this only benefit Twitter AND are detrimental to everyone else. Not only is changing links to past tweets bad for developers, but for marketers as well. Not to mention that it borders on being unethical. Can you imagine Google, Facebook, Yahoo, or Bing replacing URLs with their shorteners? Of course, they could do it, if they chose to, but they won't. I realize it's your company, you have a great product, and you can do what you want. But, Twitter's success came on the backs of many dedicated developers, who also have the choice of putting their time elsewhere. If only there were an open source microblogging solution. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Request entity too large / The XML page cannot be displayed with retweet
You requested an answer from me on Twitter, so here I go.
1. The XML page cannot be displayed sounds like an error which your
webbrowser gives, definitely not the Twitter API.
2. If you use PHP, you should use JSON, not XML.
3. The code you provided is completely useless if I want to answer your
question.
4. You might want to use @abraham's TwitterOAuth class instead of
writing your own OAuth/cURL code. https://github.com/abraham/twitteroauth
5. You might like to set $resource before using it.
Tom
On 6/10/11 7:47 PM, Randomness wrote:
I just created some php code to retweet a tweet that meets certain
criteria. The code executes fine from one webserver when called from a
browser on my vista laptop. The same webpage gives an error mesage on
anoher XP machine like this:
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error
and then click the Refresh button, or try again later.
Only one top level element is allowed in an XML document. Error
processing resource
When called from another webserver (and any machine) I get the
following error message:
Request Entity Too Large
The requested resourcedoes not allow request data with POST
requests, or the amount of data provided in the request exceeds the
capacity limit
I suspect it has something to do with the Curl libraries but I can't
figure out what needs to be corrected. The Curl code looks like this
after all base and header stuff is done:
$_h = array('Expect:');
$_h[] = substr($header, 0);
$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, $resource);
curl_setopt($curl, CURLOPT_POST, true);
curl_setopt($curl, CURLOPT_CONNECTTIMEOUT, 2);
curl_setopt($curl, CURLOPT_TIMEOUT, 30);
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_HTTPHEADER, $_h);
$result = curl_exec($curl);
$resultArray = curl_getinfo($curl);
curl_close($curl);
$resource='http://api.twitter.com/1/statuses/retweet/'.
$thistweet.'.xml';
I am really stuck here and would appreciate some help
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Needs object from desktop application ?
A desktop authentication flow usually includes a callback with a custom scheme (myapp://redirect) or xAuth, while a server application will usually use a normal callback (http://example.com/callback) with the normal OAuth flow. However, this won't cause the Woah there! error you get. Just like anything else related to the programming itself: Twitter doesn't discriminate by programming language. As long as you are using the API correctly, it's fine. To answer your initial question: you can use C (non-object oriented language) and C++ (object-oriented language) and many other languages to interface with Twitter. It's an API, so it's all the same, as long as you can make a HTTP request. Tom On 6/11/11 2:17 AM, Ari Endo wrote: Dear Tom, Thank you for your quick support. I have checked all the items you listed below. What I would like to know is information for desktop application different from server application. I would appreciate if you tell me any. Thank you in advance, Ari Tom van der Woerdt さんは書きました (2011/06/10 17:50): I just checked and I was wrong - Woah there! can mean a lot of thnigs. 1. Make sure that your time is right 2. Make sure that the signature you make is right 3. Make sure that your endpoint starts with https://api.twitter.com/1/ 4. Make sure that you use valid credentials 5. Make sure that you are supplying all the required parameters 6. Make sure that your nonce is correct 7. Make sure everything else is correct Tom On 6/10/11 10:45 AM, Ari Endo wrote: Dear Tom, Never ever did I hit the rate limit. I call only once to get the authentication token. At most, only several times for trials. Thank you for your reply, Ari Tom van der Woerdt wrote (2011/06/10 17:38): Woah there - sounds like you are hitting a rate limit. If you don't authenticate your calls, you may only make 150 API calls per hour. Tom On 6/10/11 12:54 AM, ari_endo wrote: Hello, I am developing Twitter AP with Excel VBA. When accessing with an object generated from twitter class, it works. But only with XMLHttpRequest (without object) it gets Woah there message. Is object-oriented programming needed when developing desktop applications? I need reference for desktop application. I appreciate if any site is introduced. Thank you in advance, Ari Endo -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Unwanted T.CO shortening
What they do in the background is irrelevant for the general public and for the purpose of this discussion. I very much disagree on that it's not relevant. If Twitter clients implement t.co properly, it's nothing more than a background process. I haven't seen a t.co link in days, as I finally implemented automatic unshortening of t.co links in my client - just like a lot of other clients do. If a link gets automatically unshortened on display, it's effectively nothing more than a background process. Tom On 6/11/11 3:03 AM, Mo wrote: The shortened links I originally saw were all in HootSuite. I've since logged out and logged back in and the T.CO shortened URLs went away. However, my original question was never answered. Is there a process for getting on a list of approved shortened URLs? Ben, your screenshot and the tweet page do not have the same content in the mouseover. John, you're smoking something. I just checked Google, Facebook, Bing, and Yahoo with a search of the term PHP. None of the exposed URLs are shortened. What they do in the background is irrelevant for the general public and for the purpose of this discussion. Kosso, I'm with you on the unexpected destinations. In short, whoever is in control at Twitter is either not in direct communication with users and developers in regard to this or is simply not listening. -Mo On Jun 10, 2:23 pm, Ben Wardbenw...@twitter.com wrote: On Jun 10, 2011, at 1:21 PM, Kosso wrote: The massive trouble I have with all this is that I like to know what the hell I'm clicking on before clicking a link. It's kind of my right as a citizen of the web. I personally can't stand it when, for example a link fires up iTunes or goes to some site I don't want to waste (possibly mobile and limited) bandwidth on. I like to choose WHO I give MY visit/traffic to. To be clear, the API returns all the information for all clients to display the original short URL, and navigate via t.co. We also look up the full destination URL and return that too, allowing even clearer navigation of where you as a user will end up when following a link. You can see this implemented on twitter.com today: https://twitter.com/joshtpm/status/79283124747501568 * The URL destination points to t.co * The displayed text of the URL is a cropped and shortened version of the real URL * The title (tooltip) of the URL displays the full address of the destination. I've further illustrated it with a screenshot here:https://skitch.com/benward/frff8/ The documentation for the URL entities that provide all of this information in the API response is here:http://dev.twitter.com/pages/tweet_entities Ben -- Platform Developer, Twitter -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Translate app description to different languages
You can't, however I'd recommend that you file a bug report at http://code.google.com/p/twitter-api/issues/list Tom On 6/8/11 2:10 PM, Alver wrote: Good day. Is there any way to configure the application description so, that it will appear in the user interface language? As far as I can see in the app settings section - there is just one description field with no internationalization options. Please advise if there is any way to show my app's description in different languages depending on users language? Thanks in advance! -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] tweet id versus idStr
They aren't different. JavaScript can't handle large numbers (I think the limit was at 53 bits) so there's an id_str as well, to avoid this issue. In JavaScript, always use id_str. Tom On 6/7/11 10:28 AM, Christian Rishøj wrote: (Reposting from the twitter-anywhere-dev group.) In an @Anywhere application we are building at http://tweetshow.nu/ we would like to use the (as of yet unofficial and unsupported) in-browser object-oriented wrappers for the REST API for marking statuses as favourites. However, there seems to be some confusion with respect to the ids in the generated requests. Specifically, when we call someStatus.favourite() in our application, we see this (failed) request: • Request URL: https://api.twitter.com/1/favorites/create/77973769376894980.json • Request Method: POST • Status Code: 404 Not Found On the other hand, if we favourite the same status directly at http://twitter.com/, we see this request: • Request URL: http://api.twitter.com/1/favorites/create/77973769376894976.json • Request Method: POST • Status Code: 200 OK Notice that the ids don't match, even though it's the same status. Inspecting the status object, I noticed that both ids occur: • attributes: Object • contributors: null • coordinates: null • created_at: Tue Jun 07 05:42:49 + 2011 • favorited: false • geo: null • id: 77973769376894980 • id_str: 77973769376894976 • in_reply_to_screen_name: null • in_reply_to_status_id: null • in_reply_to_status_id_str: null It leaves me wondering: Why is id different from idStr? Why does the @Anywhere API seem to use the wrong attribute in generating the request? Any hints would be much appreciated. Best regards Christian -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] tweet id versus idStr
@Anywhere is just another javascript application - it shouldn't use id. Of course, when you inspect the object returned by @Anywhere you'll get the wrong values as well. Someone from Twitter should look into the favorite() one, it shouldn't be doing that. Tom On 6/8/11 11:52 PM, Christian Rishøj wrote: When I inspect the objects returned by @Anywhere, id and id_str are consistently different. Some examples: id: 78578304315179000 id_str: 78578304315179009 id: 78574658827460600 id_str: 78574658827460608 The IDs being used at twitter.com seem to be those of id_str. But why then is @Anywhere erroneously using the id when calling e.g. favourite() ? Christian On Jun 8, 2011, at 3:39 PM, Tom van der Woerdt wrote: They aren't different. JavaScript can't handle large numbers (I think the limit was at 53 bits) so there's an id_str as well, to avoid this issue. In JavaScript, always use id_str. Tom On 6/7/11 10:28 AM, Christian Rishøj wrote: (Reposting from the twitter-anywhere-dev group.) In an @Anywhere application we are building at http://tweetshow.nu/ we would like to use the (as of yet unofficial and unsupported) in-browser object-oriented wrappers for the REST API for marking statuses as favourites. However, there seems to be some confusion with respect to the ids in the generated requests. Specifically, when we call someStatus.favourite() in our application, we see this (failed) request: • Request URL: https://api.twitter.com/1/favorites/create/77973769376894980.json • Request Method: POST • Status Code: 404 Not Found On the other hand, if we favourite the same status directly at http://twitter.com/, we see this request: • Request URL: http://api.twitter.com/1/favorites/create/77973769376894976.json • Request Method: POST • Status Code: 200 OK Notice that the ids don't match, even though it's the same status. Inspecting the status object, I noticed that both ids occur: • attributes: Object • contributors: null • coordinates: null • created_at: Tue Jun 07 05:42:49 + 2011 • favorited: false • geo: null • id: 77973769376894980 • id_str: 77973769376894976 • in_reply_to_screen_name: null • in_reply_to_status_id: null • in_reply_to_status_id_str: null It leaves me wondering: Why is id different from idStr? Why does the @Anywhere API seem to use the wrong attribute in generating the request? Any hints would be much appreciated. Best regards Christian -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Twitter's iOS integration and what this means for developers
Folks, I just took a few minutes to go over the new APIs and while I am, of course, not going to break my NDA here, I can tell you this: * Doesn't look like this was meant for the Twitter clients, but rather the normal clients which provide a Tweet function. * You can sign requests using this framework, but with a fixed set of consumer credentials so that it will always say with iOS when sending a tweet (source). Like I said, it's almost only for providing a Tweet function. * I like it! Tom On 6/7/11 2:17 AM, TJ Luoma wrote: On Mon, Jun 6, 2011 at 8:05 PM, Jason Costajasonco...@twitter.com wrote: There have been a lot of questions about what the iOS announcement today means for developers. The integration points noted in Apple’s keynote create huge opportunities for both Twitter and iOS developers. The first question that everyone should be asking is: Will you hold off the DM Oauth reauthorization requirement until iOS 5 is released, so people don't have to go through it again and again and again for each Twitter app? And if not, why not? (Other than not giving a whit about 3rd party Twitter client app developers, but being more interested in helping developers of other apps integrate Twitter into their apps.) TjL -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re : Re: New Photo upload feature: What's new coming on the API side
Hey all, From a 'pretty reliable source' I got some information about the new API endpoint, how it works, etc. You probably won't be able to use it yet but I feel like sharing this information anyway :-) Endpoint: https://upload.twitter.com/1/statuses/update_with_media.json Parameters: * media (the image, I guess), * status (the text which you will also want), * probably all other ones which currently work with update.json (lat, lon, etc). *The API will give you a Not Found error!* This is because this is still an unreleased API and only a very select of clients has access to it. I currently don't have any information about how to upload several images (I guess you'd simply post another media item, but I don't know). Tom PS: I believe I just described an API which throws Not Found for all of you. Well done Tom, very convincing. On 6/6/11 6:16 PM, Arnaud Meunier wrote: Hey Julien, For now we're focusing on opening the Twitter Photo API endpoints to third party developers. These new API endpoints will be dedicated to Twitter media hosting, you won't be able to use them as a bridge/proxy for other media hosting services. Arnaud / @rno On Jun 6, 2011, at 7:25 AM, Julien Larios julien.lar...@gmail.com mailto:julien.lar...@gmail.com wrote: Hi there, I've implemented in Picsi this new way of photo sharing on Twitter (along with Twitpic support) and it works fine (based on Twitter4J 2.2.3). These pictures can be used in the 2 firsts Picsi apps: Media RSS export and ZIP backup But Arnaud (or should I say 'Dear Raptor fan' ? ;), do you know if external picture hosting services (like Twipitc) will be made available via this API branch? That would be great to grab all kind of photo via a single API syntax (instead of funky tweet parsing) Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Consumer Key and Secret Bug
API requests. Loading a page from https://api.twitter.com/1/ counts as 1 request. Of course, it goes per user per application, so the number of users isn't really relevant for iPhone applications. http://dev.twitter.com/pages/rate-limiting Tom On 6/5/11 10:39 PM, iDeviceDesigns wrote: On Jun 5, 1:22 pm, Tom van der Woerdti...@tvdw.eu wrote: Well, using more than 350 requests per hour most certainly gets you a permanent block... Tom On 6/5/11 7:53 PM, iDeviceDesigns wrote: Would you mind clearing that up a little? 350 request per hour? I have been reading about this but it does not make much sense to me. I am just creating application such as twitteriffic. I only call out for 100 tweets per timeline and as of right now I am the only one using this. So to clarify this...350 request per hour, would that include a NSLog? just logging the information to use to parse? I am quite confused to why their is a block or limit and what I can do to not hit that limit but still achieve retrieving data from twitter for an application that is estimated to have over 5,000 users when released? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re : Re: New Photo upload feature: What's new coming on the API side
I'm not Arnaud, but I can assure you that it won't happen. Tom On 6/6/11 4:25 PM, Julien Larios wrote: Hi there, I've implemented in Picsi this new way of photo sharing on Twitter (along with Twitpic support) and it works fine (based on Twitter4J 2.2.3). These pictures can be used in the 2 firsts Picsi apps: Media RSS export and ZIP backup But Arnaud (or should I say 'Dear Raptor fan' ? ;), do you know if external picture hosting services (like Twipitc) will be made available via this API branch? That would be great to grab all kind of photo via a single API syntax (instead of funky tweet parsing) Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Is that Python? Anyway, not relevant.
1. You aren't signing using the proper url.
2. You aren't using anything related to the signature on the request (req).
Tom
On 6/6/11 4:43 PM, Correa Denzil wrote:
Hi,
I am performing OAuth to sign my requests. I am not developing a web
app. I am trying to harvest some user data. Here's what I do :
import oauth2 as oauth
import time
CONSUMER_KEY = 'xx'
CONSUMER_SECRET = 'xx'
access_key = 'xx'
access_secret_key = 'xxx'
consumer = oauth.Consumer(CONSUMER_KEY, CONSUMER_SECRET)
token = oauth.Token(access_key, access_secret_key)
client = oauth.Client(consumer)
# Set the API end point
url = 'http://api.twitter.com/1'
params = {'oauth_version': 1.0,
'oauth_nonce': oauth.generate_nonce(),
'oauth_timestamp': int(time.time()),
'oauth_token': access_key,
'oauth_consumer_key': consumer.key,
'screen_name' : 'denzil_correa'
}
req = oauth.Request(method=GET, url=url, parameters=params)
# Sign the request.
signature_method = oauth.SignatureMethod_HMAC_SHA1()
req.sign_request(signature_method, consumer, token)
### Make the auth request ###
test = 'http://api.twitter.com/1/account/rate_limit_status.json'
resp, content = client.request(test, GET)
print resp
print content # prints 'ok'
Here's the output:
{reset_time:Mon Jun 06 14:54:50 +
2011,remaining_hits:132,hourly_limit:150,reset_time_in_seconds:1307372090}
Am I missing something?
--Regards,
Denzil
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. Tom On 6/6/11 4:54 PM, Correa Denzil wrote: Is that Python? : Yes 1. You aren't signing using the proper url. Is the end point URL wrong? 2. You aren't using anything related to the signature on the request (req) I am a newbie to Python. I am trying to dabble using OAuth. I understand the OAuth flow but somehow what I am doing seems a bit tangential to what OAuth is meant for. What should I do to rectify it ? --Regards, Denzil On Mon, Jun 6, 2011 at 8:16 PM, Tom van der Woerdti...@tvdw.eu wrote: You aren't using anything related to the signature on the request (req). -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
In the Make the auth request part you make a request using client instead of the already prepared and signed req variable. You should use req to make the request. Tom On 6/6/11 5:10 PM, Correa Denzil wrote: Tom : Thanks for the reply. 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. I have changed the same 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. I don't understand this point. What's the change am I supposed to make ? I have opened up a gist for easier editing : https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:30 PM, Tom van der Woerdti...@tvdw.eu wrote: 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Well, of course, don't literally replace the variables, but figure out a way to use the req object. I don't know anything about that object so I can't help you there. Tom On 6/6/11 5:28 PM, Correa Denzil wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, inmodule resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdti...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
In that case, try removing everything related to the req variable. Seems it's all unrelated to the actual request (unless the oauth library is very badly designed, of course). Line 22 all the way up to 35. Tom On 6/6/11 5:38 PM, Correa Denzil wrote: Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzilmcen...@gmail.com wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, inmodule resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdti...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Twitter and iOS - an Integration Workshop
What about the rest of the iOS developers who can't be there? I'm registered as an Apple Developer but I'm not there... Tom On 6/6/11 8:29 PM, Jason Costa wrote: Hi everyone, We're incredibly excited about the announcement that Apple made at WWDC today. We believe that Twitter's deep integration with iOS is going to open up a lot of exciting opportunities for developers. For your apps, this includes: - single sign-on and lightweight identity - taking advantage of the tweet sheet feature - the ability to tweet a photo from your app - pulling down a user's following graph and a whole lot more. As part of the announcement, we're looking to host a workshop at Twitter's headquarters this Wednesday (6/8) from 6:30pm to 8:30pm at 795 Folsom Street. At this event, we'll cover what the integration hooks mean for developers. Loren Brichter will also be talking about ABUIKit, a UI framework specifically for Mac, which we'll be open-sourcing. In order to attend, you'll need to first be registered as an Apple Developer - you can register with Apple here: http://developer.apple.com/programs/register/ Please also RSVP at the link below (with your Apple Developer login): http://bit.ly/jBX5B6 We hope you'll be able to join us for the evening. --@jasoncosta -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] t.co?
Anyone answering 'no' to this question is a fool: Twitter wants full control, t.co is a necessary part of it. Also, all official Twitter clients wrap t.co URLs, and afaik that's it. Of course, Tweet Button and web intents go in this category as well. Tom On 6/5/11 6:27 PM, SM wrote: When exactly do links get wrapped in t.co URLs? In the stream of people I follow, I've noticed more links getting wrapped this way recently, but it's not every single link. Will there be a time when every single link is wrapped with t.co? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Consumer Key and Secret Bug
Well, using more than 350 requests per hour most certainly gets you a permanent block... Tom On 6/5/11 7:53 PM, iDeviceDesigns wrote: Dear iDeviceDesigns, As you don't mention which route you are using, I can only make a guess. I make almost every query to Twitter using the maximum count from iOS (200 tweets w/ user info and entities). On startup I also go get the most recent 800+ tweets. My access tokens, as advertised, never expire. I am heavier user of the API, as you claim to use it, than you are and I do not see your reported behavior. Hence, without more specific data, I suggest that the problem is in your code. Anon, Andrew P.S. Most APIs that service hundreds of thousands of accesses every hour, as Twitter's APIs do, are really unlikely to exhibit this kind of bug. It would hit every client and web site. We would hear about it on this list. I am sorry I should have been more specific with the actual flow that I am using. I use MGTwitterEngine and OAuth which seems to work great and I searched through twitter API for IOS and it seemed to be the only library available. So I would assume most IOS developers are using this form of Twitters API The initial login in and redirect is just fine as well as ALL timelines such as followers list and replies ect et.. I receive ALL of the 20 objects I call out such as text, screen_names, description, user_profile_image ect ect... Then if I call out 100 objects everything works fine for around 10 minutes then just goes blank and nothing works for around 30 minutes and it has repeated this several times. So lets just say hypothetically it is within my codes which is a good possibility by your explanation could you or anyone else give a few reasons why a consumer key and secret would freeze up? I ask this because I am 99.9 percent positive the key is freezing up. It happens I walk away for 30 minutes and it works again or sometimes I have to reset the key and put the new key in my code As well as it affects the device that the code itself has yet to be run on so the devices code was still only calling out 20 and it works just fine then I was running the new code in the simulator and my device stopped receiving objects. What are a few things that makes a key freeze up? I have tried to look in Twitters documentations of an issue like this or of a occasion they might freeze the keys but can not seem to find a straight answer. Thanks I appreciate the insight. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
I'd like to point out that this is against the TOS. You should limit your API requests where possible - for a normal application with user interaction you won't need more than 350 per hour. If you do some sort of data analysis, you may need to use streams instead. Tom On 6/4/11 7:53 PM, Correa Denzil wrote: Tom : Thanks. I will create multiple user accounts. I guess about 20 (350 * 20 = 7000 considering 1 request per second) should solve my issue. --Regards, Denzil On Sat, Jun 4, 2011 at 3:35 AM, Tom van der Woerdti...@tvdw.eu wrote: If you authenticate, all requests (except for search) will go into the 350 requests. If you want 500, then perform 150 unauthenticated and 350 authenticated. If you need even more, use more accounts to do the requests. Tom On 6/3/11 11:06 PM, Correa Denzil wrote: Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Giffordja...@jamesrgifford.com wrote: The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzilmcen...@gmail.comwrote: Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
If you have the permission of the users, you can probably use their OAuth tokens, which gives you an almost infinite API limit (actually it's still 350 per user, but you won't easily break that). If you want to perform an analysis on a group of users without their consent (without OAuth access), you'll have to find a better way to do it. Tom On 6/4/11 8:12 PM, Correa Denzil wrote: Oh! I should avoid creating multiple user accounts in that case. I would like to perform analysis on a target set of users and not streams. How do I proceed? I should add that 350 requests per hour is highly insufficient for my use case. --Regards, Denzil On Sat, Jun 4, 2011 at 11:33 PM, Tom van der Woerdti...@tvdw.eu wrote: I'd like to point out that this is against the TOS. You should limit your API requests where possible - for a normal application with user interaction you won't need more than 350 per hour. If you do some sort of data analysis, you may need to use streams instead. Tom On 6/4/11 7:53 PM, Correa Denzil wrote: Tom : Thanks. I will create multiple user accounts. I guess about 20 (350 * 20 = 7000 considering 1 request per second) should solve my issue. --Regards, Denzil On Sat, Jun 4, 2011 at 3:35 AM, Tom van der Woerdti...@tvdw.euwrote: If you authenticate, all requests (except for search) will go into the 350 requests. If you want 500, then perform 150 unauthenticated and 350 authenticated. If you need even more, use more accounts to do the requests. Tom On 6/3/11 11:06 PM, Correa Denzil wrote: Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Giffordja...@jamesrgifford.com wrote: The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzilmcen...@gmail.com wrote: Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] How to obtain user demography using Twitter API in our apps?
I don't recall ever entering that info when signing up for Twitter. Without data you can't give that kind of information. Tom On 6/3/11 12:54 PM, GDPL wrote: Hi All We have used Twitter API as per the documentation in our mobile app. The API status shows the usage and other technical stats. But we could not come across user demography stats such as age group, gender, active users set, country/state etc. Is there anyway we can find these on the Twitter API/Developer portal? Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Does Twitter Photos require the use of tweet entities?
Not at all! Embed.ly also parses them! http://api.embed.ly/embed?url=http%3A%2F%2Ftwitter.com%2Ftwitter%2Fstatus%2F76360760606986241%2Fphoto%2F1 Tom On 6/3/11 11:02 PM, SM wrote: Are tweet entities required for parsing Twitter Photos? Many clients do their own parsing and can figure out when a link is an image based on the URL (twitpic, yfrog, etc). It looks like Twitter Photos will use t.co in which case it doesn't look possible to figure out whether the link is an image based on URL. Is this correct? Are tweet entities required for Twitter Photos? When will tweet entities no longer be an optional parameter for the REST API? Thanks. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
If you authenticate, all requests (except for search) will go into the 350 requests. If you want 500, then perform 150 unauthenticated and 350 authenticated. If you need even more, use more accounts to do the requests. Tom On 6/3/11 11:06 PM, Correa Denzil wrote: Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Giffordja...@jamesrgifford.com wrote: The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzilmcen...@gmail.com wrote: Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] tweet button zero count
Firefox 6.0a2, OS X 10.7. I see a count of 3... Tom On 6/2/11 1:30 PM, Scott Wilcox wrote: Firefox 4.0.1, OSX 10.6. No plugins. Works fine in Chrome and Safari too. On 2 Jun 2011, at 12:04, John Carver wrote: What version of browser do you use? Do you have any plugins installed? 2011/6/2 Scott Wilcox sc...@dor.ky mailto:sc...@dor.ky The URL count is working fine for me. On 2 Jun 2011, at 11:41, John Carver wrote: Hi Matt, Today have figured out zero count is firefox issue. IE, Opera, Chrome all work just fine. Take the look: http://icisweb.ru/tweet-button-test/ I'm using FF 3.6.17 Any suggestions? Thanks -- Scott Wilcox @dordotky | sc...@dor.ky mailto:sc...@dor.ky | http://dor.ky http://dor.ky/ +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Scott Wilcox @dordotky | sc...@dor.ky mailto:sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] New Photo upload feature: What's new coming on the API side
Arnaud / @rno, Will you (and the rest of the dev/platform team, of course) also make these available via services such as Embed.ly (OEmbed)? Currently my entire image implementation depends on parsing images from the tweet's text instead of the entities, and I'd like to keep it like that. :-) Tom On 6/2/11 9:12 PM, Arnaud Meunier wrote: Hey there, The first public tweet with a twitter.com http://twitter.com uploaded photo has just been published. We just updated our JSON example on the Tweet entities documentation page: https://dev.twitter.com/pages/tweet_entities#media We're excited to see you guys support rendering of these photos. Let us know how it goes! Arnaud / @rno http://twitter.com/rno On Thu, Jun 2, 2011 at 9:56 AM, Arnaud Meunier arn...@twitter.com mailto:arn...@twitter.com wrote: Hey Yusuke, No, media URLs will not appear in the URL array. Arnaud / @rno http://twitter.com/rno On Thu, Jun 2, 2011 at 8:51 AM, Yusuke Yamamoto yus...@mac.com mailto:yus...@mac.com wrote: Hi, The media-entities look very similar to url-entities. Are media entity URLs appear in urls object as well? Best, -- Yusuke Yamamoto yus...@mac.com mailto:yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ On Jun 2, 2011, at 03:34 , Arnaud Meunier wrote: Hey developers, We have just announced a couple of new exciting features at the All Things D conference, one of which is the ability to upload photos to twitter.com http://twitter.com/. Uploading photos to Twitter is currently available on the twitter.com http://twitter.com/ desktop version, and its access is initially limited to a very small number of users. In the next couple of weeks, as we progressively ramp up the number of users who have access to the feature, we'll provide you with more details about how you can use the Tweet-with-photo API. For now, the only change you'll notice on the API side is a new media entity in the status object. We encourage you to support rendering, and to help you with that, we just revamped the Tweet Entities documentation page, describing in detail how you can use this structured data: http://dev.twitter.com/pages/tweet_entities Note that we also updated our API Terms of Service [1] and our Display Guidelines [2] to include this new feature. As ever, if you have questions about the new media entity or our ToS changes, let us know on the list or through @twitterapi. [1] http://dev.twitter.com/pages/api_terms [2] http://dev.twitter.com/pages/display_guidelines Arnaud / @rno -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Rate limiting - per user or per application key?
Per user per application. A user can use, for example, 350 requests with TweetDeck, and then it can still use 350 requests with your application, without interfering with other users that also use your application. Tom On 5/31/11 2:37 PM, Rob Wilson wrote: Hi, I am writing an iPhone application that uses the Twitter API, using oAuth. Could you please clarify that the 350 requests per hour are tied to the logged in user and not the application key? If not, do I need to white-list to prevent this becoming a problem? Cheers, Rob. -- Please visit... SpikyOrange.co.uk http://spikyorange.co.uk/ A portal for anything I create, including... BitBanter.com http://bitbanter.com/ A technical podcast 50% Tech + 50% software development = 100% Entertaining! http://spikyorange.co.uk/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] problem in Posting a tweet using OAuth from IOS app
I assume that your URL encoding is wrong in the OAuth code. Make sure
that you use %20 for a space and not +. The standard NSString URLencode
function won't really work.
Code that has always worked for me to URLencode (got it from the web
somewhere, sorry for not mentioning the original author) :
+(NSString*)urlEncode:(NSString*)str {
return [(NSString *)CFURLCreateStringByAddingPercentEscapes(
NULL,
(CFStringRef)str,
NULL,
(CFStringRef)@!*'();:@=+$,/?%#[],
kCFStringEncodingUTF8 ) autorelease];
}
Tom
On 5/28/11 1:25 PM, Ayman Adel wrote:
I am building a twitter client for the IPhone and I'm using OAuth to
authenticate my requests to twitter,
Right now I am able to get the home time line and even post tweets
( that do not contain any spaces or symbols) the problem starts when I
try to post a tweet that contains spaces for example it gives me :
{error:Incorrect signature,request:\/1\/statuses\/update.json}
For example the tweet : ThisIsATweet works, but the tweet : this is
a tweet doesn't work here's my http request body code:
code
NSData* body =[NSString stringWithFormat:@status=%@,[self
percentageEncoding:tweet]];
[request setValue:@application/x-www-form-urlencoded
forHTTPHeaderField:@Content-Type];
[request setValue:[NSString stringWithFormat:@%d,[body length]]
forHTTPHeaderField:@Content-Length];
[request setHTTPBody:[body
dataUsingEncoding:NSISOLatin1StringEncoding]];
/code
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] list/statuses
You can't. The 20 is the number of tweets received from Twitter's database. It will then simply not send the ones which come from private users, deleted ones (?), retweets, etc. If you want 20, ask for 50 and limit it yourself. Tom On 5/29/11 11:20 AM, ogierepier wrote: Now I have a public list that includes private accounts. I'm retrieving the result by calling statuses.json. The list is followed by a few people. I have a gadget on my site which retrieves the latest statuses. The private tweets are left out, which is fine by me, but they're taking the place of the public tweets. Which means if for example the 20 latest tweets on the first page of the results contain 19 private tweets you get only one tweet back. I do not want to remove the private accounts from the list because the people following the list can see this private tweets on twitter.com. How can I exclude the private tweets from the query so that my results of the latest 20 tweets contain 20 public statuses? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Question about rate limiting
Per user per application. With 1000 users you can use 35 API calls per hour. Tom On 5/24/11 5:41 AM, Sam Oldak wrote: I am developing an app that allows users to login with twitter. I'm a bit confused about the rate limiting applied to verifying credentials of users. Is it 350/hour for the application, or per user that uses the application? For example, could 1000 people signin within an hour, or am I limited to 350 per hour? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Please confirm this OAuth flow ...
On 5/20/11 6:36 AM, Andrew W. Donoho wrote: Tom, Thank you for your answers. As I read other threads, I am finding ambiguity reemerging. Pardon my pedantry, I want to nail this down correctly the first time. As you know, I have a hard deadline to get these fixes implemented and deployed. It appears that there is a difference between /oauth/authorize and /oauth/authenticate. In a separate thread: On May 19, 2011, at 15:17 , themattharris wrote: You said you were restricting this permission to the OAuth /authorize web flow only. Will /oauth/authenticate (Sign in with Twitter) support the new permission? The R/W/DM permission can only be granted through the /oauth/authorize route. Sign in with Twitter cannot be used to grant R/W/DM. Could you confirm which route you want mobile devices to use? I don't work for Twitter - let's get that cleared up first. Mr. Harris does. However: since I assume that you will want R/W/DM permissions, you should use /oauth/authorize. Also, since a mobile device normally stores the tokens in a keychain or some other secure mechanism, the user will only have to go through the process once. Also, since only /oauth/authorize supports oauth_callback (may be wrong there) it's the recommended way for non-web applications. Furthermore, Mr. Harris claims the following: Be sure to include a path with your callback. For example: myapp://oauth_complete This is at variance with your advice below. Do you concur with Mr. Harris' view? Absolutely. Mr. Harris further states: Is using a web view against the Terms of Service (TOS)? Using an in-app web view to show the OAuth pages is not against our TOS. However, we encourage developers to use the built-in browser where appropriate. Forgive my being gun shy but Twitter has made it clear that client apps were to get special scrutiny. I want to know exactly what Mr. Harris means by appropriate. In my view, leaving my app for Safari is only appropriate when a user presses a button to go to Safari. Pressing a login button and then seeing my app swap out for Safari is a confusing and sub-standard user experience. Am I going to get banned because I deem it a better user experience to stay fully within my app? I just want to know what the rules are. Rules: it's apparently not against the TOS to use a WebView, but everyone I asked thinks it's best to use the normal webbrowser. The user then gets an additional layer of security, because an application cannot inject JavaScript in this browser, and the user will recognize that he's logging in on the actual twitter.com site by looking at the address bar. If possible, use the normal webbrowser. Again, thank you for your time and attention to these issues. Andrew On May 19, 2011, at 09:53 , Tom van der Woerdt wrote: 1. Yep 2. NO. There's no difference in oauth/authorize and oauth/authenticate, except that authenticate will simply pass the accept/deny screen if the user has already accepted the app. Also, don't display it in a WebView, use the normal browser instead and use a callback URL with a custom scheme - for example myapp://. Let the browser redirect this URL back to the app. Again, do NOT use a UIWebView - I'm pretty sure that that's against the TOS, and if it's not, it soon will be. 3. Yep 4. Yes, you will need to store the consumer token and secret in the code, and store the user's token and secret in the keychain (or somewhere else, secure). The OAuth flow is no different for mobile devices than for desktops. Tom On 5/19/11 4:45 PM, Andrew W. Donoho wrote: Gentle Twitter Support Folks, There is an ambiguity in the OAuth flow for mobile devices. As I now have little time to move from xAuth to OAuth, I would appreciate it if Twitter Support would confirm the following OAuth flow which uses your routes. 1) Use POST oauth/request_token to get the access token needed for the user web dialog. 2) Upon receiving the request token, open a web view using GET oauth/authorize. This is the ambiguous path for mobile devices. It is specified that this path must be used for desktop devices. As a mobile device is really a wireless desktop device, I believe Twitter wants me to use this route in lieu of GET oauth/authenticate. Other vendors also allow the specification of whether this is a mobile device. They then provide a web authorization dialog appropriate for a narrow screen. It does not appear that Twitter offers this functionality. Could you please confirm this? Finally, as my app runs on an iPad, what is the preferred web view width? (To support both portrait and landscape orientations, it needs to be less than 768 pixels. 600 pixels is a common, Apple suggested, width.) Could you please enlighten me to what is Twitter's preferred authorization web view width? 3) Use GET oauth/authenticate to acquire the access token and access secret. 4) As I haven't yet requested my new consumer key and, hence, do
Re: [twitter-dev] Twitter button code limiting cookies
You could simply use some CSS to create a Tweet Button-like button and link to https://twitter.com/share Example: https://twitter.com/share?url=http://test.com/ I'm pretty sure that the docs specify the arguments which you can pass to the Tweet Button. Tom On 5/20/11 8:30 PM, Tony House wrote: I am hoping to add the Twitter Button to several pages at the Census, but need to limit the cookies (Being a government agency we have laws regarding cookies on our sites in addition to concerns over Personally Identifiable Information). I have noticed that I have 14 cookies related to twitter. Is there code for the like button which turns off specific cookies - or at least makes the button work with just session information? Thanks Tony -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Auto Populating Tweets Broken?
Jonathan, It's only /home?status= that does not currently work, /?status= does still work. As a quick workaround you could simply use /?status=. Of course, I'd strongly recommend making the switch to web intents asap. Tom On 5/19/11 2:42 AM, Jonathan Strauss wrote: I'm totally with you guys on the value of switching to web intents, and we recommend all our customers doing new implementations use them. However, there are just too many legacy implementations against the old hack, as Taylor deemed it, for you to expect everyone to switch over in such a timeframe. For a very long time the /?status= method was the only way to tweet from a website and web intents are only a few months old, so I hope you guys don't diminish the priority of fixing this bug just because you want to force everyone to the new way of doing things. -jonathan On May 18, 7:50 am, Taylor Singletarytaylorsinglet...@twitter.com wrote: Hi Omar, Sorry for the confusion -- we recommend Web Intents as we've developed the Tweet Intent specifically for this purpose -- let us know what tweaks you think the display needs to look good in a full browser tab. Intents are optimized to load quickly and service the user's intent as efficiently as possible -- the old way requires a more significant load time and invites the user to engage in all kinds of other fun Twitter activity aside from tweeting -- maybe they'll even forget why you sent them there in the first place. This is a bug and while I don't have an ETA on when it will be fixed, it was not intentional and this old hack has not been deprecated. @episodhttp://twitter.com/episod - Taylor Singletary On Tue, May 17, 2011 at 5:34 PM, omegdadiomegd...@gmail.com wrote: Hey There, +1. This issue is affecting all of our products at the moment. I can't find any notification anywhere about this being deprecated today. Please restore this functionality. And allow us some time to migrate w/ a date in mind. If it's no longer going to be supported, we need to know sooner as we have clients waiting for an answer at the moment. We would like to use intents, but we need a full page to send the user to since we can't always open a popup window (ie from Flash.) and that page doesn't look good in a full browser tab. Thanks, Omar On May 17, 3:05 pm, Arnaud Meunierarn...@twitter.com wrote: Hey Yahel, Meet Web Intents:http://dev.twitter.com/pages/intents(takea look on the intent/tweet intent). It really is super easy to implement. For example:http://twitter.com/intent/tweet?text=foobar Arnaud / @rnohttp://twitter.com/rno On Tue, May 17, 2011 at 1:18 PM, Yahel Carmonyah...@gmail.com wrote: Hey, We've just noticed that auto-populating tweets using http://twitter.com/home/?status=foobarnolonger works. Has this feature been totally removed, or is this a temporary glitch? (Perversely,http://twitter.com/?status=foobarworks, but that was the older method that broke last year and we were told to add /home to fix it.) I know we're supposed to move to the official Tweet button, but we have a very large scale CRM that still relies on the old method. Please let me know ASAP, as we have a lot of broken tweet links in the wild. Thanks, Yahel -- Yahel Carmon (917) 445-3498 Twitter:http://twitter.com/yahelc Facebook:http://facebook.com/yahel LinkedIn:http://www.linkedin.com/in/yahelc -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Auto Populating Tweets Broken?
True, but I've seen some people saying that they want a normal Twitter page, not an intent. Like I said, I really recommend using intents instead, but the option is still there. Tom On 5/19/11 11:57 AM, Mohan Arun wrote: On May 19, 2:25 pm, Tom van der Woerdti...@tvdw.eu wrote: Jonathan, It's only /home?status= that does not currently work, /?status= does still work. As a quick workaround you could simply use /?status=. Of course, I'd strongly recommend making the switch to web intents asap. If you are making this change you might as well make the change to use web intents: Example: http://twitter.com/intent/tweet?status=My%20new%20super-awesome%20status Read more about this: http://dev.twitter.com/pages/intents By the way I just came across today, what looks to me like a bug given twitter's idealogical stress behind 'intent-based process flow'. I came across a twitter bio page which I wanted to follow and I wasnt logged in to twitter and I just clicked 'Follow' and it opened the login box as expected but after I did login it returned me to the same page. My original intent of clicking on the 'follow' button was incomplete and I had to click on 'Follow' again. =- Mohan -= http://www.mohanarun.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Please confirm this OAuth flow ...
Like I mentioned in my post - use the actual browser which includes an address bar (that's what it's about - without the address bar the user doesn't know it's actually twitter.com and you might just as well use xAuth, lol). Use a callback URL which includes a custom scheme (myapp://oauth_redirect, for example) and catch this URL in your code. Tom On 5/19/11 4:58 PM, Adriaan Pelzer wrote: If using a UIWebView is against the TOS, how should app developers (standalone apps, that is) authenticate without xauth, in the light of yesterday's announcements? Adriaan Pelzer //))//\\//\\||// //\\//7//7///\\ putting you in touch with your crowds http://www.wewillraakyou.com twitter: http://www.twitter.com/adriaan_pelzer linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ skype: adriaan_pelzer +4478 7978 1743 On Thu, May 19, 2011 at 3:53 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: 1. Yep 2. NO. There's no difference in oauth/authorize and oauth/authenticate, except that authenticate will simply pass the accept/deny screen if the user has already accepted the app. Also, don't display it in a WebView, use the normal browser instead and use a callback URL with a custom scheme - for example myapp://. Let the browser redirect this URL back to the app. Again, do NOT use a UIWebView - I'm pretty sure that that's against the TOS, and if it's not, it soon will be. 3. Yep 4. Yes, you will need to store the consumer token and secret in the code, and store the user's token and secret in the keychain (or somewhere else, secure). The OAuth flow is no different for mobile devices than for desktops. Tom On 5/19/11 4:45 PM, Andrew W. Donoho wrote: Gentle Twitter Support Folks, There is an ambiguity in the OAuth flow for mobile devices. As I now have little time to move from xAuth to OAuth, I would appreciate it if Twitter Support would confirm the following OAuth flow which uses your routes. 1) Use POST oauth/request_token to get the access token needed for the user web dialog. 2) Upon receiving the request token, open a web view using GET oauth/authorize. This is the ambiguous path for mobile devices. It is specified that this path must be used for desktop devices. As a mobile device is really a wireless desktop device, I believe Twitter wants me to use this route in lieu of GET oauth/authenticate. Other vendors also allow the specification of whether this is a mobile device. They then provide a web authorization dialog appropriate for a narrow screen. It does not appear that Twitter offers this functionality. Could you please confirm this? Finally, as my app runs on an iPad, what is the preferred web view width? (To support both portrait and landscape orientations, it needs to be less than 768 pixels. 600 pixels is a common, Apple suggested, width.) Could you please enlighten me to what is Twitter's preferred authorization web view width? 3) Use GET oauth/authenticate to acquire the access token and access secret. 4) As I haven't yet requested my new consumer key and, hence, do not know some things, will I also be maintaining a consumer secret for my OAuth signature mechanism? Thank you for your support. Anon, Andrew P.S. Thank you for the two week extension for our xAuth to OAuth transition. Because Apple may still reject my app for unrelated to Twitter issues, four weeks is still a totally inadequate period to ensure a zero downtime transition. Please recognize both the risks to our business and the hardship you are imposing on small organizations. Furthermore, Apple's WWDC conference occurs in the middle of your current conversion schedule, this only allows me, in effect, 3 weeks to make this change. You can really hurt us with your imposed schedule. While I doubt that is your intent, it is, nonetheless, a likely outcome. Please double, at least, your conversion period to 8 weeks. Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com mailto:a...@ddg.com, +1 (512) 750-7596, twitter.com/adonoho http://twitter.com/adonoho When you can't imagine how things are going to change, that doesn't mean that nothing will change. It means that things will change in ways that are unimaginable. Bruce Sterling, January 02, 2009 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk
Re: [twitter-dev] Please confirm this OAuth flow ...
http://dev.twitter.com/pages/api_terms - II. Principles - 1. Don't surprise users - C. Your application should not: - replicate, frame, or mirror the Twitter website or its design. Tom On 5/19/11 5:10 PM, hax0rsteve wrote: Tom, Could you clarify : If using a web view is against the ToS, could you state which section ? And if it soon will be (which conflicts with the above), what makes you think so ? Did I miss something ? Also, if someone from the Twitter team could confirm either of these, this would be much more helpful. On 19 May 2011, at 16:00, Tom van der Woerdt wrote: Like I mentioned in my post - use the actual browser which includes an address bar (that's what it's about - without the address bar the user doesn't know it's actually twitter.com http://twitter.com and you might just as well use xAuth, lol). Use a callback URL which includes a custom scheme (myapp://oauth_redirect, for example) and catch this URL in your code. Tom On 5/19/11 4:58 PM, Adriaan Pelzer wrote: If using a UIWebView is against the TOS, how should app developers (standalone apps, that is) authenticate without xauth, in the light of yesterday's announcements? Adriaan Pelzer //))//\\//\\||// //\\//7//7///\\ putting you in touch with your crowds http://www.wewillraakyou.com http://www.wewillraakyou.com/ twitter: http://www.twitter.com/adriaan_pelzer linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ skype: adriaan_pelzer +4478 7978 1743 On Thu, May 19, 2011 at 3:53 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: 1. Yep 2. NO. There's no difference in oauth/authorize and oauth/authenticate, except that authenticate will simply pass the accept/deny screen if the user has already accepted the app. Also, don't display it in a WebView, use the normal browser instead and use a callback URL with a custom scheme - for example myapp://. Let the browser redirect this URL back to the app. Again, do NOT use a UIWebView - I'm pretty sure that that's against the TOS, and if it's not, it soon will be. 3. Yep 4. Yes, you will need to store the consumer token and secret in the code, and store the user's token and secret in the keychain (or somewhere else, secure). The OAuth flow is no different for mobile devices than for desktops. Tom On 5/19/11 4:45 PM, Andrew W. Donoho wrote: Gentle Twitter Support Folks, There is an ambiguity in the OAuth flow for mobile devices. As I now have little time to move from xAuth to OAuth, I would appreciate it if Twitter Support would confirm the following OAuth flow which uses your routes. 1) Use POST oauth/request_token to get the access token needed for the user web dialog. 2) Upon receiving the request token, open a web view using GET oauth/authorize. This is the ambiguous path for mobile devices. It is specified that this path must be used for desktop devices. As a mobile device is really a wireless desktop device, I believe Twitter wants me to use this route in lieu of GET oauth/authenticate. Other vendors also allow the specification of whether this is a mobile device. They then provide a web authorization dialog appropriate for a narrow screen. It does not appear that Twitter offers this functionality. Could you please confirm this? Finally, as my app runs on an iPad, what is the preferred web view width? (To support both portrait and landscape orientations, it needs to be less than 768 pixels. 600 pixels is a common, Apple suggested, width.) Could you please enlighten me to what is Twitter's preferred authorization web view width? 3) Use GET oauth/authenticate to acquire the access token and access secret. 4) As I haven't yet requested my new consumer key and, hence, do not know some things, will I also be maintaining a consumer secret for my OAuth signature mechanism? Thank you for your support. Anon, Andrew P.S. Thank you for the two week extension for our xAuth to OAuth transition. Because Apple may still reject my app for unrelated to Twitter issues, four weeks is still a totally inadequate period to ensure a zero downtime transition. Please recognize both the risks to our business and the hardship you are imposing on small organizations. Furthermore, Apple's WWDC conference occurs in the middle of your current conversion schedule, this only allows me, in effect, 3 weeks to make this change. You can really hurt us with your imposed schedule. While I doubt that is your intent, it is, nonetheless, a likely outcome. Please double, at least, your conversion period to 8 weeks. Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com mailto:a...@ddg.com, +1 (512) 750-7596, twitter.com/adonoho http://twitter.com/adonoho When you
Re: [twitter-dev] Please confirm this OAuth flow ...
Can you name a modern device on which people will want a client with access to direct messages, without a webbrowser? I can't. Tom On 5/19/11 5:17 PM, Adriaan Pelzer wrote: Understood. In other words, there is no way to consume the authenticated parts of the Twitter API on devices without web browsers anymore? This severe limitation will haunt Twitter in future, without a doubt. Adriaan Pelzer //))//\\//\\||// //\\//7//7///\\ putting you in touch with your crowds http://www.wewillraakyou.com twitter: http://www.twitter.com/adriaan_pelzer linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ skype: adriaan_pelzer +4478 7978 1743 On Thu, May 19, 2011 at 4:00 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Like I mentioned in my post - use the actual browser which includes an address bar (that's what it's about - without the address bar the user doesn't know it's actually twitter.com http://twitter.com and you might just as well use xAuth, lol). Use a callback URL which includes a custom scheme (myapp://oauth_redirect, for example) and catch this URL in your code. Tom On 5/19/11 4:58 PM, Adriaan Pelzer wrote: If using a UIWebView is against the TOS, how should app developers (standalone apps, that is) authenticate without xauth, in the light of yesterday's announcements? Adriaan Pelzer //))//\\//\\||// //\\//7//7///\\ putting you in touch with your crowds http://www.wewillraakyou.com twitter: http://www.twitter.com/adriaan_pelzer linkedIn: http://uk.linkedin.com/pub/adriaan-pelzer/4/874/860/ skype: adriaan_pelzer +4478 7978 1743 On Thu, May 19, 2011 at 3:53 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: 1. Yep 2. NO. There's no difference in oauth/authorize and oauth/authenticate, except that authenticate will simply pass the accept/deny screen if the user has already accepted the app. Also, don't display it in a WebView, use the normal browser instead and use a callback URL with a custom scheme - for example myapp://. Let the browser redirect this URL back to the app. Again, do NOT use a UIWebView - I'm pretty sure that that's against the TOS, and if it's not, it soon will be. 3. Yep 4. Yes, you will need to store the consumer token and secret in the code, and store the user's token and secret in the keychain (or somewhere else, secure). The OAuth flow is no different for mobile devices than for desktops. Tom On 5/19/11 4:45 PM, Andrew W. Donoho wrote: Gentle Twitter Support Folks, There is an ambiguity in the OAuth flow for mobile devices. As I now have little time to move from xAuth to OAuth, I would appreciate it if Twitter Support would confirm the following OAuth flow which uses your routes. 1) Use POST oauth/request_token to get the access token needed for the user web dialog. 2) Upon receiving the request token, open a web view using GET oauth/authorize. This is the ambiguous path for mobile devices. It is specified that this path must be used for desktop devices. As a mobile device is really a wireless desktop device, I believe Twitter wants me to use this route in lieu of GET oauth/authenticate. Other vendors also allow the specification of whether this is a mobile device. They then provide a web authorization dialog appropriate for a narrow screen. It does not appear that Twitter offers this functionality. Could you please confirm this? Finally, as my app runs on an iPad, what is the preferred web view width? (To support both portrait and landscape orientations, it needs to be less than 768 pixels. 600 pixels is a common, Apple suggested, width.) Could you please enlighten me to what is Twitter's preferred authorization web view width? 3) Use GET oauth/authenticate to acquire the access token and access secret. 4) As I haven't yet requested my new consumer key and, hence, do not know some things, will I also be maintaining a consumer secret for my OAuth signature mechanism? Thank you for your support. Anon, Andrew P.S. Thank you for the two week extension for our xAuth to OAuth transition. Because Apple may still reject my app for unrelated to Twitter issues, four weeks is still a totally inadequate period to ensure a zero downtime transition. Please recognize both the risks to our business and the hardship you are imposing on small organizations. Furthermore, Apple's WWDC conference occurs in the middle of your current conversion schedule, this only allows me, in effect, 3 weeks
Re: [twitter-dev] A new permission level
Sounds good! Also sounds like you folks are finally trying to get rid of
xAuth :-)
Of course, for desktop (and mobile) applications this will mean that
they will have to integrate the normal OAuth flow. Yay!.
In the past, I've seen several occurrences where popular clients weren't
affected by the rules. Will we yet again see this, or will there not be
an exception for those clients? The same question goes for Twitter's own
apps: will they make the switch to OAuth, or will they keep using xAuth?
Tom
On 5/18/11 7:01 PM, Matt Harris wrote:
Hey everyone,
We recently updated our OAuth screens to give users greater
transparency about the level of access applications have to their
accounts. The valuable feedback Twitter users and developers have
given us played a large part in that redesign and helped us identify
where we can do more.
In particular, users and developers have requested greater granularity
for permission levels.
In response to this feedback, we have created a new permission level
for applications called “Read, Write Direct Messages”. This
permission will allow an application to read or delete a user's direct
messages. When we enforce this permission, applications without a
“Read, Write Direct Messages” token will be unable to read or delete
direct messages. To ensure users know that an application is receiving
access to their direct messages, we are also restricting this
permission to the OAuth /authorize web flow only. This means
applications which use xAuth and want to access direct messages must
send a user through the full OAuth flow.
What does this mean for your application?
If you do not need access to direct messages: you won’t need to make
any changes to your application. When we enforce the new permission
level your read or read/write token will automatically lose access to
direct messages.
If you do need access to direct messages: you will need to edit your
application record on https://dev.twitter.com/apps and change the
permission level of your application to “Read, Write and Direct
Messages”. The new permission will not affect existing tokens which
means existing users or your app or service will need to reauthorize.
We know this will take some time so we are allowing a transition
period until the end of this month. During this time there will be no
change to the access Read/Write tokens have to a users account.
However, at the end of the month any tokens which have not been
upgrade to “Read, Write and Direct Messages” will be unable to access
and delete direct messages.
Affected APIs and requests
On the REST API, Read and Read/Write applications will no longer be
able to use these API methods:
/1/direct_messages.{format}
/1/direct_messages/sent.{format}
/1/direct_messages/show.{format}
/1/direct_messages/destroy.{format}
For the Streaming API, both User Streams and Site Streams will only
receive direct messages if the user has authorised an application to
access direct messages.
Applications that use “Sign-in with Twitter” or xAuth will only be
able to receive Read or Read/Write tokens.
What this means is only applications which direct a user through the
OAuth web flow will be able to receive access tokens that allow access
to direct messages. Any other method of authorization, including
xAuth, will only be able to receive Read/Write tokens.
What will happen when the permission is activated
When we activate the new permission, all Read and Read/Write
user_tokens issued to third-party applications will lose their ability
to read direct messages. Any attempt to read direct messages will
result in an HTTP 403 error being returned.
For example, a GET request to
https://api.twitter.com/1/direct_messages/sent.json will return an
HTTP 403 Forbidden with the response body:
{errors:[{code:93,message:This application is not allowed to
access or delete your direct messages}]}
Key Points
* If you wish to access a user’s direct messages you will need to
update your application and reauthorize existing tokens.
* The only way to get direct message access is to request access
through the OAuth /authorize web flow. You will not be permitted to
access direct messages if you use xAuth.
* When we enforce the permission Read/Write and Read tokens will be
unable to access and delete direct messages.
* Read/Write tokens will be able to send direct messages after the
permission is enforced.
We’ll be collating responses and adding more information on our
developer resources permission model page:
https://dev.twitter.com/pages/application-permission-model
We have also blogged about this on the Twitter blog:
http://blog.twitter.com/2011/05/mission-permission.html
Best,
@themattharris
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your
Re: [twitter-dev] Launching Twitter for iOS using twitter:// url schemes
If I'm not mistaken, Twitter for iOS still responds to the old
tweetie:// URL schemes.
http://wiki.akosma.com/IPhone_URL_Schemes#Tweetie (found them on google)
Also, the Mac version of Twitter for iOS supports twitter:// as well - I
think I've seen URLs that opened profile but I don't remember where I
saw that.
twitter:///post?message=test definitely works on the Mac version, so
I'll assume that it works on the iOS version as well.
Tom
On 5/15/11 2:16 PM, Daniel wrote:
Hi, I can't find any documentation, or even a place to ask this
question, so sorry if this is off-topic...
I'm an iOS developer, and I'd like to attempt to open the Twitter app
on the device, (from my app) at a particular profile, or even in a
state to @mention a particular username. Currently I can do this...
BOOL didOpenOtherApp = NO;
if ([device respondsToSelector:@selector(isMultitaskingSupported)]
[device isMultitaskingSupported]) {
NSString *urlString = [NSString stringWithFormat:@twitter://
%@, USER_NAME];
didOpenOtherApp = [NSApp openURL:[NSURL
URLWithString:urlString];
}
if (!didOpenOtherApp) {
NSString *urlString = [NSString stringWithFormat:@https://
twitter.com/%@, USER_NAME];
didOpenOtherApp = [NSApp openURL:[NSURL
URLWithString:urlString];
}
And, if the user has Twitter for iPhone installed, then it'll open,
but it won't go to that profile or anything, so, it responds to twitter://
but not anything in the actual URL, that I can make out.
So, essentially, I'm just wondering if there is any documentation on
the format of the URL strings that are meaningful to Twitter on iOS
devices, and if it's even possible to do what I'm trying here? I'd
love to be able to launch the app and put it into a state ready for
posting a new tweet, maybe something like: twitter://tweet@USER_NAME
Thanks
Dan
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Launching Twitter for iOS using twitter:// url schemes
I just found that twitter:///user?screen_name=tvdw works as well.
Tom
On 5/15/11 6:51 PM, Tom van der Woerdt wrote:
If I'm not mistaken, Twitter for iOS still responds to the old
tweetie:// URL schemes.
http://wiki.akosma.com/IPhone_URL_Schemes#Tweetie (found them on google)
Also, the Mac version of Twitter for iOS supports twitter:// as well -
I think I've seen URLs that opened profile but I don't remember where
I saw that.
twitter:///post?message=test definitely works on the Mac version, so
I'll assume that it works on the iOS version as well.
Tom
On 5/15/11 2:16 PM, Daniel wrote:
Hi, I can't find any documentation, or even a place to ask this
question, so sorry if this is off-topic...
I'm an iOS developer, and I'd like to attempt to open the Twitter app
on the device, (from my app) at a particular profile, or even in a
state to @mention a particular username. Currently I can do this...
BOOL didOpenOtherApp = NO;
if ([device respondsToSelector:@selector(isMultitaskingSupported)]
[device isMultitaskingSupported]) {
NSString *urlString = [NSString stringWithFormat:@twitter://
%@, USER_NAME];
didOpenOtherApp = [NSApp openURL:[NSURL
URLWithString:urlString];
}
if (!didOpenOtherApp) {
NSString *urlString = [NSString stringWithFormat:@https://
twitter.com/%@, USER_NAME];
didOpenOtherApp = [NSApp openURL:[NSURL
URLWithString:urlString];
}
And, if the user has Twitter for iPhone installed, then it'll open,
but it won't go to that profile or anything, so, it responds to
twitter://
but not anything in the actual URL, that I can make out.
So, essentially, I'm just wondering if there is any documentation on
the format of the URL strings that are meaningful to Twitter on iOS
devices, and if it's even possible to do what I'm trying here? I'd
love to be able to launch the app and put it into a state ready for
posting a new tweet, maybe something like: twitter://tweet@USER_NAME
Thanks
Dan
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] access token expires ?
Tokens don't expire. You should check the timezone settings - while it shouldn't matter, because a UNIX timestamp is always in UTC, it could be the issue. Tom On 5/4/11 3:26 AM, Joshua Nguyen wrote: I have obtained the access token; then i check for new @mentions twice a minute. In ~9 hours, Twitter returns an error : Timestamps out of bounds. I see this error is relating to the time difference between Twitter and my system; but i changed nothing in my system time. Does access token expire ? How can I solve this problem ? Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: New oAuth Authenticate Page
I don't know whether it's the only working solution, but it is the only proper OAuth procedure and as far as I'm aware, also the recommended one. Tom On 5/3/11 4:50 AM, Bess wrote: I'd like to confirm the all the developers here on this mailing list. Does the new OAuth redesign page prevent you from using OAuth in a new popup window? This OAuth hack is officially not going to work going forward? Hi Tom van der Woerdt, Your recommend using the workaround launching OAuth in a safari browser outside the app? Your suggested approach will require user to quit and exit app and authenticate with OAuth using device mobile browser. Then ask user to go back to the app again. Is this the only working solution? On Apr 30, 9:09 am, Tom van der Woerdti...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:55 AM, Bob12345 wrote: I'm having this problem too. My login browser inside the phone app is now rendered useless, it doesn't even scroll. On Apr 28, 1:41 pm, Shannon Whitleyshannon.whit...@gmail.comwrote: I was surprised to see a newly formatted oAuth Authenticate Page. The new page doesn't account for the scores of oAuth implementations that popup a new window. There is an ad-hoc standard for the window height and width that makes for a decent user experience. The new format will cause issues for the user since it results in page scrolling. Can we discuss this new page format and determine if it can be changed or if we can have alternate formats? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control
I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: New oAuth Authenticate Page
I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:55 AM, Bob12345 wrote: I'm having this problem too. My login browser inside the phone app is now rendered useless, it doesn't even scroll. On Apr 28, 1:41 pm, Shannon Whitleyshannon.whit...@gmail.com wrote: I was surprised to see a newly formatted oAuth Authenticate Page. The new page doesn't account for the scores of oAuth implementations that popup a new window. There is an ad-hoc standard for the window height and width that makes for a decent user experience. The new format will cause issues for the user since it results in page scrolling. Can we discuss this new page format and determine if it can be changed or if we can have alternate formats? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
Yes. But I don't like xAuth :-) (Not that that should be relevant for you) Anyway, the Microsoft.Phone.Tasks.WebBrowserTask is exactly what I meant. Can you get WM7 to recognize a yourapp:// URL (custom scheme)? You could have the OAuth login flow redirect back to that page with the oauth code (not talking about oob authorization, but the normal flow) and get the token that way. For the user, this would probably be the best way. Tom On 4/30/11 10:33 PM, Bob12345 wrote: Thanks for your response Tom, but I am not sure whether this could be done on a Windows Phone 7. The only way to open a regular browser window from a Silverlight app on the phone(that I know of) is to use Microsoft.Phone.Tasks.WebBrowserTask and that just opens a webpage. Would it be possible to bypass this new screen altogether if I were to use xAuth? Thanks! -Bob On Apr 30, 9:09 am, Tom van der Woerdti...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control
In an embedded view, the developer can access the content of the website without the user knowing it (read passwords, usernames, etc). On most OSes (definitely iOS, WM7 and Android) this is not possible in the non-embedded (webbrowser) view. Tom On 5/1/11 1:02 AM, Dean Collins wrote: Why is it safer Tom? Safer for who? Cheers, Dean *From:*twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] *On Behalf Of *Tom van der Woerdt *Sent:* Saturday, April 30, 2011 12:09 PM *To:* twitter-development-talk@googlegroups.com *Subject:* Re: [twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On 5/1/11 12:47 AM, Matthieu GD wrote:
On Apr 30, 12:09 pm, Tom van der Woerdti...@tvdw.eu wrote:
I've heard this before.
It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.
They are not blocked, it's *only* a problem of layout.
Are you sure? A block of CSS saying html { display: none; } doesn't
look like a problem, more like a feature.
The workaround I recommend: launch the actual browser, using a
yourapp:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.
I have the same problem, and I don't see why using a webcontrol is a
security problem. Since xauth is the exception, why twitter is making
the use of oauth so hard ?
You should read the article at http://goo.gl/xI0PZ
Tom
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Having Problem in the first step to use Twitter API with OAUTH for JAVASCRIPT
Well, it's definitely possible with JavaScript and even as a Web
Application, but only in one of these cases :
* User marks the web application as trusted, to avoid cross-domain
restrictions
* Twitter implements Mozilla's cross-domain XHR method
* From a file:// location or another location that has full scripting
access
The most common way of doing this is sending all requests via a
server-side proxy.
Also, I *must* point out that your current approach, with OAuth keys
plaintext in the code, is in violation of the Twitter API TOS. You have
to make it harder for people to find those keys.
Tom
On 4/28/11 6:25 PM, Victor wrote:
Hi There!.
I am having problems using the OAUTH authentication from an web based
application developed in javascript.
Basically i can do the first step requesting a Request Token using
submit a form. But i cannot make it work with an ajax request.
I guess that this step the application must do it in background
hidden from the final user.
The final user hasn't to press a button to submit a form to get the
request token he probably doesn't even want to know what it's
means... so,i insist, that there must be a way using ajax. to get a
request token
So, i tried and tried... looking across the web and the universe...
and after a lot of work, finally i was able to get to be able to send
a HTTP header for request token, and twitter answer me with a 200 HTML
code (i see that using firebug, the net panel) , but there is NO text
in the response!!
I will copy paste the code that make things work with forms and
apparently with XHR but it doesn't return anything.
JUST PASTE IT IN A FILE, PUT A REAL CONSUMER KEY AND SECRET AND VIOLA
THE RESULTS.
Thanks for advance to all the readers!!
Hope anyone can help me!.
Víctor.
!DOCTYPE html
html
head
titleOAuth Sandbox/title
script type=text/javascript src=sha1.js/script
script type=text/javascript src=oauth.js/script
/head
body
script
var myConsumerKey ='A'; // HERE IT WAS A REAL KEY
var myConsumerSecret ='B'; // HERE WAS A REAL SECRET
requestToken();
function requestToken (form)
{
var accessor = {
consumerSecret: myConsumerSecret,
tokenSecret: ''
};
var message = {
method: POST,
action:
https://api.twitter.com/oauth/request_token;,
parameters: {
oauth_signature_method: HMAC-SHA1,
oauth_consumer_key: myConsumerKey,
oauth_callback: oob
}
};
OAuth.setTimestampAndNonce(message);
OAuth.SignatureMethod.sign(message, accessor);
// FILL THE FORM INPUTS WITH THE NECESARY PARAMETERS
var parameterMap =
OAuth.getParameterMap(message.parameters);
for (var p in parameterMap) {
if (p.substring(0, 6) == oauth_ form[p] !=
null
form[p].name != null form[p].name != )
{
form[p].value = parameterMap[p];
}
}
return true;
}
function requestTokenXHR ()
{
var accessor = {
consumerKey: myConsumerKey,
consumerSecret: myConsumerSecret,
tokenSecret: ''
};
var message = {
method: POST,
action:
https://api.twitter.com/oauth/request_token;,
parameters: {
oauth_signature_method: HMAC-SHA1,
oauth_consumer_key: myConsumerKey,
oauth_callback: oob
}
};
OAuth.setTimestampAndNonce(message);
OAuth.completeRequest(message, accessor);
OAuth.SignatureMethod.sign(message, accessor);
var a =
OAuth.SignatureMethod.normalizeParameters(message.parameters);
var encodedParameters = OAuth.formEncode
(message.parameters);
var authorizationHeader =
OAuth.getAuthorizationHeader(,message.parameters);
var http = new XMLHttpRequest();
http.open(POST, message.action
Re: [twitter-dev] Tweet Button vs ?Status=
http://twitter.com/intent/tweet?status=whatever Tom On 4/10/11 11:21 PM, DustyReagan wrote: I'm torn between using the Tweet Button and simply linking to http://twitter.com/home?status=whatever ? It seems like the Tweet Button has a ton more overhead and complexity than a simple link with a querystring. I guess you get to show off your retweet count and solicite a follow with Tweet Button though. What say you? Do you prefer one to the other? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Tweet Button vs ?Status=
Afaik Twitter is trying to get people to stop using /home?status=. You should use either /share or /intent. However: /share simply redirects to /intent. I'd definitely go with /intent/tweet because it allows more customization than /share. I definitely wouldn't use /home?status=. Tom On 4/11/11 12:09 AM, DustyReagan wrote: Yup. That's another way. Is that your preferred way? And if so why? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] X-Ratelimit-Reset, Retry-After, and what the actual values mean
I've been looking at the ratelimiting response headers and have found some documentation, but nothing that provides me with sample values and what they mean. I'm developing an application in ColdFusion and using scribe (in java) for the OAuth library. I'm getting the headers back fine (at least X-RateLimit-Reset, I haven't hit the ratelimit for Search to see what it looks like yet) and I can read them in. That isn't the problem. What I'm having difficulty with is what the number that actually comes back. It appears to be a specific time in Seconds since 1/1/1970, but when I do the calculations, regardless of if i've hit the rate-limit I always get a time back that is 1 hour in the future. I feel like I'm just making a stupid mistake and overlooking something, but any help that you can provide would be much appreciated. Thanks, Tom McConlogue -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Introducing Web Intents
I wonder... Why is the script tag included in the example when the 3 lines below it don't actually use javascript? Does the widgets.js code automatically transform the buttons? That would be a bad thing... Besides that, I like it. I haven't checked yet, but is there a mobile version ready as well? Tom On 3/30/11 11:04 PM, Brian Ellin wrote: Developers, users, and journalists are finding more creative ways to use Tweets on the web to leverage the power of the network to spread news. In the past it’s been difficult to make these Tweets interactive, requiring you to write an OAuth app simply to attach Reply, Retweet, and Favorite actions to Tweets. Today we’re releasing a simple new addition to the API called Web Intents that makes it possible to make Tweets that you display on the web interactive. Web Intents provide popup optimized flows for all the ways you interact with Tweets and users on Twitter: Tweet, Reply, Retweet, Favorite, and Follow. The new tool makes it possible for users to interact with Twitter content in the context of your site, without leaving the page or having to authorize a new app just for the interaction. Web intents are mobile friendly and easy to implement. For example, here’s how you add Reply, Retweet, and Favorite links to a specific Tweet: script type=text/javascript src=http://platform.twitter.com/widgets.js;/script pa href=http://twitter.com/intent/tweet?in_reply_to=51113028241989632;Reply/a/p pa href=http://twitter.com/intent/retweet?tweet_id=51113028241989632;Retweet/a/p pa href=http://twitter.com/intent/favorite?tweet_id=51113028241989632;Favorite/a/p Detailed documentation is available at http://dev.twitter.com/pages/intents To see Web Intents in action check out Wordpress.com’s great tool for quoting Tweets in blog posts: Twitter Blackbird Pie http://en.support.wordpress.com/twitter-blackbird-pie/. Here's a post that uses their tool to quote @jack's Tweets about our 5 year anniversary http://techcrunch.com/2011/03/13/twitters-beginning/. We’ve also added these standard Tweet actions to our timeline widgets https://twitter.com/about/resources/widgets that are used all over the web. We’ve also updated the display guidelines http://dev.twitter.com/pages/display_guidelines with some suggestions on how to make your Tweets actionable, and made the standard Reply, Retweet and Favorite icons available for download https://dev.twitter.com/pages/image-resources. Cheers, Brian Ellin Product Manager, Platform http://twitter.com/brianellin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Twitter followers in excel
I've seen someone do it with VB scripting. Ask him, you can find him as Randomness on this list and on Twitter as @nl_twop_1000 Tom On 3/25/11 7:39 PM, M. Edward (Ed) Borasky wrote: On Fri, 25 Mar 2011 14:10:36 +, Scott Wilcox sc...@dor.ky wrote: Hello there, There is no method to do this straight from the API. What 'details' of each follower are you interested in having? Can you elaborate on why you're interested in having an export to excel if possible too. Scott. On 25 Mar 2011, at 12:25, shaily wrote: Hi Tweeples, Can you please help me how to download the details of my followers, their details, picture into excel! Can I connect excel directly to twitter? Is their an easy way? Please advise. Shaily There's a service called Export.ly that will do this for you. I don't remember how many of the fields it exports, though. This is an easy coding task in any of the scripting languages with Twitter API libraries - I do it in Perl but I'm sure it can be done in Python, Ruby or PHP as well with just a few lines of code. Finally, there are some ways in Excel to import XML data - anything you can export from Twitter via Atom / RSS feeds in XML can be imported into Excel that way. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: OAuth without read or write access
Thanks for the confirmation. I guess I'll have to rely on informing the user as you suggest. It looks like a gap in the API to me, there must be plenty of websites out there that might want to confirm a user's identity with their twitter account, without wanting access to their tweets. Tom. On 21 March 2011 10:38, Ninjamonk dar...@stuartmedia.co.uk wrote: yes it would, I think people are more worried about the ability to write than read. You could just put up a message saying this is only being used for sign in and we will not read your stream. On Mar 20, 9:06 pm, Tom Gibara m...@tomgibara.com wrote: Searching for sign in with twitter pointed me to: http://dev.twitter.com/pages/sign_in_with_twitter which I've already read. My understanding is that my application must be registered to use OAuth, and that the access type it requires (read/write) is determined by that registration. Doesn't this mean that, at a minimum, the user will be informed that my application may read their tweets and account details? This won't be the case, and I don't want to give users that impression. Tom. On 20 March 2011 17:05, Ninjamonk dar...@stuartmedia.co.uk wrote: search for sign in with twitter and you should be ok. All you need to do is let them login with oauth and you will get those details. On Mar 20, 3:29 pm, tomgibara m...@tomgibara.com wrote: I'm developing an application in which I want to allow users to authenticate themselves with their twitter account. I need nothing more back from the authentication API than an ID that identifies the user; I don't want any access to any other account details or their tweets etc. In other words, I don't want read access. Is this possible? It seems not, because the application registration page offers only read or read/write. If this is the case, are there any plans to support an authenticate only option for applications? I did search this group for related threads but only found this post, which had no replies: http://groups.google.com/group/twitter-development-talk/browse_thread... -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: OAuth without read or write access
Searching for sign in with twitter pointed me to: http://dev.twitter.com/pages/sign_in_with_twitter which I've already read. My understanding is that my application must be registered to use OAuth, and that the access type it requires (read/write) is determined by that registration. Doesn't this mean that, at a minimum, the user will be informed that my application may read their tweets and account details? This won't be the case, and I don't want to give users that impression. Tom. On 20 March 2011 17:05, Ninjamonk dar...@stuartmedia.co.uk wrote: search for sign in with twitter and you should be ok. All you need to do is let them login with oauth and you will get those details. On Mar 20, 3:29 pm, tomgibara m...@tomgibara.com wrote: I'm developing an application in which I want to allow users to authenticate themselves with their twitter account. I need nothing more back from the authentication API than an ID that identifies the user; I don't want any access to any other account details or their tweets etc. In other words, I don't want read access. Is this possible? It seems not, because the application registration page offers only read or read/write. If this is the case, are there any plans to support an authenticate only option for applications? I did search this group for related threads but only found this post, which had no replies: http://groups.google.com/group/twitter-development-talk/browse_thread... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Retweet chain
No, it's not. You can, however, analyze who gets the retweet in the timeline and build the chain that way. Of course, this won't work if you have a huge amount of retweets. Also, it's not 100% accurate. Tom On 3/17/11 6:47 PM, Karthik Murugan wrote: Let us assume: C follows B. B follows A A sends a tweet and B retweets it. C gets the retweet on his timeline and retweets it again. I'm connected to UserStream of A and I receive both the retweets. But not sure how to find the retweet chain How can we know that C retweeted it via B? Is it exposed in any API methods? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Please hire a developer relations manager
Isn't what you are describing the task of a developer advocate, Taylor Singletary and Matt Harris (and others?)? Tom On 3/14/11 2:44 PM, Adam Green wrote: First of all, I honestly believe that Twitter HQ values developers and appreciates their contribution. That is why I decided to devote myself to this area a couple of years ago. I was amazed that when a dev reported a problem the engineer responsible replied here and tried to solve it. That is better than any big product I know of today. That is why you have so many developers putting in all this work. I also believe that the last few announcements from Ryan and others have been the worst examples of third party developer management I have seen in 30 years in this business. I can see what Ryan wanted to accomplish in his latest message. He wanted to provide guidance. He ended up telling us that Twitter no longer wanted anyone to build clients, didn't explain clearly what a client meant to him, and pointed out that hundreds of apps that fail to meet his undefined high bar were cut off every week. Not good. Sorry, Ryan. You are right. You are not good at communicating with third party developers. At least not in written form. You look like a very cool guy with a lot of personal charm. Maybe it works better in person. You should spend some time talking directly to developers in small groups. It might help you develop some canned responses that work. Here is a simple way this could have been prevented. If you had a developer relations person with experience and skills in dealing with third party developers, who have completely different motivations from in-house coders, he or she could have quietly passed around a draft of what you wanted to say. This would have gotten very strong negative reactions. You would have been able to reformulate it to strip out the implied threats and turn it into a positive roadmap. It could have been framed as Here are some areas we promise to leave open for developers. If you work here, we will give you all kinds of extra support and promotion. Here is another simple way this could have been prevented. Create an advisory board of developers. Rotate people through it every 6-12 months. Let them vet announcements in advance. Let them respond to the questions. It works in every other company I have worked with. Here is what could be done instead of these repeated bombs you keep dropping on the community. Give people a present. Announce that you will use some of your precious ad space to promote third party apps, and not just the ones with millions of dollars of VC who happen to work in your building. Find new ways to rev share with developers. Offer all expense paid trips to select developers to visit your office for a day to hang out. HOLD A DEVELOPERS CONFERENCE. There are many other things a good developer relations person could do. Talk to Guy. That is how he started for Apple. One last thing. Give this developer relations person a seat at the table when big decisions are made. I can read lots of signals, like this high bar nonsense, that there are negative attitudes inside Twitter towards developers. They are a pain in the ass. Yes. But they do hundreds of millions of dollars in development and promotion for you for free. Hire someone good for $100K+. Give them a million dollar budget to really take care of developers and run conferences and get togethers around the world. It will pay off many times over. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Signature generation issue
After fixing the basic parts of your signature (please don't ever replace %26 with only a %, it screws up the encoding) and checking at http://quonos.nl/oauthTester/, I got : *Bad sorting!* All Base String parameters (query and POST parameters) must be sorted alphabetically. Tom On 3/14/11 3:02 PM, lappynet wrote: Hi I'm using C#.NET to produce an oob client. I've fallen at the first hurdle though as I'm failing to make the token request. I've gone through many iterations, and am no longer receiving a 417, 404, or 401. This is very positive! Now my application hangs whilst waiting for a response from twitter. (I left it running for an hour over lunch and still nothing happened, and the code didn't appear to want to step through.) I've tried with the values detailed in the documentation to have a look at the variables that have been produced from them in my algorithm. I think that I've traced it down to being the way I generate the signature string: string signingKey = Uri.EscapeDataString(ConsumerSecret) + ; HMACSHA1 hasher = new HMACSHA1(new ASCIIEncoding().GetBytes(signingKey)); string signatureString = Convert.ToBase64String(hasher.ComputeHash(new ASCIIEncoding().GetBytes(baseString))); My base string is: POSThttps%3A%2F%2Fapi.twitter.com%2Foauth %2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key%XXX %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0 Any pointers as to where I may be going wrong? Thanks in advance Georgina -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Signature generation issue
No, actually, it was my fault: it wasn't a %26, but a %3D. Oops! Base string is fine. Tom On 3/14/11 3:21 PM, Taylor Singletary wrote: Wow, my blindness to signature base string foo this morning is humbling. Thanks Tom. On Mon, Mar 14, 2011 at 7:15 AM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: After fixing the basic parts of your signature (please don't ever replace %26 with only a %, it screws up the encoding) and checking at http://quonos.nl/oauthTester/, I got : *Bad sorting!* All Base String parameters (query and POST parameters) must be sorted alphabetically. Tom On 3/14/11 3:02 PM, lappynet wrote: Hi I'm using C#.NET to produce an oob client. I've fallen at the first hurdle though as I'm failing to make the token request. I've gone through many iterations, and am no longer receiving a 417, 404, or 401. This is very positive! Now my application hangs whilst waiting for a response from twitter. (I left it running for an hour over lunch and still nothing happened, and the code didn't appear to want to step through.) I've tried with the values detailed in the documentation to have a look at the variables that have been produced from them in my algorithm. I think that I've traced it down to being the way I generate the signature string: string signingKey = Uri.EscapeDataString(ConsumerSecret) + ; HMACSHA1 hasher = new HMACSHA1(new ASCIIEncoding().GetBytes(signingKey)); string signatureString = Convert.ToBase64String(hasher.ComputeHash(new ASCIIEncoding().GetBytes(baseString))); My base string is: POSThttps%3A%2F%2Fapi.twitter.com http://2Fapi.twitter.com%2Foauth %2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key%XXX %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0 Any pointers as to where I may be going wrong? Thanks in advance Georgina -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] twitter dump where i only care about size
100GB is a lot... If the average JSON representation of a tweet takes 5 KB (and I think it might), you'd need 20 million tweets. Let's say that there are 100 million tweets sent per day (I think it's more though), and you get 1% from the sample stream (which would be 1 million). You'd have to capture that stream for 20 days to get enough tweets. Sample stream is at https://stream.twitter.com/1/statuses/sample.json (OAuth/Basic Auth required). Have fun capturing! Tom PS: I really hope I got the math right. :-) On 3/6/11 8:16 PM, Ted Pedersen wrote: I'd like to get somewhere around 100GB of tweets. It doesn't matter where they are from, when they were sent, etc. I'd just like to have a relatively large collection of data to use as assignment data for a class I'm teaching that uses Hadoop. Is such a collection available for download anywhere, or is there an existing program I could use to simply record twitter data for some period of time? (I've heard about both the firehose and the streaming API, but can't seem to find anything that is ready to run with that for this particular taskbut I might not know where to look). Cordially, Ted --- Ted Pedersen http://www.d.umn.edu/~tpederse -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Tweet Button Error
I've noticed the same thing, and if I've got firebug open, I see an error referring to jQuery not being defined. On Mar 3, 9:54 am, Jerry Thompson jerrycando...@gmail.com wrote: Just noticed that the Twitter's Tweet button which opens up a popup window for sharing, upon posting to Twitter, there's a link to Return to X site. Clicking this link will open the originating site within the JS popup. Shouldn't it simply just close the popup window as the user is already on the originating site? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] is there a way to update statuses more then 100 per semi-hour at all?
You can't post more than 127 (?) tweets per 4 hours (that's 1000 per day). This is a limit which can not be raised. Tom On 2/21/11 10:22 AM, John Carver wrote: greatings people. im using twitter api to update statuses but im getting this after about 100 of them have been posted in 1 hour time period: error: User is over daily status update limit i HAVE to post new tweets say 200 or even 500 per hour. is it possible at all? if yes how can i achieve this? it won't be spam or some kind of inappropriate materials. this is going to be value posts for my readers. i'd like to have this ability really much. thanks. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Rate limiting for streaming API
On 2/19/11 1:49 PM, Paresh Nakhe wrote: Hi, From what i understand, there is no concept of rate limiting for streaming api. Actually it does make sense because if anyone is to use 'statuses/sample' method (say) the limit will soon be crossed. We are working on something that will heavily use the streaming api, so if rate limiting is imposed in future it could create some problems. Are there any chances of such a restriction being imposed? There's no limit on the amount of tweets you can receive, but there's a limit on the amount of searches you can do, and the amount of connections you can have open. Secondly, this api requires authentication unlike search api. Authentication for user streams is fine but I don't understand it's need for streaming api. There's probably no real technical reason for why this is required, but for properly being able to keep statistics etc, it's needed. That, and the fact that there are several different levels of access to the API. Thanks, Paresh -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Rate limiting for streaming API
On 2/19/11 2:23 PM, Paresh Nakhe wrote: On going through the documentation in more detail i found this: - The the track parameter (keywords), and the location parameter (geo) on the statuses/filter method are rate-limited predicates. You can't have an infinite number of search terms. - After the */limitation period/* expires, all matching statuses will once again be delivered, along with a limit message that enumerates the total number of statuses that have been eliminated from the stream since the start of the connection. As far as I know, this limitation is only for user streams. When you get more than 2 or 3 statuses per second, it wouldn't be readable for the user anyway so the extra statuses get discarded and you get a limitation notice. I don't think that this goes for the normal stream. What exactly is the limitation period and what is one supposed to do after the limitation period expires? Destroy the current connection and create a new one? Just keep listening :-) Paresh. On Sat, Feb 19, 2011 at 6:22 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: On 2/19/11 1:49 PM, Paresh Nakhe wrote: Hi, From what i understand, there is no concept of rate limiting for streaming api. Actually it does make sense because if anyone is to use 'statuses/sample' method (say) the limit will soon be crossed. We are working on something that will heavily use the streaming api, so if rate limiting is imposed in future it could create some problems. Are there any chances of such a restriction being imposed? There's no limit on the amount of tweets you can receive, but there's a limit on the amount of searches you can do, and the amount of connections you can have open. Secondly, this api requires authentication unlike search api. Authentication for user streams is fine but I don't understand it's need for streaming api. There's probably no real technical reason for why this is required, but for properly being able to keep statistics etc, it's needed. That, and the fact that there are several different levels of access to the API. Thanks, Paresh -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- /What I have is not a dream, because I will make it a reality./ -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streams and @mentions
Home Timeline = check it in the friends dictionary Mention = match the tweet's text Search = match the keywords The rest is easy. Tom On 2/14/11 4:01 PM, Rich wrote: Hi all I'm just starting to play with the User Streams with the aim of allowing it in addition to REST api. I've had a stream open for most of the day looking at the received data and most of it looks pretty straightforward. When it comes to DM's, deletes, etc the message tells us that in the JSON. The one thing I haven't noticed is how mentions are displayed for example I receive a mention from someone I don't follow. This only appears on my Mentions API under REST and not my home timeline. When I connect over User Streams it seems to just come in as any other tweet. My question is how do I determine that this is a mention that shouldn't appear in my home timeline. Do I have to keep track of the initial friends message and compare the user id every time or is there something even simpler that I'm missing? Many thanks Richard -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Whitelisting is still in the docs. Please remove this.
won't sustain more than 15 users Why not? If you have 15 users, you can spread the API calls over them and the last time I checked, 15*350 gives you 5250 API calls. Tom On 2/12/11 7:24 PM, Jan Paricka wrote: Cool. I am weeks from launch and I am fucked. Without whitelisting, my app won't sustain more than 15 users. Thank you twitter, thank you very much. Btw, I really hoped to launch at @geekn'rolla Jan On Sat, Feb 12, 2011 at 6:33 PM, mabujo jaa...@gmail.com mailto:jaa...@gmail.com wrote: Jan, yes twitter have said they're removing whitelisting for new requests, see here : http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 On Feb 12, 5:37 pm, Jan Paricka jpari...@gmail.com mailto:jpari...@gmail.com wrote: Whoa, does that mean twitter is no longer whitelisting?? Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. Please advice, Jan On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com mailto:140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. Thanks. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: DM rate limit
Actually, the limit is 250 per account, not 250 DMs per IP. Tom On 2/12/11 9:10 PM, DaveH wrote: Dossy: Don't be so quick to condemn. I have an app that uses DMs and ALL DM traffic is generated by users and they know it--so there is no spamming. There are legitimate uses of DMs that users are OK with that push an app beyond 250/day. Think of it this way, if an application has 300 followers and they all interact via private message (DM) one time per day, then 50 users will be unable to communicate on any given day. On Feb 12, 11:46 am, Dossy Shiobarado...@panoptic.com wrote: Any one Twitter account that sends250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. On 2/12/11 2:31 PM, Trevor Dean wrote: Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] About http response:Failed to validate oauth signature and token in India
Just a guess: could it be related to using non-ASCII characters that get encoded improperly? Tom On 2/10/11 8:09 AM, Cathy Yeh wrote: Dears, We found a log-in problem ONLY happened in India. We implemented a mediatek widget and use xAuth for authentication. The testers in India try to log in Twitter, however, sometimes they cannot log in and receive a http response below: Failed to validate oauth signature and token Would you mind helping us to resolve this issue? Thanks! Sincerely, Cathy -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Failed to validate oauth signature and token
Please check your Base String at http://quonos.nl/oauthTester/. You seem to be missing the between the parameters. I also see other issues, but the signature checker will reveal those to you as well. Tom On 2/9/11 12:15 AM, Dale wrote: I am attempting to set up a ColdFusion script to do auto updates to Twitter when a new article is posted to our CMS. I have been having trouble getting the request token and keep getting the Failed to validate oauth signature and token error message when making attempts. Here is my request string... POSThttp%3A%2F%2Fapi%2Etwitter%2Ecom%2Foauth%2Frequest%5Ftoken%26oauth %5Fconsumer%5Fkey%XXX%26oauth%5Fsignature%5Fmethod%3DHMAC %2DSHA1%26oauth%5Ftimestamp%3D1297206414%26oauth%5Fversion %3D1%2E0%26oauth%5Fnonce%3D556979%2E9534 I have verified that the time stamp is the the correct epoch time in my time zone (PST). Any help would be appreciated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] twitter ideas for multiple users....or does this exist?
Yes, it exists, but it's currently in a very closed beta phase within the Twitter HQ. You may find more if you search for contributors. I haven't seen an API for this yet. Tom On 2/8/11 7:09 PM, Victoria Smith wrote: Hello Twitter, I thought I noticed this on a twitter page...but now that i'm looking i'm thinking I imagined this myself, and since I proposed this to my company as a possible idea, I look like an idiot if I'm completely wrong about this. The idea is basically for Company twitter pages. There are usually more than one member of a company so there is a lot of stuff different people want to say, if each employee had a member ID, they could post their own tweets under the same company name, but with their own identification. In a company like ours it would generate a bigger buzz of posts on twitter, and for us attract more followers. Did I completely make this up, or does this exist. I don't know the appropriate channel for this question, but I was hoping I could get an answer? Victoria Smith -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] twitter ideas for multiple users....or does this exist?
Actually, I meant Google : http://www.google.com/search?q=twitter+contributors+api Tom On 2/8/11 8:01 PM, Victoria Smith wrote: Tom, Thank you for getting back to me Contributors? I'm not exactly sure what that means? Just search it on Twitter.? -Victoria On Tue, Feb 8, 2011 at 1:57 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Yes, it exists, but it's currently in a very closed beta phase within the Twitter HQ. You may find more if you search for contributors. I haven't seen an API for this yet. Tom On 2/8/11 7:09 PM, Victoria Smith wrote: Hello Twitter, I thought I noticed this on a twitter page...but now that i'm looking i'm thinking I imagined this myself, and since I proposed this to my company as a possible idea, I look like an idiot if I'm completely wrong about this. The idea is basically for Company twitter pages. There are usually more than one member of a company so there is a lot of stuff different people want to say, if each employee had a member ID, they could post their own tweets under the same company name, but with their own identification. In a company like ours it would generate a bigger buzz of posts on twitter, and for us attract more followers. Did I completely make this up, or does this exist. I don't know the appropriate channel for this question, but I was hoping I could get an answer? Victoria Smith -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Is there going to be another Chirp?
I'd prefer London or some other West-European city. Tom On 2/7/11 5:35 AM, Brainewave Consulting wrote: I vote for Chirp: NYC! *Mike Caprio* /Principal and Lead Consultant/ Brainewave Consulting 402 Graham Avenue PMB 211 Brooklyn, NY 11211 p: +1-347-269-0558 @brainewave On Feb 6, 2011, at 11:20 PM, zbowl...@gmail.com mailto:zbowl...@gmail.com wrote: Yah, more of these would be fun. On Feb 6, 12:28 pm, Abraham Williams 4bra...@gmail.com wrote: How about some more state of the union events too. I thought they were going to be quarterly. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham http://github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sun, Feb 6, 2011 at 12:21, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Maybe this is the wrong place to ask, but is there going to be another Chirp? If so, when and where? I'm making my conference plans for the year and pretty much know when everything is *except* Chirp! -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Media Partnerships and Oembed for Twitter's Detail Panel
That is correct. It will only show for users who have the plugin. Tom On 2/3/11 9:39 PM, Ashley Sarver wrote: With the plugin, this is only visible by people who enable the plugin? We're looking to open it for the entire site, so that whenever anyone tweets a grooveshark song, the media will show up in the details panel. On Feb 2, 7:49 am, Ken D.k...@cimas.ch wrote: I just re-enabled the Parrotfish plugin and it's pretty amazing. It's pulling content from my own website and from just about any URL mentioned in a Tweet. Goes way beyond the advertised performance. On Feb 2, 1:26 pm, Tom van der Woerdti...@tvdw.eu wrote: Some Twitter applications (including my own) use embed.ly to display content. Tom On 2/2/11 1:25 PM, Ken D. wrote: Ashley, While waiting for native support from Twitter, have you checked out the embed.ly Parrotfish plugin (http://labs.embed.ly/) ? Grooveshark is one of 160-plus OEmbed-compliant media partners supported by the plugin. Tweets bearing supported URLs are marked in the timeline and yes, you'll see Grooveshark content in your Twitter right pane. Don't know how many people are using it. Ken On Feb 1, 9:38 pm, Ashley Sarverasarv...@gmail.comwrote: The purpose of this is to find out a way to use twitter's oembed for listen.grooveshark.com links, and embed the media player of a specific song when the link is posted. How long does requesting permission for a media partnership take, and has anyone had problems requesting a partnership? Has anyone atempted to use oembed on twitter, or began working with oembed? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Media Partnerships and Oembed for Twitter's Detail Panel
You cannot just embed your content into Twitter without having a content partnership with them. Without using addons, that is. Tom On 2/3/11 10:08 PM, Ashley Sarver wrote: Is there any way we would be able to open that up to everyone on twitter? Or do I just have to wait until Twitter decides to re-open back up media partnerships? On Feb 3, 3:40 pm, Tom van der Woerdti...@tvdw.eu wrote: That is correct. It will only show for users who have the plugin. Tom On 2/3/11 9:39 PM, Ashley Sarver wrote: With the plugin, this is only visible by people who enable the plugin? We're looking to open it for the entire site, so that whenever anyone tweets a grooveshark song, the media will show up in the details panel. On Feb 2, 7:49 am, Ken D.k...@cimas.chwrote: I just re-enabled the Parrotfish plugin and it's pretty amazing. It's pulling content from my own website and from just about any URL mentioned in a Tweet. Goes way beyond the advertised performance. On Feb 2, 1:26 pm, Tom van der Woerdti...@tvdw.euwrote: Some Twitter applications (including my own) use embed.ly to display content. Tom On 2/2/11 1:25 PM, Ken D. wrote: Ashley, While waiting for native support from Twitter, have you checked out the embed.ly Parrotfish plugin (http://labs.embed.ly/) ? Grooveshark is one of 160-plus OEmbed-compliant media partners supported by the plugin. Tweets bearing supported URLs are marked in the timeline and yes, you'll see Grooveshark content in your Twitter right pane. Don't know how many people are using it. Ken On Feb 1, 9:38 pm, Ashley Sarverasarv...@gmail.com wrote: The purpose of this is to find out a way to use twitter's oembed for listen.grooveshark.com links, and embed the media player of a specific song when the link is posted. How long does requesting permission for a media partnership take, and has anyone had problems requesting a partnership? Has anyone atempted to use oembed on twitter, or began working with oembed? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Media Partnerships and Oembed for Twitter's Detail Panel
Some Twitter applications (including my own) use embed.ly to display content. Tom On 2/2/11 1:25 PM, Ken D. wrote: Ashley, While waiting for native support from Twitter, have you checked out the embed.ly Parrotfish plugin ( http://labs.embed.ly/ ) ? Grooveshark is one of 160-plus OEmbed-compliant media partners supported by the plugin. Tweets bearing supported URLs are marked in the timeline and yes, you'll see Grooveshark content in your Twitter right pane. Don't know how many people are using it. Ken On Feb 1, 9:38 pm, Ashley Sarverasarv...@gmail.com wrote: The purpose of this is to find out a way to use twitter's oembed for listen.grooveshark.com links, and embed the media player of a specific song when the link is posted. How long does requesting permission for a media partnership take, and has anyone had problems requesting a partnership? Has anyone atempted to use oembed on twitter, or began working with oembed? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] New Twitter bug?
I'd say: get rid of xAuth, get rid of this problem (and probably a lot of other problems as well). Tom On 2/2/11 6:36 PM, Naveen Ayyagari wrote: Not that I am advocating any change because I prefer the way it works now. But this has been a point of confusion for some of our users as well. The issue stems from when a user uses xAuth to authenticate, they understand it as they have used their password so if they change the app should no longer have access. When a user uses the OAuth flow on the web, they generally seem to understand they are granting access to the application regardless of password. Some other services that use xAuth like authorization schemes will actually invalidate the OAuth connection when the user changes their password IF they have been authorized using the xAuth like mechanism. This is confusing for us as the developer, but seems to make sense to the majority of users. I think this is more of a user education issue than an actual technical issue.. --Naveen On Feb 2, 2011, at 6:53 AM, Scott Wilcox wrote: Hello, Tweetdeck uses the OAuth/Streaming API which is independent of your password. Are you suggesting that when you change your password it should invalidate your OAuth connections? If so, then no, it does not do that. Scott. On 2 Feb 2011, at 14:18, cazz wrote: I can hardly believe it's true but I discovered a rather strange issue Once you've added a twitter account to Tweetdeck, you're allowed to tweet from that account via Tweetdeck. No surprises so far But when you change your password in Twitter, there's no account/ password check again in Tweetdeck. Which means that once you've changed your password in Twitter, you don't exclude other twitterclients from having acces to your Twitteraccount!!! I would expect every time posting a tweet there should be a credentials check So this seems not very logical to me, or is it just me thinking this smells pretty much like a bug? See my tweet: http://twitter.com/#!/Cazz/status/32802305644433408 Cheers, Cazz -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Upgrading from Read to Read / Write access for OAuth API Key
Actually, since the user needs to re-authorize the application, I do not think that this is a bug. Tom On 1/31/11 10:45 PM, Tim Bull wrote: While this makes me happy (from a developers point of view), surely this is a bug and therefore not to be relied on? As a user, I agree with the logic that if I authorised Read only, the application shouldn't be able to turn this into Read/Write without some subsequent approval. Tim On Jan 31, 1:46 pm, Abraham Williams4bra...@gmail.com wrote: Taylor, Confirmed. I just upgraded read only tokens and was able to successfully send a DM. Thank you for finally allowing read only access tokens to be upgraded to read and write access tokens. This issue has been plaguing developers for almost a year now. Both forcing applications to ask for permission they didn't need if there was even a remote possibility they might want write permissions in the future and biting devs in the ass if they unknowingly built up a customer base of read only tokens. I hope we will continue to see fixes coming down the pipe to keep Twitter API a viable platform for further development. Thank you again, Abraham - Abraham Williams | Hacker Advocate | abrah.am @abrahamhttps://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sun, Jan 30, 2011 at 11:19, Taylor Singletary taylorsinglet...@twitter.com wrote: You'll have to re-ask your users for permission for write mode and you won't have any way via the API to track who is ready to read/write yet -- you'll want to manage the conversion process yourself and track whether you've converted your users yet or not. The thinking behind this is that when your users authorized your app, they only authorized it for read-access. Wanting write access requires a new agreement with the user. The oauth/authorize step should now upgrade to read/write from read-only tokens when the user is re-challenged. Taylor On Sun, Jan 30, 2011 at 8:32 AM, Adam Green140...@gmail.com wrote: So if a user authorizes an app for read access, the app can switch to read/write at any time without asking the users permission? Is this true? Anyone from Twitter have any input on this? On Sun, Jan 30, 2011 at 11:04 AM, Patrick Kennedykenned...@gmail.com wrote: Tim - 1. Changing from read to read/write won't change you API consumer keys or tokens. 2. Your application's users don't authorized for read or read/write; they merely use your application, which you offer as read or read/write to the world. That is to say, if it's read, your application can only read its tweets, and if read/write, it can both read its own tweet and post to the world. I'd say go ahead and switch to read/write, given the fact that you now want that functionality. ~Patrick On Sat, Jan 29, 2011 at 10:24 PM, Tim Bulltim.b...@binaryplex.com wrote: We must be about the only developers in the universe that requested users grant only read access when we first got people to connect http://trunk.lyto Twitter (I think of the 40 or so apps authorized on my account, Trunk.ly is the only one that asks for Read only). Never ask for more access than you need is my philosophy. Doh! Of course now, we want to add some Tweet out functions which require users grant us Write access. A couple of questions for the Twitter people. 1. If we change the access in the application from read to read/write does this reset the API key, or will it stay the same (hoping it stays the same). 2. How can I work out if existing users have authorised us for read/ write? I looked at http://developer.twitter.com/doc/get/account/verify_credentials but it doesn't show me what access they have. Do I have to write, fail, force them to step through OAuth then post? Or is there a way of knowing before hand it will fail and asking them to upgrade? Thanks, Tim -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http
Re: [twitter-dev] Stream API with firehorse method
On 1/25/11 9:08 PM, Zhe Chen wrote: Hi, On your website, you said the Firehose is not a generally available resource. Does that mean I cannot use it in my application? What should I do if I want to use it. Thanks I don't think that you want the Firehose in your application. The Firehose is a stream with *all* Tweets that *any* Twitter user sends. Depending on your application, you may like : - Desktop application: User Streams - Web-based application: Site Streams - Search-based application: filter.json (normal streams) Tom -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: iPhone twitter client
Answers inline.
Sent from my iPhone
On Jan 19, 2011, at 9:32 AM, Bess bess...@gmail.com wrote:
I'd like to get feedback on possible webinar on iOS Twitter API.
Such as
- What are your pain points of integrating Twitter on iOS app?
Launching the iOS simulator takes long. For me that's it.
- What are your main problems?
None, the twitter API is very easy to understand.
- What would you like to achieve using Twitter API on iOS app?
Awesomeness. :-)
Can anyone suggest any good online webinar? learning platform
I'd say dev.twitter.com but that's probably not the best place to learn how to
authenticate etc. To learn this I recommend reading the oauth rfc.
Tom
On Jan 18, 9:03 pm, ronnocv ronnocv11223...@gmail.com wrote:
I tried to make a twitter client i have an api with 2 files
TwitterRequest.h and TwitterRequest.m
here is the code for the .m file
//
// TwitterRequest.m
// Chirpie
//
// Created by Brandon Trebitowski on 6/15/09.
// Copyright 2009 __MyCompanyName__. All rights reserved.
//
#import TwitterRequest.h
@implementation TwitterRequest
@synthesize username;
@synthesize password;
@synthesize receivedData;
@synthesize delegate;
@synthesize callback;
@synthesize errorCallback;
-(void)friends_timeline:(id)requestDelegate requestSelector:
(SEL)requestSelector{
isPost = NO;
// Set the delegate and selector
self.delegate = requestDelegate;
self.callback = requestSelector;
// The URL of the Twitter Request we intend to send
NSURL *url = [NSURL
URLWithString:@http://api.twitter.com/1/statuses/
update.xml];
[self request:url];
}
-(void)statuses_update:(NSString *)status delegate:(id)requestDelegate
requestSelector:(SEL)requestSelector; {
isPost = YES;
// Set the delegate and selector
self.delegate = requestDelegate;
self.callback = requestSelector;
// The URL of the Twitter Request we intend to send
NSURL *url = [NSURL
URLWithString:@http://api.twitter.com/1/statuses/
update.xml];
requestBody = [NSString stringWithFormat:@status=%@,status];
[self request:url];
}
-(void)request:(NSURL *) url {
theRequest = [[NSMutableURLRequest alloc] initWithURL:url];
if(isPost) {
NSLog(@ispost);
[theRequest setHTTPMethod:@POST];
[theRequest setValue:@application/x-www-form-urlencoded
forHTTPHeaderField:@Content-Type];
[theRequest setHTTPBody:[requestBody
dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES]];
[theRequest setValue:[NSString
stringWithFormat:@%d,[requestBody
length] ] forHTTPHeaderField:@Content-Length];
}
theConnection = [[NSURLConnection alloc] initWithRequest:theRequest
delegate:self];
if (theConnection) {
// Create the NSMutableData that will hold
// the received data
// receivedData is declared as a method instance elsewhere
receivedData=[[NSMutableData data] retain];
} else {
// inform the user that the download could not be made
}
}
- (void)connection:(NSURLConnection *)connection
didReceiveAuthenticationChallenge:(NSURLAuthenticationChallenge
*)challenge {
//NSLog(@challenged %@,[challenge proposedCredential] );
if ([challenge previousFailureCount] == 0) {
NSURLCredential *newCredential;
newCredential=[NSURLCredential credentialWithUser:[self
username]
password:[self
password]
persistence:NSURLCredentialPersistenceNone];
[[challenge sender] useCredential:newCredential
forAuthenticationChallenge:challenge];
} else {
[[challenge sender] cancelAuthenticationChallenge:challenge];
// inform the user that the user name and password
// in the preferences are incorrect
NSLog(@Invalid Username or Password);
}
}
- (void)connection:(NSURLConnection *)connection didReceiveResponse:
(NSURLResponse *)response
{
// this method is called when the server has determined that it
// has enough information to create the NSURLResponse
// it can be called multiple times, for example in the case of a
// redirect, so each time we reset the data.
// receivedData is declared as a method instance elsewhere
//[receivedData setLength:0];
}
- (void)connection:(NSURLConnection *)connection didReceiveData:
(NSData *)data {
//NSLog([[NSString alloc] initWithData:data
encoding:NSUTF8StringEncoding]);
// append the new data to the receivedData
// receivedData is declared as a method instance elsewhere
[receivedData appendData:data];
}
- (void)connection:(NSURLConnection *)connection
didFailWithError:(NSError *)error
Re: [twitter-dev] is streaming API read-only?
Yes, that is correct. The HTTP protocol does not really allow two-way communication. You should use the normal API instead. Tom On 1/17/11 9:19 PM, Gary Ma wrote: Hi, I have an impression that streaming API (for example, user stream API) is read-only. I can obtain statuses but I won't be able to update, such as add follows to a user account. Is it correct? Thanks, Gary -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] RE: New twitter in ie8 broken again
Sounds like a cookie/cache issue. Tom Sent from my iPhone On Jan 5, 2011, at 5:00 PM, Dean Collins d...@cognation.net wrote: Huh well that IS interesting. I have no idea why but someone just emailed me to answer my question about New Twitter being broken for IE8. They told me if you turn on “InPrivate” browsing on IE8 that new twitter works…. Just tried it for my account http://www.Twitter.com/LiveNascarChat came up perfect. Can someone from twitter explain what in their code broke this morning at 8am that is negated by inprivate browsing? Cheers, Dean From: Dean Collins Sent: Wednesday, January 05, 2011 8:23 AM To: twitter-development-talk@googlegroups.com Subject: New twitter in ie8 broken again New twitter in ie8 is broken again, works great in firefox but started failing in ie8 about 8am this morning. Cheers, Dean -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
