from:"Taylor Singletary"

We'll look into this, thanks for the report. Would be very helpful if you
can provide specific Tweet IDs where you've encountered this issue.

Thanks!
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 12, 2011 at 3:08 AM, Rachel Green rachelmgree...@gmail.comwrote:

 I have started seeing this issue too.

 On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote:
  Can anybody from Twitter let us know what is going on?  Seems like it
  is not an isolated issue.
 
  Thanks,
  Mike
 
  On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote:
 
 
 
 
 
 
 
   I have been seeing this exact 24:00 timestamp issue too for the last
   few days too.
 
   Also using tweepy.
 
   thanks
   Adam
 
   On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote:
 
Hi everybody,
 
My application queries the search API periodically throughout the
day.  I'm still working on a solution using the streaming API, but
this has been working fairly well for my needs.
 
About 4 days ago I started getting errors from the Python library
 that
I use to perform the queries (tweepy.)  It appears that some results
contain what appear to be invalid timestamps.  Here is a sample of
 the
times that I see for some tweets:
 
ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not
match format '%a, %d %b %Y %H:%M:%S +'
ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not
match format '%a, %d %b %Y %H:%M:%S +'
ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not
match format '%a, %d %b %Y %H:%M:%S +'
ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not
match format '%a, %d %b %Y %H:%M:%S +'
 
These timestamps all have 24 as the hour, which doesn't seem correct.
Is anybody else seeing the same thing?
 
Thanks,
Mike

 --
 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!

Hi everyone on the thread,

When you're having this problem, what endpoints are you using for
authentication?

Make sure that you're using https://api.twitter.com/oauth/authorize on the
redirect to Twitter step of OAuth. If you're using
https://api.twitter.com/oauth/authenticate, you'll never be able to
negotiate a higher than RW access level token, regardless of what you've
configured in your application detail settings.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi nlupa...@googlemail.comwrote:

 The same problem here - i am not sure if the api guys are aware of the
 consequences every change they make...

 On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote:
  I have the same problem.
 
  On the App settings it is set to:
 
  Read, Write and Accessdirectmessages
 
  But when users authenticate with OAuth, it's telling users:
 
  This application will not be able to:
  Access yourdirectmessages.
 
  How do we fix this?
 
  On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote:
 
 
 
 
 
 
 
   Most of my apps require read access forDirectMessages, but they're
   only reading from one account.  Many users DM to one account and I
   need access to that one account to grab all the DMs (which no longer
   works as of June 30th).
 
   I changed the Access Level of all my apps to Read, Write andDirect
   Message, but it doesn't seem that the change has taken place, or I'm
   missing something, somewhere in terms of what I need to do?
 
   When I try and re-authorize an account I see the following on the
   Twitter / Authorize screen:
 
   This application will not be able to:
   Access yourdirectmessages.
   See your Twitter password.
 
   What else do I need to do?  I have confirmed that the application
   settings on Twitter do say, Read, Write andDirectMessagesfor my app
   but I can only use my access token (for the Twitter handle
   associated with the app) to accessdirectmessages, anytime I try and
   re-authorize any account through my actual app, I see:
 
   This application will not be able to:
   Access yourdirectmessages.
   See your Twitter password.
 
   ... which isn't inline with how I setup the settings.  Any help would
   be greatly appreciated.  I'm really hoping I'm missing something small
   here.

 --
 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: Access level changed to Read, Write AND Direct Message but still can't access DMs!

On the step where you arrive at Twitter's credential screen, what URL do you
see in the browser bar?

If it's the URL that's being returned by your authenticateURL function, then
it's a URL that can't upgrade your tokens. You want to use the URL returned
in the autorizeURL function instead.

Also, these URLs are out-of-date. They should have the api subdomain
attached, like https://api.twitter.com/oauth/access_token

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 12, 2011 at 9:05 AM, Nencho Lupanov nlupa...@googlemail.comwrote:

 Hi again,

 here is what i have set in my Oauth library:

   function accessTokenURL() { return '
 https://twitter.com/oauth/access_token'; }
   function authenticateURL() { return '
 https://twitter.com/oauth/authenticate'; }
   function authorizeURL() { return 'https://twitter.com/oauth/authorize';
 }
   function requestTokenURL() { return '
 https://twitter.com/oauth/request_token'; }

 Please advice if it needs to be changed?

 On 12 July 2011 16:13, Taylor Singletary taylorsinglet...@twitter.comwrote:

 Hi everyone on the thread,

 When you're having this problem, what endpoints are you using for
 authentication?

 Make sure that you're using https://api.twitter.com/oauth/authorize on
 the redirect to Twitter step of OAuth. If you're using
 https://api.twitter.com/oauth/authenticate, you'll never be able to
 negotiate a higher than RW access level token, regardless of what you've
 configured in your application detail settings.

 @episod http://twitter.com/intent/user?screen_name=episod - Taylor
 Singletary



 On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi nlupa...@googlemail.comwrote:

 The same problem here - i am not sure if the api guys are aware of the
 consequences every change they make...

 On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote:
  I have the same problem.
 
  On the App settings it is set to:
 
  Read, Write and Accessdirectmessages
 
  But when users authenticate with OAuth, it's telling users:
 
  This application will not be able to:
  Access yourdirectmessages.
 
  How do we fix this?
 
  On Jul 4, 5:38 pm, alexre...@gmail.com alexre...@gmail.com wrote:
 
 
 
 
 
 
 
   Most of my apps require read access forDirectMessages, but they're
   only reading from one account.  Many users DM to one account and I
   need access to that one account to grab all the DMs (which no longer
   works as of June 30th).
 
   I changed the Access Level of all my apps to Read, Write andDirect
   Message, but it doesn't seem that the change has taken place, or I'm
   missing something, somewhere in terms of what I need to do?
 
   When I try and re-authorize an account I see the following on the
   Twitter / Authorize screen:
 
   This application will not be able to:
   Access yourdirectmessages.
   See your Twitter password.
 
   What else do I need to do?  I have confirmed that the application
   settings on Twitter do say, Read, Write andDirectMessagesfor my app
   but I can only use my access token (for the Twitter handle
   associated with the app) to accessdirectmessages, anytime I try and
   re-authorize any account through my actual app, I see:
 
   This application will not be able to:
   Access yourdirectmessages.
   See your Twitter password.
 
   ... which isn't inline with how I setup the settings.  Any help would
   be greatly appreciated.  I'm really hoping I'm missing something
 small
   here.

 --
 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] Re: Could not authenticate using OAuth...

It depends on what you mean by log out -- if they log out of Twitter and
you have an access token they granted your application, you can use that
access token until the end-user revokes your access. You can store the token
forever, but that doesn't necessarily mean it will be valid forever -- the
user can sever your application's access at any time. The tokens themselves
do not expire without user intervention though.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 12, 2011 at 9:38 AM, Astralis astralis...@gmail.com wrote:

 Web application.

 --
 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


-- 
Have you visited the Developer Discussions feature on 
https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings: 
http://groups.google.com/group/twitter-development-talk/subscribe

Re: [twitter-dev] Re: Could not authenticate using OAuth...

When your end-users are using the API, are they doing so client-side in
their browser or are you making server-to-server requests on their behalf?

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 12, 2011 at 10:12 AM, Astralis astralis...@gmail.com wrote:

 I might be missing how this works, but I am storing the user tokens and I'm
 able to post through the web app onto Twitter with success.

 But, I found that when the user logs out of Twitter (via the Twitter
 website), the user's no longer able to post and the tokens seem to be
 invalid and I receive an error message that oAuth could not authenticate.

 When the user logs back into Twitter (again via the Twitter website) the
 tokens work again.

 Thoughts?

 --
 Have you visited the Developer Discussions feature on
 https://dev.twitter.com/discussions yet?

 Twitter developer links:
 Documentation and resources: https://dev.twitter.com/docs

 API updates via Twitter: https://twitter.com/twitterapi

 Unsubscribe or change your group membership settings:
 http://groups.google.com/group/twitter-development-talk/subscribe


-- 
Have you visited the Developer Discussions feature on 
https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings: 
http://groups.google.com/group/twitter-development-talk/subscribe

Re: [twitter-dev] Re: Getting invalid timestamps from search API

Thanks for the helpful ids. We've identified the issue and are working on a
fix. Hope to have it out later today but it's possible it won't be until
later this week. Thanks for your patience!

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 12, 2011 at 11:24 AM, Doza mcard...@gmail.com wrote:

 Hi Taylor,

 Thanks for the response.  It looks like the following Tweets generated
 those invalid timestamps.

 90208830268510208: Mon, 11 Jul 2011 24:00:35 +
 90582035785195520: Tue, 12 Jul 2011 24:43:34 +
 90572723142660097: Tue, 12 Jul 2011 24:06:34 +

 Let me know if I can provide you with any more information.

 Thanks,
 Mike


 On Jul 12, 10:12 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  We'll look into this, thanks for the report. Would be very helpful if you
  can provide specific Tweet IDs where you've encountered this issue.
 
  Thanks!
  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary
 
  On Tue, Jul 12, 2011 at 3:08 AM, Rachel Green rachelmgree...@gmail.com
 wrote:
 
 
 
 
 
 
 
   I have started seeing this issue too.
 
   On Jul 12, 6:05 am, Doza mcard...@gmail.com wrote:
Can anybody from Twitter let us know what is going on?  Seems like it
is not an isolated issue.
 
Thanks,
Mike
 
On Jul 11, 10:37 pm, Adam Kent adam.k...@gmail.com wrote:
 
 I have been seeing this exact 24:00 timestamp issue too for the
 last
 few days too.
 
 Also using tweepy.
 
 thanks
 Adam
 
 On Jul 10, 10:37 am, Doza mcard...@gmail.com wrote:
 
  Hi everybody,
 
  My application queries the search API periodically throughout the
  day.  I'm still working on a solution using the streaming API,
 but
  this has been working fairly well for my needs.
 
  About 4 days ago I started getting errors from the Python library
   that
  I use to perform the queries (tweepy.)  It appears that some
 results
  contain what appear to be invalid timestamps.  Here is a sample
 of
   the
  times that I see for some tweets:
 
  ValueError: time data u'Thu, 07 Jul 2011 24:58:43 +' does not
  match format '%a, %d %b %Y %H:%M:%S +'
  ValueError: time data u'Thu, 07 Jul 2011 24:59:45 +' does not
  match format '%a, %d %b %Y %H:%M:%S +'
  ValueError: time data u'Fri, 08 Jul 2011 24:58:03 +' does not
  match format '%a, %d %b %Y %H:%M:%S +'
  ValueError: time data u'Fri, 08 Jul 2011 24:33:41 +' does not
  match format '%a, %d %b %Y %H:%M:%S +'
 
  These timestamps all have 24 as the hour, which doesn't seem
 correct.
  Is anybody else seeing the same thing?
 
  Thanks,
  Mike
 
   --
   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

 --
 Have you visited the Developer Discussions feature on
 https://dev.twitter.com/discussions yet?

 Twitter developer links:
 Documentation and resources: https://dev.twitter.com/docs
 API updates via Twitter: https://twitter.com/twitterapi

 Unsubscribe or change your group membership settings:
 http://groups.google.com/group/twitter-development-talk/subscribe


-- 
Have you visited the Developer Discussions feature on 
https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings: 
http://groups.google.com/group/twitter-development-talk/subscribe

Re: [twitter-dev] Re: Rate Limit

2011-07-11 Thread Taylor Singletary

Hi there,

The widgets are rate limited the same as twitter.com and the API: a single
IP address is allowed up to 150 unauthenticated requests per hour against
api.twitter.com and twitter.com. Search widgets are rate limited also by IP
address but with different limits.

If you share an IP address with many users, you may exhaust the amount of
requests your shared IP address can make to Twitter. In that case you might
see an empty/slow to update widget. Your end users might see a fully
functional widget if their own perspectival rate limits have not been
exhausted.

If you're using a search widget instead, it's good to know that our search
index only maps a few days worth of tweets -- if there haven't been tweets
recently matching the queries in a search widget, it will also have no
results to display.


@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jul 11, 2011 at 12:20 PM, twitterwidget
twitterwidget...@gmail.comwrote:

 Someone please help.

 On Jul 8, 10:04 am, twitterwidget twitterwidget...@gmail.com wrote:
  Can someone please help me to understand how rate limiting works for
  twitter widget, either the profile or the list widget. I have gone
  through the rate limit faq herehttp://
 dev.twitter.com/pages/rate_limiting_faq
  which talks about authorized and unauthorized requests which is a bit
  confusing to me.
 
  I want to understand this because the widget goes blank on our site
  sometimes, which we don't want it to happen.
 
  Can you please 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


-- 
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: Rate Limit

2011-07-11 Thread Taylor Singletary

Authenticated requests aren't possible using the widgets really (well, not
without getting pretty complex and at that point you're building something
yourself).

Authenticated means I'm requesting data from Twitter and it knows that I'm
@episod as opposed to just an anonymous user calling Twitter.

To a certain degree, this is just the way that rate limiting works right now
and you'll have to deal with it. Though if you've got some technical
interest and a developer, you can find ways to mitigate the issue -- happy
to walk through some of those options with you if you like.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jul 11, 2011 at 1:03 PM, twitterwidget
twitterwidget...@gmail.comwrote:

 Thanks Taylor for getting back to me.

 But can you tell me what is the difference between authenticated
 request and unauthenticated request?
 Is there any other better approach of using this widget or do we have
 to just live with it?



 On Jul 11, 12:55 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  Hi there,
 
  The widgets are rate limited the same as twitter.com and the API: a
 single
  IP address is allowed up to 150 unauthenticated requests per hour against
  api.twitter.com and twitter.com. Search widgets are rate limited also by
 IP
  address but with different limits.
 
  If you share an IP address with many users, you may exhaust the amount of
  requests your shared IP address can make to Twitter. In that case you
 might
  see an empty/slow to update widget. Your end users might see a fully
  functional widget if their own perspectival rate limits have not been
  exhausted.
 
  If you're using a search widget instead, it's good to know that our
 search
  index only maps a few days worth of tweets -- if there haven't been
 tweets
  recently matching the queries in a search widget, it will also have no
  results to display.
 
  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary
 
  On Mon, Jul 11, 2011 at 12:20 PM, twitterwidget
  twitterwidget...@gmail.comwrote:
 
 
 
 
 
 
 
   Someone please help.
 
   On Jul 8, 10:04 am, twitterwidget twitterwidget...@gmail.com wrote:
Can someone please help me to understand how rate limiting works for
twitter widget, either the profile or the list widget. I have gone
through the rate limit faq herehttp://
   dev.twitter.com/pages/rate_limiting_faq
which talks about authorized and unauthorized requests which is a bit
confusing to me.
 
I want to understand this because the widget goes blank on our site
sometimes, which we don't want it to happen.
 
Can you please 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

 --
 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] What is the best strategy to get this volume of data?

2011-07-07 Thread Taylor Singletary

What kinds of queries are you wanting to send -- search queries? Are they
different queries or are you repeating the same queries over and over? Do
you display the results on a website? In what other ways is the data used?
Who are your users and how does this service their needs?

There are likely alternate implementation options that won't necessitate you
having to make 100 queries every minute.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jul 6, 2011 at 10:22 PM, Ben Flux b...@trafficjunction.co.uk wrote:

 I want to send 100 queries to Twitter every minute via my server
 application and would like to know if there is a method that will
 allow me to do this?

 --
 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] Any idea to minimize my request number?

2011-07-07 Thread Taylor Singletary

Hi,

You may find better results using the Streaming API instead of the Search
API: https://dev.twitter.com/pages/streaming_api

Also, if you did have to perform bulk lookups of multiple users, the
users/lookup API is superior in that you can perform 80-100 user lookups in
a single call: https://dev.twitter.com/doc/get/users/lookup

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jul 7, 2011 at 8:25 AM, Jean-Yves Kiger jyki...@gmail.com wrote:

 Hi everyone,

 Here is my project:
 I would like to make a java programm wich would store as many tweets
 as possible about one subject using the search API.  And once it is
 done, i would like to get basic informations about their posters, such
 as their number of followers, number of tweets and so on. But for that
 purpose i will have to make one request like that

 http://api.twitter.com/1/users/show.json?screen_name=SCREEN_NAME_STR

 for each individual poster, wich will surely reaches the rate
 limitation before i could store all the informations i want.
 I dont find these informations in the HTML code of the homepage of
 each users, so i think i will have to get them through the REST API.

 Do you have any idea to get the informations i want to get without
 overflow the limitation?

 Thanks for reading, and pardon my english.

 --
 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: Site Streams

Orian,

It's just that one shouldn't go to production without checking in with us
first right now so we can make sure the capacity outlook is good. We're
getting closer to increased capacity on Site Streams, but until then we're
cautious with additional production consumers, especially with larger user
bases.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 5, 2011 at 10:39 PM, Orian Marx or...@orianmarx.com wrote:

 Mark, this is a great post, thanks for taking the time to write it up.
 What I'm curious about is that I believe Site Streams is still in beta
 and not supposed to be used in a production environment according to
 Twitter. Has it been stable for you?

 On Jun 28, 12:24 pm, Mark Krieger markskrie...@gmail.com wrote:
  We've gone live with Site Streams for paying customers of our
  TweetRoost product. I wrote a blog with technical details which some
  people might find interesting. See it athttp://
 www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
  -- it is not a product blog or a pitch :) (and I am a big fan of Site
  Streams, it was a great project for us to implement)
 
  Mark Krieger
  President
  @mediaroost

 --
 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: Twitter Mentions since_id

Hey there Paul,

First, you'll want to change/reset your API keys ASAP -- you should never
post your consumer secret (that signing key) on a public forum.

One thing that may be amiss in your request here is that you're including an
oauth_callback parameter in your header that is not in your signature base
string. In fact, you shouldn't be setting an oauth_callback on any other API
method other than oauth/request_token. This sort of inconsistency can easily
invalidate a request. Make sure to strip this parameter out of your
authorization header.

When you finally get back to your mission, including since_id -- be sure and
add it to your signature base string, and since this is
in lexicographical order and s comes after o, it'll be the last parameter in
your signature base string assuming you don't add any other additional
parameters. You'll also need to include it on the querystring of your
request.

Hope this helps.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jul 6, 2011 at 5:20 AM, Paul jpb@gmail.com wrote:

 This is really frustrating. Thank you Tom, made the changes but no
 effect. Here is everything I pass and get. Im trying to do a GET for
 mentions.

 Whats the problem? :(

 - Generate Base URL -
 base=GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
 %2Fmentions.xmloauth_consumer_key%3D0RaXE4T4CuMFJHI1jViEQ
 %26oauth_nonce%3DDGTQVDPXRAYASJJFJLJF%26oauth_signature_method%3DHMAC-
 SHA1%26oauth_timestamp%3D1309954505%26oauth_token
 %3D298006718-8yTikfcuvQ3Xq1ZGuykhkxK2wY0ZAOxcI0jesRxd%26oauth_version
 %3D1.0
 --
 - Build Signature -
 --
 - Request twit Start -
 postvars=
 url=http://api.twitter.com/1/statuses/mentions.xml
 --
 - Socket Before Header Send -
 GET /1/statuses/mentions.xml HTTP/1.0
 Accept: */*
 Referer: http://eden.fm
 User-Agent: Mozilla/4.0 (compatible; ICS)
 Host: api.twitter.com
 Authorization: OAuth oauth_nonce=DGTQVDPXRAYASJJFJLJF,
 oauth_callback=oob,
 oauth_token=298006718-8yTikfcuvQ3Xq1ZGuykhkxK2wY0ZAOxcI0jesRxd,
 oauth_signature_method=HMAC-SHA1, oauth_timestamp=1309954505,
 oauth_consumer_key=0RaXE4T4CuMFJHI1jViEQ,
 oauth_signature=Q844NOw7T0oq8tNQkdR%2F6ez6Z8s%3D,
 oauth_version=1.0

 --
 - Socket Header End -
 HTTP/1.1 401 Unauthorized
 Date: Wed, 06 Jul 2011 12:16:11 GMT
 Server: hi
 Status: 401 Unauthorized
 WWW-Authenticate: OAuth realm=http://api.twitter.com;
 X-Runtime: 0.00899
 Content-Type: application/xml; charset=utf-8
 Content-Length: 152
 Cache-Control: no-cache, max-age=1800
 Set-Cookie: k=41.133.180.120.1309954571265496; path=/; expires=Wed, 13-
 Jul-11 12:16:11 GMT; domain=.twitter.com
 Set-Cookie: guest_id=v1%3A130995457172572573; domain=.twitter.com;
 path=/; expires=Sat, 06 Jul 2013 00:16:11 GMT
 Set-Cookie: original_referer=ojItV1ByhTzWh74Jc1NQEw%3D%3D; path=/
 Set-Cookie:
 _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCNR9YP8wAToHaWQiJTQzZGVmMTE3YTI5ZjEz
 %250AOGYzZWEwYjlmNTRlM2I3MzA2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
 %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
 dd24ddb28d1207c2ebf479e57b6f9edb82553bbe; domain=.twitter.com; path=/;
 HttpOnly
 Expires: Wed, 06 Jul 2011 12:46:11 GMT
 Vary: Accept-Encoding
 Connection: close

 --
 - Request Done Socket DocEnd -
 result=
 status code=401
 headers=HTTP/1.1 401 Unauthorized
 Date: Wed, 06 Jul 2011 12:16:11 GMT
 Server: hi
 Status: 401 Unauthorized
 WWW-Authenticate: OAuth realm=http://api.twitter.com;
 X-Runtime: 0.00899
 Content-Type: application/xml; charset=utf-8
 Content-Length: 152
 Cache-Control: no-cache, max-age=1800
 Set-Cookie: k=41.133.180.120.1309954571265496; path=/; expires=Wed, 13-
 Jul-11 12:16:11 GMT; domain=.twitter.com
 Set-Cookie: guest_id=v1%3A130995457172572573; domain=.twitter.com;
 path=/; expires=Sat, 06 Jul 2013 00:16:11 GMT
 Set-Cookie: original_referer=ojItV1ByhTzWh74Jc1NQEw%3D%3D; path=/
 Set-Cookie:
 _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCNR9YP8wAToHaWQiJTQzZGVmMTE3YTI5ZjEz
 %250AOGYzZWEwYjlmNTRlM2I3MzA2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
 %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
 dd24ddb28d1207c2ebf479e57b6f9edb82553bbe; domain=.twitter.com; path=/;
 HttpOnly
 Expires: Wed, 06 Jul 2011 12:46:11 GMT
 Vary: Accept-Encoding
 Connection: close

 --
 result=?xml version=1.0 encoding=UTF-8?
 hash
  errorCould not authenticate with OAuth./error
  request/1/statuses/mentions.xml/request
 /hash


 On Jun 10, 9:23 pm, Tom van der Woerdt i...@tvdw.eu wrote:
  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

Re: [twitter-dev] Browser application (AT HOME)

Hi there,

In this scenario, just provide a placeholder URL that represents you. Have
a Google Profile URL? A LinkedIn public profile URL? Anything that's
relevant will do.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 5, 2011 at 11:48 PM, fpmaring fpmar...@gmail.com wrote:

 I have an twitter application which works in any browser. However, it
 is not public. It is in my computer AT HOME. It means 'there is not
 any URL you can go and see it.

 In this sense it is like a desktop application but it runs in a
 browser by using HTML5, CSS, javascript and PHP.

 I know I can register apps at Twitter. But whenever I say it runs in a
 browser twitter ask for the URL which of course does not have any
 sense.

 My question: What can I do ?

 --
 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] http://askobama.twitter.com/

Hi Dean,

We made a blog post yesterday detailing more of the how and what:
http://blog.twitter.com/2011/07/twitter-town-hall.html

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jul 4, 2011 at 1:33 PM, Dean Collins d...@cognation.net wrote:

  Anyone from twitter on this dev-list able to answer questions about
 http://askobama.twitter.com ?

 I’d like to know what format the webinar will take place and how the
 questions/answers will be appearing on twitter/on the askobama website?***
 *

 ** **

 ** **

  

 Cheers,

 Dean

  

  

 ** **

 --
 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] Transfer of api keys

Hi Attila,

To change the owner of your application keys, send an email to
a...@twitter.com from the email address associated with the Twitter account
currently owning the application. In the email indicate the target user
account you would like to become the new owner and the rest will be taken
care of for you, barring any possible issues with the transfer. The transfer
won't effect the keys or access of your users and is pretty seamless.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jul 6, 2011 at 12:25 PM, attila.molnar molnar.attil...@gmail.comwrote:

 Few months ago, I created a developer account on  Twitter, with a pair
 of api key/secret. An application using these keys was built, now it's
 on market, serving users. By the time, I decided to leave the company.
 How can I transfer the api key/secret that is assigned to my developer
 account to an account of someone else from the company? Of course I
 don't want to delete my account, as I don't know what would happen to
 keys, and I don't want to limit the users using our application.

 Please advice.

 Best regards
 Attila

 --
 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] API Bug: Malformed JSON returned for some requests

2011-07-05 Thread Taylor Singletary

Hi Idan,

Thank you very much for your detailed bug report. We're working on
identifying the underlying cause and hope to have a fix out for this next
week.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 5, 2011 at 12:41 AM, Idan Gazit i...@gazit.me wrote:

 *Full bug report is here: https://gist.github.com/1064338*


 Summary:

 The Twitter API returns malformed JSON for some valid requests.

 I discovered this while attempting to fetch all of my list memberships via
 the API. The issue is present regardless of authentication. It occurs 100%
 of the time, and has persisted for over twelve hours. I have reproduced it
 for multiple users.

 Note that the response does not indicate any error condition. The
 transaction completes successfully, but the payload is malformed.

 It seems that any user with enough lists will eventually have a page
 returned containing this bug. I've located it on the first two users I
 tried, which is my own account (@idangazit ~120 listed) and that of Jacob
 Kaplan-Moss (@jacobian, ~500 listed), founder of the Django web framework.

 The offending queries:

 These are two examples:


 http://api.twitter.com/1/idangazit/lists/memberships.json?cursor=1336796671888485791


 http://api.twitter.com/1/jacobian/lists/memberships.json?cursor=1343747472518328819

 Note that these are literally the first two users I inspected. I imagine
 this bug affects anybody with a sufficient number of lists. I have not
 encountered the issue in any other API call, but I haven't looked very hard,
 either.

 All of the following applies to my account, but is equally reproducible for
 @jacobian, albeit with different values.

 Starting with cursor=-1, the following (stable) progression of next_cursor 
 values
 lead to the broken query result:

- 2nd: 1370876429079454131
- 3rd: 1363944001883709517
- 4th: 1352913498669071334
- 5th: 1336796671888485791

 Each of the requests leading up to the offender return well-formed JSON.

 The problem is a superfluous empty value at the very end of the lists
 value, more easily seen on line 956 of the pretty-printed JSON attached to
 this gist. Pasting the JSON into a validity checker like
 http://jsonlint.com handily points out the invalid serialization.

 Interestingly, the developer console in Twitter for Mac munges the response
 to replace the trailing comma with null, thereby making it valid JSON
 (screenshot:http://cl.ly/1q072g380B0P3g213t3e). Regardless, the bytestream
 from the server contains invalid JSON.


 Raw and pretty-printed dumps of the transaction are available in the gist
 linked at the top of this post.


 Thanks!

 Idan (@idangazit)

 --
 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] lists.json API call ignoring the callback parameter as of the last few hours

2011-07-05 Thread Taylor Singletary

Hi Harshad,

We hope to have a fix for this bug out next week, sorry for the
inconvenience in the meantime.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 5, 2011 at 10:44 AM, Harshad RJ harshad...@gmail.com wrote:

 Hi Taylor,

 Any updates on this issue?

 tDash users are not able to read their lists because of this.

 thanks,
 Harshad


 On Sat, Jul 2, 2011 at 12:24 AM, Taylor Singletary 
 taylorsinglet...@twitter.com wrote:

 Thanks everyone, I'll report this to the team -- not quite sure what's
 happening.

 Just to set expectations, I also don't have an ETA on a fix.

 @episod http://twitter.com/intent/user?screen_name=episod - Taylor
 Singletary


  --
 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] Rate limiting questions

2011-07-05 Thread Taylor Singletary

Hi there,

This is actually a different error than your library may be leading you to
believe -- the library is suggesting that the 403 may be due to rate
limiting, but in this case it's actually due to a recent permission model
change.

The permission model gas change whereas requesting a user's direct messages
now requires a re-authorization at the appropriate access request level
(RWD). You can read more about the new permission model and what to do next
here: http://dev.twitter.com/pages/application-permission-model ..

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jul 5, 2011 at 1:35 PM, YupiqDZ mrclea...@gmail.com wrote:

 Hi,

 I'm currently in the process of writing an application which
 periodically gets directed messages from a user (once every 120
 seconds checks if the user has new messages).

 The API I am using is the Twitter4j library in Java. Here's the error
 I get:

 403:The request is understood, but it has been refused.  An
 accompanying error message will explain why.
 TwitterException{exceptionCode=[ece01d6a-01eb72d6], statusCode=403,
 retryAfter=0,
 rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=326,
 hourlyLimit=350, resetTimeInSeconds=1309899, secondsUntilReset=1629,
 resetTime=Tue Jul 05 13:58:10 PDT 2011}, version=2.1.10}

 I am confused as to how my remainingHIts is still 326 yet I am rate
 limited? Additionally, even if I wait until the reset time indicated
 before hitting the service again, I receive the rate limit exception
 again with the reset time pushed back by an hour.

 I am fairly confident that this service does not poll Twitter more
 than 350 times a second, is there something else that could be causing
 me to be rate limited?

 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


-- 
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] Downgrading the permissions on an application

Hi Simon,

1. Yes, your existing tokens with the application will still work when you
make this change.
2. Yes, your existing tokens will continue to have the higher level of
permission that they were originally granted at.

When an end-user does downgrade their token to the read-only flavor, the
strings for the access token will also change.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jul 1, 2011 at 6:35 AM, Simon Cast simon.c...@gmail.com wrote:

 Hi,

 We are looking at reducing the permissions, R/W = R, on our
 application. I have several questions before we attempt this:

 1. Will the existing tokens associated with the application still
 work?
 2. Will the existing tokens still have the higher level of permission?

 Regards,

 Simon

 --
 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: Downgrading the permissions on an application

You would ask your users to re-authenticate and send them through the OAuth
flow again, this time to exchange their RW token for a RO token. By
re-authenticating, they would invalidate the RW token and you would then
consume the new RO token.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jul 1, 2011 at 8:41 AM, Simon Cast simon.c...@gmail.com wrote:

 Hi Taylor,

 Thanks for the info.

 How is it possible for a user to downgrade their token? I know
 applications can be removed but I've never seen the ability to
 downgrade?

 Regards,

 Simon

 On Jul 1, 3:06 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  Hi Simon,
 
  1. Yes, your existing tokens with the application will still work when
 you
  make this change.
  2. Yes, your existing tokens will continue to have the higher level of
  permission that they were originally granted at.
 
  When an end-user does downgrade their token to the read-only flavor,
 the
  strings for the access token will also change.
 
  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary
 
 
 
 
 
 
 
  On Fri, Jul 1, 2011 at 6:35 AM, Simon Cast simon.c...@gmail.com wrote:
   Hi,
 
   We are looking at reducing the permissions, R/W = R, on our
   application. I have several questions before we attempt this:
 
   1. Will the existing tokens associated with the application still
   work?
   2. Will the existing tokens still have the higher level of permission?
 
   Regards,
 
   Simon
 
   --
   Twitter developer documentation and resources:
 https://dev.twitter.com/doc0
   API updates via Twitter:https://twitter.com/twitterapi79
   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: Twitter and Atom. Result type

Do other tweets you post show up in search? This article might help you:
https://support.twitter.com/articles/66018-i-m-missing-from-search

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jul 1, 2011 at 10:18 AM, sri shilpa srishilp...@gmail.com wrote:

 Hi,
  May be your twitter is private so your account tweets are not shown... Or
 else there are no tweets with that has tag



 --
 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] lists.json API call ignoring the callback parameter as of the last few hours

Thanks everyone, I'll report this to the team -- not quite sure what's
happening.

Just to set expectations, I also don't have an ETA on a fix.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jul 1, 2011 at 11:30 AM, Tim Meadowcroft meer...@gmail.com wrote:

 Glad it's not just me then !
 Here's an entire curl request with headers in case that gives any clues (eg
 if it's particular hosts behind a load balancer)

 Cheers

 --
 Tim


  curl -v 
 http://api.twitter.com/1/lists.json?callback=abcscreen_name=schmerg;
 * About to connect() to api.twitter.com port 80 (#0)
 *   Trying 199.59.148.87... connected
 * Connected to api.twitter.com (199.59.148.87) port 80 (#0)
  GET /1/lists.json?callback=abcscreen_name=schmerg HTTP/1.1
  User-Agent: curl/7.21.4 (i686-pc-linux-gnu) libcurl/7.21.4 GnuTLS/2.10.5
 zlib/1.2.5
  Host: api.twitter.com
  Accept: */*
 
  HTTP/1.1 200 OK
  Date: Fri, 01 Jul 2011 18:28:34 GMT
  Server: hi
  Status: 200 OK
  X-Transaction: 1309544914-75829-41020
  X-RateLimit-Limit: 150
  ETag: aab4fa3d9f5ae979ad19a12fa7fcccb0
  X-Frame-Options: SAMEORIGIN
  Last-Modified: Fri, 01 Jul 2011 18:28:34 GMT
  X-RateLimit-Remaining: 145
  X-Runtime: 0.01157
  X-Transaction-Mask: a6183ffa5f8ca943ff1b53b5644ef114a933ec98
  Content-Type: application/json; charset=utf-8
  Content-Length: 100
  Pragma: no-cache
  X-RateLimit-Class: api
  X-Revision: DEV
  Expires: Tue, 31 Mar 1981 05:00:00 GMT
  Cache-Control: no-cache, no-store, must-revalidate, pre-check=0,
 post-check=0
  X-MID: 3e1aeaa17e566ebc8a4c9b2ebcc4f1a1ebb20bbf
  X-RateLimit-Reset: 1309548219
  Set-Cookie: k=78.149.138.182.1309544914102224; path=/; expires=Fri,
 08-Jul-11 18:28:34 GMT; domain=.twitter.com
  Set-Cookie: guest_id=v1%3A130954491410552515; domain=.twitter.com;
 path=/; expires=Mon, 01 Jul 2013 06:28:34 GMT
  Set-Cookie:
 _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCLqc9eYwAToHaWQiJWU5Mjc3MmMzNjVlZTIw%250AYTkxMTZiMGI5NjBkNGIzMWNhIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--fb869e5bba31f66f478b99dc38035752adff4eaa;
 domain=.twitter.com; path=/; HttpOnly
  Vary: Accept-Encoding
  Connection: close
 
 * Closing connection #0
 {lists:[], next_cursor:0, previous_cursor:0, next_cursor_str:0,
 previous_cursor_str:0}

 --
 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: The new permission model (R / RW / RWD) is now in effect

Hi Jeff,

There's no way to specify a RWD option on this method -- if your application
requires the use of direct messages in any context, you must set that at the
application level.

This parameter will only influence the creation of RO or RW tokens.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jul 1, 2011 at 11:42 AM, Jeff Dairiki dair...@dairiki.org wrote:

 To restate my question of yesterday:

 It has been (and is still) possible to set the default access type
 for ones app to Read-only, yet still get read/write tokens by passing
 x_auth_access_type=write to /oauth/request_token.

 Is there a corresponding value for x_auth_access_type which will
 yield a read/write/direct-message token?

 (The docs at http://dev.twitter.com/doc/post/oauth/request_token list
 only the choices 'read' and 'write'.  If there really is no third
 value to be used to request a r/w/dm token, this would seem to me ---
 in light of the recent permission model changes --- to be an
 oversight.)

 I've just filed a ticket on this:

  http://code.google.com/p/twitter-api/issues/detail?id=2258

 Thanks for any help!

 Jeff


-- 
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: ABUIKit / TwUI ?

Hi everyone,

The TwUI kit is now available on github: https://github.com/twitter/twui and
you can read more about it on our engineering blog:
http://engineering.twitter.com/2011/07/starting-today-twitter-is-offering-twui.html

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 23, 2011 at 1:53 PM, Matt Harris thematthar...@twitter.comwrote:

 Thanks for your interest in the library. We hope to have information about
 it released soon. As soon as we do we'll let you know through the mailing
 list and through @twitterapi.

 Best
 @themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
 Developer Advocate, Twitter




 On Sun, Jun 19, 2011 at 1:52 PM, nfarina nfar...@gmail.com wrote:

 *Bump*

 Also, any info about when TwUI will be available? Would love to use it
 in a project I'm working on.


 On Jun 11, 5:21 pm, SM sanja...@gmail.com wrote:
  I wasn't able to attend the announcement regarding ABUIKit /TwUI. Can
  someone provide a summary of what was presented?
 
  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


  --
 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] Application website

As far as the application record creation on dev.twitter.com is concerned,
you can use a placeholder website URL until you have a more permanent home.

Without more information about your development environment, I can't help
you get up and running on your local machine, but ultimately you'll want to
get your PHP and CSS files to be served from a HTTP server running on your
machine, in most cases Apache. If you're using a Mac, you already have
Apache running on your machine and it should be pretty easy for you to find
some documentation on how to execute PHP files from your ~/Sites directory
structure.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 30, 2011 at 5:15 AM, gshadowninja...@hotmail.com 
gshadowninja...@hotmail.com wrote:

 What do i do if i dont have an application website? i registered my
 app already but i dont have an actual application and i cant use it to
 tweet because i dont know how to open the web page because i have no
 addres...its just a folder on my desktop with my php and css files.
 What do i do now? lol

 --
 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] When is permission level enforcement going to happen?

Hi Sean,

We're currently aiming for early to mid afternoon, Pacific Time, barring any
unplanned circumstances. We'll also update @twitterapi and both the
-announce and -talk mailing lists as we roll out.

Thanks!
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 30, 2011 at 6:57 AM, Sean Heber s...@spiffytech.com wrote:

 I know the date for this is today (June 30), but is it something that will
 be rolling out slowly throughout the day starting sometime soon, or is it
 going live at the *end* of today or how is that working? I don't recall
 seeing the details mentioned previously.

 I'd like to get an idea of when I should start the pot of coffee that will
 be necessary to deal with the inevitable tech support flood...

 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] Re: The new permission model (R / RW / RWD) is now in effect

Additionally, newly generated tokens with the  My Access Token feature on
dev.twitter.com will now return an access token at the same level of access
your application requests.

If you used My Access Token to generate your token in the past, you'll
want to first go to http://twitter.com/settings/applications to revoke your
access token's permissions and then go back to dev.twitter.com's My Access
Token feature to re-negotiate an upgraded token.

Any token that transitions from one state to another will have the string
representation of the access token and secret changed: If a token goes from
RO to RW, the strings will change. If a token goes from RW to RWD, the
strings will change. If a user revokes a token and you then renegotiate the
token, even if the permission level didn't change, the strings will change.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com wrote:

 Hey Chris,

 The new permission model applies to all access tokens, including the
 application owner's one. You have to reauthorize your existing access_token
 through the OAuth Flow, just like any other user.

 Arnaud / @rno http://twitter.com/rno



 On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com wrote:

 I assumed that the new permissions would not apply to an app reading
 it's own DMs. ie: When authenticating with an apps own token and
 secret /1/direct_messages.{format} should not enforce the R/W/DM
 policy.

 Appears this is not the case?

 On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
  Hey Developers,
 
  As planned, the new three-tier permission model is now officially in
 effect.
  Please remember that you don't have to make any changes if your
 application
  or service doesn't need to read or delete Direct Messages.
 
  Key points:
  - Existing oauth_tokens have not (and will not) be invalidated, even if
 you
  update your application permission level.
  - Read/Write and Read tokens are now unable to read and delete Direct
  Messages. If you wish to read or delete a user's Direct Messages, you
 need
  to update your application and have your existing access tokens
 reauthorized
  through the OAuth authorize web flow.
  - All authenticated API requests return an X-Access-Level header, so
 you
  can find out the current permission level of the access token you're
 using
  (read, read-write, or read-write-directmessages).
 
  For more information, be sure to take a look on:
  - The Application Permission Model documentation page:
 http://t.co/elH0KY4
  - The Application Permission Model FAQ:http://t.co/1Wliqg4
 
  Thanks again for working with us on this new permission level,
  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


  --
 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: The new permission model (R / RW / RWD) is now in effect

Hi Chris,

With the one exception of Site Streams' authorization pattern, there is no
special relationship between the account owner of an application and the
application itself -- you are just a user of your application, same as any
other user. I'm sorry that wasn't clear.

You have a few options in this scenario and I'm sure one of them will be
right for you.

* Option 1: Create a side-car application record for the purpose of reading
and responding to DMs. Set your permission level on this app to RWD. Issue
your own access token. Use this consumer key and secret for the portion of
your application that needs to read/write DMs. You would code your
application to use the appropriate set of keys for the appropriate
situation. This separates concerns and would have other benefits. If your
app tweets on its own behalf, you'd want to use your primary API keys so
that you're attributed the way you like. When creating an app for this
purpose, be sure and clearly label its intent and purpose.

* Option 2: There's a feature we've added to the OAuth flow that allows you
to specify the level of permissions you are asking for at the time of the
request. In this scenario, you would set your application to RWD but
explicitly request your end-users to receive only RW tokens by passing the
parameter x_auth_access_type=write to
api.twitter.com/oauth/request_tokenon the first step of the OAuth song
and dance. When negotiating your own
token, you'll ask for a RWD but for all end-user tokens, only RW. You leave
your application at the RWD level. More details on this option are at
http://dev.twitter.com/doc/post/oauth/request_token

Either of these options seem suitable for your scenario, with the first
option likely being your quickest solution and also the most preferable.
Unless you have a requirement to share access tokens between arms of the
application, it's a great approach for separating concerns in an app.

Let me know if you have any questions on this.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 30, 2011 at 12:27 PM, Chris Teso christ...@gmail.com wrote:

 Arnaud  Taylor,

 Thanks for the response. I must say that I'm confused as to why the
 decision was made to block ones own app from reading their own DMs?
 Can you elaborate on the logic behind this decision?

 It seems logical that I would not have to re-authorize my own app
 tokens to view my own DMs. Further, I do not want to change my apps
 permission levels to do so. This effects ALL of our customers solely
 so I can read my own apps DMs! If I follow Taylors suggested new token
 request, can I then revert my apps permissions and still access my
 apps own dms? ie: I DEFINITELY do not want to keep my app permissions
 set to R/W/DM when I don't need to access any customer DM data.

 Thanks,
 Chris


 On Jun 30, 12:17 pm, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  Additionally, newly generated tokens with the  My Access Token feature
 on
  dev.twitter.com will now return an access token at the same level of
 access
  your application requests.
 
  If you used My Access Token to generate your token in the past, you'll
  want to first go tohttp://twitter.com/settings/applicationsto revoke
 your
  access token's permissions and then go back to dev.twitter.com's My
 Access
  Token feature to re-negotiate an upgraded token.
 
  Any token that transitions from one state to another will have the string
  representation of the access token and secret changed: If a token goes
 from
  RO to RW, the strings will change. If a token goes from RW to RWD, the
  strings will change. If a user revokes a token and you then renegotiate
 the
  token, even if the permission level didn't change, the strings will
 change.
 
  Thanks,
  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary
 
 
 
 
 
 
 
  On Thu, Jun 30, 2011 at 12:11 PM, Arnaud Meunier arn...@twitter.com
 wrote:
   Hey Chris,
 
   The new permission model applies to all access tokens, including the
   application owner's one. You have to reauthorize your existing
 access_token
   through the OAuth Flow, just like any other user.
 
   Arnaud / @rno http://twitter.com/rno
 
   On Thu, Jun 30, 2011 at 11:56 AM, Chris Teso christ...@gmail.com
 wrote:
 
   I assumed that the new permissions would not apply to an app reading
   it's own DMs. ie: When authenticating with an apps own token and
   secret /1/direct_messages.{format} should not enforce the R/W/DM
   policy.
 
   Appears this is not the case?
 
   On Jun 30, 11:39 am, Arnaud Meunier arn...@twitter.com wrote:
Hey Developers,
 
As planned, the new three-tier permission model is now officially in
   effect.
Please remember that you don't have to make any changes if your
   application
or service doesn't need to read or delete Direct Messages.
 
Key points:
- Existing oauth_tokens have not (and will not) be invalidated, even
 if
   you
update

Re: [twitter-dev] Re: Introducing the Follow Button

2011-06-29 Thread Taylor Singletary

Hi Pankaj,

That feature is unavailable for the Follow Button -- in general, the Follow
Button will tell you little to nothing about the end-user -- only the
factual interactions they took while engaging with the button and subsequent
intent flow are available.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 29, 2011 at 6:36 AM, Pankaj Rohankar
pankaj.rohan...@gmail.comwrote:

 Hi,
 As I told I am using Twitter Follow Button and my question is,
 How we can detect that logged in user is already following that  twitter id
 or not ?

 On Fri, Jun 24, 2011 at 5:58 AM, Matt Harris thematthar...@twitter.comwrote:

 Hi David,

 Glad to hear this is working for you now. For the benefit of everyone else
 this issue was identified and resolved in the last few days.

 Best,
 @themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
 Developer Advocate, Twitter




 On Thu, Jun 23, 2011 at 9:07 AM, David Huang linshunghu...@gmail.comwrote:

 Seems like my issue was fixed during maintenance..
 http://status.twitter.com/post/6816501955/follow-button-off-line

 Thanks,
 David

 On Jun 15, 11:06 am, David Huang linshunghu...@gmail.com wrote:
  Hi all,
 
  I was testing the new Follow button on my webpage and noticed that
  one-click only works when the user have signed in to Twitter during
  the same browsing session. If I relaunched the browser, even though
  I'm still logged in to Twitter, clicking the Follow button would open
  a popup. Am I missing anything, or is this the expected behavior?
 
  Thanks,
  David
 
  On May 31, 1:07 pm, Arnaud Meunier arn...@twitter.com wrote:
 
 
 
 
 
 
 
   Hey developers,
 
   Today we're launching theFollowButton!  Similar to the Tweet Button,
   it's a new widget that lets users easilyfollowa Twitter account from
   any web page. TheFollowButton has a single clickfollowexperience,
   simple implementation model, and is configurable to fit the needs of
   your website.
 
   Read our announcement on the Twitter blog, and use the resources
 below
   to set up your ownFollowButton:
 
   - Create aFollowButton here:
 http://twitter.com/about/resources/followbutton
   - Detailed documentation:http://dev.twitter.com/pages/follow_button
 
   We’ve also added a Javascript layer to our Buttons and Web Intents
   that makes it possible for you to detect how users are interacting
   with these tools, and to hook them up to your own web analytics. More
   details on:http://dev.twitter.com/pages/intents-events
 
   We're excited to see how you guys will implement theFollowButton.
   Let us know what you think, or if you have any questions.
 
   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


  --
 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




 --
 Thanks  Regards.

 Pankaj Rohankar.
 Mob ( WWP++.PG.P )

 --
 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 register new app

2011-06-29 Thread Taylor Singletary

Thanks for the bug report.

Where are you located that you can't view the CAPTCHA? Are there any
Javascript errors on the page when this happens? Are you viewing over SSL or
without?

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 29, 2011 at 9:54 AM, vbose vigil.b...@gmail.com wrote:

 We are unable to register new app using https://dev.twitter.com/apps/new#
 web site because the captcha is not visible to us. Multiple folks
 tried from different location within the city without success. We
 tried using Firefox 5.0, Chrome and IE 8.0.

 --
 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 can I determine user_id having access token?

2011-06-29 Thread Taylor Singletary

While one should consider the access token strings as opaque identifiers, at
least as far as the present day is concerned, our access tokens have a
format 1234-xyzxyzxyz -- the 1234 part before the dash is the user_id of
the Twitter user the access token represents.

Calling account/verify_credentials without parameters using the access token
will be a more canonical way to get the user_id. If it doesn't return data
for you, either the user no longer has granted your app permission or
there's something amiss with your OAuth signing.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 29, 2011 at 3:34 PM, Evgeny yaid...@gmail.com wrote:

 Hi!

 On my site users have ability to interact with Twitter. For this I
 stored only access token  secret, not user_id. But now I want to know
 user_id in Twitter for this users. How can I get it right way?

 I tried request users/show without params, signed with users's token -
 received error:Not found; tried statuses/user_timeline without
 params just to get user_id from post data, it works, but there are
 some users with zero posts.

 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


-- 
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] Query based on the number of followers

2011-06-28 Thread Taylor Singletary

Hi Venu,

There aren't any API methods that return this kind of ranked information
provided by Twitter.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jun 28, 2011 at 5:41 AM, Venu ven...@gmail.com wrote:

 Is it possible to get a list of all Twitter Users who have more than
 2000 followers (or some number) with an API or any other easy way?

 I have been doing a lot of research from a long time but could not
 find a easy answer.

 Really appreciate if some one can throw a hint!

 --
 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] Is there api for invite friend?????????????

2011-06-28 Thread Taylor Singletary

There's nothing explicit like the function Facebook has. Instead, you could
encourage the user to craft a tweet @mentioning their friend that they would
recommend the product to and instead of your app sending the invite the
user would send the invite from their own account.

The Tweet Button/Tweet Web Intent are great for this purpose as it allows
you to pre-prepare the text and the user still retains control over the
message they actually send. The Tweet Button is documented here:
http://dev.twitter.com/pages/tweet_button and the Tweet Web Intent can be
read about here: http://dev.twitter.com/pages/intents#tweet-intent

If you have/want or more rich Twitter API integration, you could use the API
to accomplish this instead.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jun 28, 2011 at 5:16 AM, Pravin Mishra 
pravin.mis...@startupsourcing.com wrote:

 Hi Everyone,

 Hoping you guy's doing there.

 It is my first mail and i am newbie in this google mail  group. Might
 be my question is silly OR obvious , But i am not able to figure
 out my problem. I want to add invite friend in my RUBY ON RAILS
 project like facebook(http://developers.facebook.com/docs/reference/
 dialogs/requests/).

 Is it possible on twitter.???
 if yes then give me like of API.

 I am aware about Follow Button and tweetbutton API. But i want
 some improvement in tweetbutton API.
 There should be selection button for select followers to whom my tweet
 will visible.

 IF it possible then, how will i achieve this.

 any suggestion will be appreciated .

 Thanks for giving your great time.


 +
 Pravin Mishra

 --
 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] Stream API and OAuth

2011-06-28 Thread Taylor Singletary

The parts of the Streaming API on stream.twitter.com support both
three-legged OAuth (an access token is required for the account attempting
to connect) or basic auth (username and password). Other parts of the
Streaming API like User Streams and Site Streams are OAuth-only.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jun 28, 2011 at 12:03 AM, Tudor Claudiu Florea 
tudor.claudiu.flo...@gmail.com wrote:

 Twitter Stream API supports OAuth login now and no username and
 password?

 --
 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-dev] Re: 401 Unauthorized in Python/Twisted app

2011-06-27 Thread Taylor Singletary

Hi Eryn,

I'm not too familiar with the Twisted framework or its implementation
of OAuth, so take what I recommend with a grain of salt.

* Access tokens generated through the OAuth flow on Twitter,
regardless of the technique used (PIN code, xAuth, vanilla OAuth) are
long-lived and do not expire until the end-user makes an explicit
effort to revoke the access. You store the access token and access
token secret.

* While OAuth in theory should just work when it works in one spot,
there's a great amount of variation in the amount of wrongness that
given services will tolerate when evaluating the credentials. Long-
term, we're working to normalize the entire validation procedure
across all of our services, but in reality the streaming API and the
REST API use different OAuth engines to evaluate the validity of the
request -- the streaming API's OAuth verification is considerably
stricter than the REST API's more forgiving implementation.

* I notice that your authorization header is missing a oauth_timestamp
parameter -- is that a copy and paste error? Do you know how to locate
the OAuth signature base string in the Python library you are using --
it can often be buried under private or protected methods but the
string is invaluable in debugging issues like this.

Thanks,
Taylor

On Jun 24, 7:54 pm, Eryn Wells e...@3b518c.com wrote:
 Hello all,

 I'm quite new to OAuth and the Twitter API, and this is my first post to this 
 list.

 I'm working on an app in Python using the Twisted framework. It uses 
 brosner's fork of python-oauth2[1] to do the initial authentication and 
 subsequent request signing. I'm using the PIN code flow for authentication. 
 Do access tokens need to be generated every time you start the app, or can 
 they be stored between runs and reused? If so, how long are the valid? Right 
 now, my code writes the access token and secret out to a file and recovers it 
 the next time it starts. The procedure seems to go just fine – I don't get 
 any errors – but I can't really verify that everything is Correct because I 
 don't really know what I'm looking for…

 Second thing, I'm at the point where I'm trying to do the initial connection 
 tohttps://userstream.twitter.com/2/user.json. I'm using SSLConnect and 
 web.HTTPClient, if that helps… I write out the command (GET url), and the 
 headers (a Host and an Authorization header). The OAuth library generates the 
 following Authorization header content. I get back a 401 Unauthorized error 
 with a WWW-Authenticate: Basic header. I've heard from @twitterapi that User 
 Streams require OAuth, so why am I getting a Basic auth response?

 OAuth realm=Firehose, oauth_nonce=25622603816219309853125867384777, 
 oauth_consumer_key=cut, oauth_signature_method=HMAC-SHA1, 
 oauth_version=1.0, oauth_token=cut, 
 oauth_signature=1AV5YG4DsfCV4jDoQcOCOmxZ2Gw%3D

 Anything obvious there that I'm doing wrong?

 Thanks,
 Eryn

-- 
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 API / People Search API not returning anything

2011-06-27 Thread Taylor Singletary

Hi Ruben,

We're looking into this issue and hope to have it resolved soon. Thanks for
the report.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 27, 2011 at 9:51 AM, RubenOrozco ruben.oro...@gmail.com wrote:

 Hi Twitter Devs. http://api.twitter.com/1/users/search

 When people search Tweetfind.com , they get a searched box at the
 bottom(Twitter Find People), For a few weeks it was working. You were able
 to scroll down and it would load more Twitter Profiles.  A week or two ago,
 it stopped.

 The programmer that is helping me said this:
 *--*
 For People Search API: http://api.twitter.com/1/users/search
 http://api.twitter.com/1/**users/searchhttp://api.twitter.com/1/users/search
 .*json?q=basketballpage=1 is returning results while *
 http://api.twitter.com/1/**users/searchhttp://api.twitter.com/1/users/search
 .*json?q=basketballpage=2 is not returning anything from twitter API.

 Is there any problem with page 2 ?**
 --
 *

 --
 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] xAuth login

2011-06-24 Thread Taylor Singletary

Hi Sushil,

Twitter enforces that timestamps be within a reasonable amount of time from
the present, so this is expected behavior.

One way that you can get plan ahead for this is by reading the Date HTTP
header that is sent in the response to every request -- once you parse that
date, you can determine the delta between what our server clock is running
at and what time your device thinks it is and then adjust your timestamp
calculations accordingly.

Another strategy that some developers take is to issue an unauthenticated
HTTP HEAD request to https://api.twitter.com/1/help/test.json when the app
starts up, which will also yield the Date header that you can adjust to.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 23, 2011 at 11:36 PM, Sushil sushil.sys...@gmail.com wrote:

 Hi All,

 I have a Android application for Twitter. I'm using Twitter4j library
 to do xAuth authentication.

 I'm facing a problem during login if the device date set as any past
 date. Like if today is 24th June and device date set as 23rd June and
 when I'm trying to login it gives me following error.

 SNS exception :: The screen name / password combination seems to be
 invalid.Relevant discussions can be on the Internet at:
 http://www.google.co.jp/search?q=e07c50ee or
 http://www.google.co.jp/search?q=e7bd
 TwitterException{exceptionCode=[e07c50ee-e7bd 1ac06e3f-695622d6],
 statusCode=503, retryAfter=0, rateLimitStatus=null, version=2.1.12}

 But if the device date is current date then the authentication works
 just fine.

 I want to know if this is expected behavior ?


 Thanks,
 Sushil

 --
 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: Switching Application Type to Browser

2011-06-24 Thread Taylor Singletary

Changing your application type has no effect on existing access tokens. If a
key has the xAuth permission granted to it, xAuth can be performed using the
API key regardless of the setting for application type. Applications set to
desktop cannot  dynamically present a oauth_callback on the request token
step (unless the value of oauth_callback is equal to oob for PIN-code
out-of-band OAuth), while apps set to client have the ability to
dynamically set an oauth_callback as they see fit. When saving an
application in client mode, one must provide a placeholder callback URL
even though it's a best practice (and valid OAuth) to set the oauth_callback
explicitly.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jun 24, 2011 at 9:00 AM, Andrew W. Donoho
andrew.don...@gmail.comwrote:


 On Jun 23, 2011, at 20:14 , Victoria wrote:

  If I change Application Type to Browser (on the
 https://dev.twitter.com/apps/edit/
  page), will this negatively affect the xAuth process currently used in
  the production version of my Twitter client?



 Victoria,



Only Twitter or an experiment with an xAuth enabled application can
 answer this question. It could go either way. That said, I expect that the
 authorization paths, due to the different routes, are independent for xAuth
 and the OAuth path. (I believe the app type is really a choice between
 three-legged browser OAuth and PIN OAuth.)

Twitter folks need to answer this question.

Good luck.



 Anon,
 Andrew
 
 Andrew W. Donoho
 Donoho Design Group, L.L.C.
 a...@ddg.com, +1 (512) 750-7596, twitter.com/adonoho

 Knowing is not enough; we must apply.
Willing is not enough; we must do.
-- Johann Wolfgang von Goethe




 --
 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] Streaming API with start_date and end_date

2011-06-23 Thread Taylor Singletary

This is not within the scope of the real-time streaming API which serves the
purpose of streaming tweets  related events as they happen with very
limited support for any kind of rewind behavior.

On Thu, Jun 23, 2011 at 9:42 AM, Trevor Dean trevord...@gmail.com wrote:

 This would be a great feature, any word on this yet?

 Trevor Dean | Director
 big time design  communication Inc.
 647 234 8198

 Visit http://www.bigtimedesign.ca for more information

 On 2011-06-23, at 7:13 AM, JackRabbit yacobus.reinh...@gmail.com wrote:

  Hi Guys,
 
  is it possible to query streaming api with filter and include
  start_date and end_date, so that developer can track or filter by date
  range? If yes, that could be awesome, if no, would you mind please to
  add this feature?
 
  Why it is needed because it would be great if we can track keyword
  from previous date where we have missed the tweets. For event
  organizer and finance reports application like us, this feature is
  very valuable.
 
  Many Thanks,
  Jack
 
  --
  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] Does twitter offer any hook to register a click on the tweet button iframe?

2011-06-22 Thread Taylor Singletary

While we don't necessarily offer click tracking from within the IFRAME, we
do have a set of hooks for the Tweet Button (and Follow Button and Web
Intents) that will likely give you the tools to accomplish this:
http://dev.twitter.com/pages/intents-events

You can track the clicks on the Tweet Button itself (and both of its
regions) as well as the completion/conversion of the intended actions that
occur within the popup (like when tweets are tweeted and related accounts
are followed).

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 22, 2011 at 3:09 PM, Drew alam...@gmail.com wrote:

 We have all kinds of click events on our pages to figure out how
 people are interacting with our page. ie. someone clicks a tab here,
 or a like button there, etc.

 Since clicks on an iframe can't be accessed, other companies like
 Facebook offer a hook into it:

 FB.Event.subscribe('edge.create', function(response){
   //do tracking ping
 })

 Does Twitter offer something similar? If not, why not?

 --
 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] Brand Confusion

Hi Jerry,

I think you're looking for this form for reporting brand/trademark issues:
https://support.twitter.com/forms/trademark

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 20, 2011 at 7:06 PM, Jerry Thompson jerrycando...@gmail.comwrote:

 Who's the best person to reach out to at Twitter if there is a twitter
 account that is causing confusion with our brand and users?

 --
 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] 500 errors from the search api on specific queries, related to geocode parameter.

Hi Eric,

For now you should be able to overcome this issue by requesting a much
smaller amount of results per page -- you might find a sweeter spot with
some of these queries at 20 to 40 rpp -- it's simply timing out building a
result set for you at that quantity.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 20, 2011 at 8:34 AM, Eric Mueller nevin...@gmail.com wrote:

 I noticed some 500 responses to our search api requests this morning that
 were oddly consistent - specific queries that would always error, when most
 queries never (rarely) do.

 I started trying to reproduce with smaller queries, and arrived at a few
 examples.

 This search fails with a 500 error:

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.75,-84.37,12.35mi
 It probably should be returning an empty results list (notice the 12 mile
 radius).

 The same search with the decimals chopped off the latitude woks fine (empty
 results as expected):

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33,-84.77,12.35mi

 Removing the decimals from the longitude instead doesn't work:

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.25,-84,12.35mi

 *Changing* the value of the decimal digits on the latitude sometimes works,
 and sometimes doesn't:

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84,12.35mi

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.44,-84,12.35mi

 Changing the value of the decimal digits on the longitude doesn't seem to
 produce failures no matter what I put in.

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.99,12.35mi

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.01,12.35mihttp://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.99,12.35mi

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.44,12.35mihttp://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=bieber%20OR%20jersey%20shore%20OR%20younggeocode=33.01,-84.99,12.35mi


 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=biebergeocode=33.44,-84.99,12.35mi
  fails,
 but

 http://search.twitter.com/search.json?rpp=100lang=enresult_type=recentgeocode=33.44,-84.99,12.35mihttp://search.twitter.com/search.json?rpp=100lang=enresult_type=recentq=palingeocode=33.44,-84.99,12.35mi
  (geocode
 only) works fine.

 I tested a few of these without rpp, lang, and result_type params with
 identical results, so you can probably disregard those.

 These aren't random failures - every time I try one of the failing queries,
 it continues to fail (though that may change as the result set changes over
 time).
 Are there any known bugs with the geocode handling in the search api?

 - Eric


  --
 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: User Search API

We're looking into this, thanks for the report.

On Tue, Jun 21, 2011 at 11:07 AM, Amit Debnath amitdebnath...@gmail.comwrote:

 Thanks for answering. Now I know it isn't something I did.

 Doesn't look like a bug. The in-site search is now also limited to 20
 results. Waiting for somebody 
 **http://www.google.co.in/search?hl=enclient=firefox-arls=org.mozilla:en-US:officialsa=Xei=fd0AToufO8WIrAe65qH8DAved=0CCQQvwUoAQq=knowledgeablespell=1to
 shed some light on this.

 Thanks,
 Amit

  --
 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] I cannot see CAPTCHA image in the Register Application page.

Are you still seeing this behavior? If so, what geographic region are you
located in? I notice you tried in several browsers but I still feel
compelled to ask: do you have any plugins or browser extensions in those
browsers that may be preventing the content from displaying?

We're unable to reproduce this at the moment.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 20, 2011 at 4:28 PM, HBPark kra...@gmail.com wrote:

 I am trying to register a new application at
 https://dev.twitter.com/apps/new.
 But the CAPTCHA image is not seen in my browser.
 I have tried with Chrome, IE6, IE7, FF4...

 What should I do?

 --
 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] Recipe for getting Follow button working on an https website?

2011-06-20 Thread Taylor Singletary

Hi Rob,

The Follow Button doesn't yet support SSL -- only unencrypted HTTP, which is
why you get this error when trying to use the Follow Button on a SSL-based
site. We'll let everyone know when SSL support arrives for the Follow Button
and Tweet Button.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Fri, Jun 17, 2011 at 9:32 AM, Rob robert.osbo...@gmail.com wrote:

 I'm trying to add a follow or tweet button to a site that uses https
 by default.

 My choices appear to be scare my users with a insecure content on
 page or, if I change the url to https://platform.twitter.com/, an
 invalid certificate error.

 Is there an easy recipe for this?  Google reveals hacks like copy
 everything local.

 Why doesn't https://platform.twitter.com/ have a valid certificate?

 --
 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 Single User Login

2011-06-20 Thread Taylor Singletary

If this is for an iPhone app, it's likely you don't need to deal with the
streaming API or the complexity of authentication at all.

Occasional unauthenticated requests to a specific public user's timeline is
probably most appropriate in this case.

For instance, to get the ~5 most recent tweets and retweets by the musician
Mike Doughty just issue a HTTP GET request:

GET
http://api.twitter.com/1/statuses/user_timeline.json?count=5include_entities=trueinclude_rts=truescreen_name=Mike_Doughty_

Keep in mind that our count parameters are really up to parameters, and
you may get less than the specified count back. Unauthenticated requests are
limited to 150 per hour per IP address, so you'll want to stay conservative
with these requests in an unauthenticated context.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 20, 2011 at 2:13 PM, Greg Passmore gregp...@gmail.com wrote:

 Look at the User Streams api or the Search API. You just need to use the
 API to ask twitter for the timeline / stream of the band user you want.



 On Mon, Jun 20, 2011 at 2:05 PM, mediavu dsh.operati...@gmail.com wrote:

 Hi I need to be able to automatically log my user into a twitter
 account so that they are presented tweets from a certain music band.
 Is there a way to disable the user name ane password process and embed
 it into my iphone app.

 So in theory the user clicks a button which displays the music bands'
 twitter account. They are not logging into their own account as such
 but receiving tweets every time the band posts a tweet.

 Cheers
 mediavu

 --
 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: error 401 from oauth, starting a few days ago

2011-06-16 Thread Taylor Singletary

Hi Arlo,

A few minor points here:
  - What type of perms do you have set for your API key: RO, RW, or RW+DM?
  - The my access token feature can only yield RO and RW tokens. If you've
set your app to RW+DM, you'll get a different kind of token when walking
through the OAuth web-flow than you get for the my access token flow (which
may explain why you'll see the differing values)

Most importantly:
  - You aren't accessing valid API URLs.
https://api.twitter.com/statuses/user_timeline.xml should have a version:
https://api.twitter.com/*1*/statuses/user_timeline.xml
  - Your authorization header contains your oauth_token_secret -- which
should be kept secret and not included in your request. oauth_token_secret
is only used as part of the signing process, it's not a value that you'll
ever need to send to the API.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 16, 2011 at 9:40 AM, arlomedia a...@arlomedia.com wrote:

 Thanks for the reply. On one website, I'm accessing the timeline for a
 protected account; on the other website, the account is not protected.
 For both, I'm using this URL:
 https://api.twitter.com/statuses/user_timeline.xml.
 Both stopped working last week.

 The oauth example script I posted above requests the oauth token and
 secret from the account, then passes it back with the request (you can
 see that by checking the $params value before the request). In my own
 script, I simply have the token and secret saved in constants and then
 I pass them from there. Neither approach is working for me now. I did
 notice that the token and secret returned by the request_token API
 call are different from the token and secret that I see displayed on
 the my_token page in my Twitter account (https://dev.twitter.com/apps/
 nn/my_token), and the values returned from the API are different
 every time. Does that tell us anything?

 Here's what my request_token request looks like:

 POST https://api.twitter.com/oauth/request_token
 Authorization: OAuth realm=, oauth_signature_method=HMAC-SHA1,
 oauth_signature=[27 characters]%3D, oauth_nonce=[13 characters],
 oauth_timestamp=1308241110, oauth_token=,
 oauth_consumer_key=[consumer key], oauth_version=1.0
 Content-Type: application/x-www-form-urlencoded

 This returns values for oauth_token, oauth_token_secret and
 oauth_callback_confirmed (but the token values don't match what I see
 in my account).

 Here's what my user_timeline request looks like:

 GET https://api.twitter.com/statuses/user_timeline.xml
 Authorization: OAuth realm=, oauth_token=[oauth token],
 oauth_token_secret=[oauth token secret],
 oauth_signature_method=HMAC-SHA1, oauth_signature=[27 characters]
 %3D, oauth_nonce=[13 characters], oauth_timestamp=1308241629,
 oauth_consumer_key=[consumer key], oauth_version=1.0

 This returns the 401 error whether I send the token values returned by
 request_token or the token values I got from my account.

 --
 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: Problem With Fetching Followers and Following Id's

When using cursors, you cannot specify a count parameter. If you want to
limit the results that you get back, simply truncate the response to the
number of ids that suits you. You can pre-prepare paginated results by first
building the complete set and then building a UI that will navigate between
the already fetched data.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 2:26 AM, kamesh SmartDude 
kamesh.smartd...@gmail.com wrote:

 to whom should we write for this particular issue

 //kamesh

 On Jun 14, 12:26 pm, Georgooty varghese georgo...@gmail.com wrote:
  I am facing the same issue..
 
  On Tue, Jun 14, 2011 at 11:56 AM, kamesh SmartDude 
 
 
 
 
 
 
 
  kamesh.smartd...@gmail.com wrote:
   Is Anybody have IDEA about the solution of above problem
 
   //kamesh
 
   On Jun 13, 12:49 pm, kamesh SmartDude kamesh.smartd...@gmail.com
   wrote:
Dear All,
 
I am developing a twitter mobile application, and i have a problem in
fetching the followers and following list.
 
earlier i used
 
  http://api.twitter.com/version/statuses/friends.formathttp://api.twit.
 ..
 
API's to fecth the Followers and following people list. But now they
are depricated.
 
Now i want to use the API's
 
  http://api.twitter.com/version/friends/ids.formathttp://api.twitter.c.
 ..
 
to fetch the ID's of the follower and following people Id's and
 
   http://api.twitter.com/version/users/lookup.formatAPI to get the
user List.
 
Now My problem is that i want to fetch the Specific number (as per my
requirement it is 16) of follower and following id's using the above
two API's (friends/ids.format and followers/ids.format).
 
But these two API's ignoring the count Parameter (suppose if i sent
a request to fetch the followers of the user = sachin_rt
 
   
 http://api.twitter.com/1/followers/ids.json/screen_name=sachin_rtcur...
 
it is ignoring the count parameterand returning an amount 5000
followers ID's.
)
 
and returning a huge number of Id's. As i am developing a mobile app
 i
don't want to store this amount of data in my database until user go
for showmore/ or scroll to the bottom of the list.
 
please let me know is there any solution to fetch the specific number
of ID's of the followers/follwing.
 
Thanks in AdvanceKamesh
 
   --
   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: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine

If you want to retrieve all of a user's followers, you first get their ids
by cursoring through
http://api.twitter.com/1/followers/ids.json?cursor=-1[1] -- after
retrieving that data, you'll want to expand them for user ids
into hydrated user objects. To do this, pass 50 to 80 (maximum 100, but I
recommend lower maximums for best performance) of the ids at a time to the
bulk users lookup [2] API method. For some users this may take only two API
requests: one for the followers' ids, and another for the users/lookup.

[1] http://dev.twitter.com/doc/get/followers/ids
[2] http://dev.twitter.com/doc/get/users/lookup

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 4:34 AM, Amit Battan Ror batta...@gmail.com wrote:

 one more issue /... as I want to get the list of my all follower
 But I seen in some discussion as this API not return all the friends.
 It only return the recently updated friends with there status.
 Is it?
 and what is the API which I want?



 On Jun 14, 5:04 pm, Bill Jacobson gabe...@gmail.com wrote:
  Amit,
 
  Your endpoint is obsolete and no longer supported by Twitter. That's why
  you got the 403. Statuses/followers will succeed if you change it
 tohttp://api.twitter.com/1/statuses/followers.xml
  https://api.twitter.com/1/statuses/followers.xml
 
  BUT this API is deprecated. Read all about it here:
 http://dev.twitter.com/doc/get/statuses/followers
 
  Bill
 
  On 06/14/2011 12:38 AM, Amit Battan Ror wrote:
 
 
 
 
 
 
 
   Bill
 
   Working fine :https://twitter.com/statuses/friends_timeline.xml
 
   Not Working Giving 403 Error :
 https://twitter.com/statuses/followers.xml
 
   On Jun 14, 10:14 am, Amit Battan Rorbatta...@gmail.com  wrote:
   Thanks Bill
 
   I will check and try to track URL ..
 
   On Jun 13, 9:07 pm, Bill Jacobsongabe...@gmail.com  wrote:
 
   Amit, also seehttp://
 www.mailinglistarchive.com/html/twitter-development-talk@googl
   That's what helped me.
   -Bill
   On 06/13/2011 10:44 AM, Bill Jacobson wrote:
   I'm suggesting that you find out what endpoint (Twitter URL) your
 app
   is targeting, and make sure that it matches what is currently
   documented. If it doesn't match, correct it. That's what worked for
 me.
   On 06/13/2011 08:05 AM, Amit Battan Ror wrote:
   I am not getting the solution.
   and my API was working fine beofre 2 3 days..
   but not now..
   all other API except getFollowersIncludingCurrentStatus working ok
 and
   return proper output
   On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.comwrote:
   Amit,
   I don't know your library, but in my case the 403 was accompanied
 by
   the
   message Not authorized to use this endpoint and the solution was
 to
   update to http://api.twitter.com/1[etc.];.
   Bill Jacobson
   On 06/13/2011 05:39 AM, Amit Battan Ror wrote:
   any idea guys
   On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.com
  wrote:
   Hi All
   I am using
   Twitter-OAuth-iPhonehttps://
 github.com/bengottlieb/Twitter-OAuth-iPhone
   I am calling [twitterObj getFollowersIncludingCurrentStatus:NO]
 for
   getting my friend list which was working fine. But from last two
 days
   its giving me the 403 error.
   -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed
 with
   error: Error Domain=HTTP Code=403 The operation couldn t be
   completed. (HTTP error 403.)
   As twitter api wiki 403 is due to crossing the limit of updates
   and DM
   but here in getFollowersIncludingCurrentStatus Why this error
   occurring and even list is not comes next day giving same 403
 error.
   Thanks
   Amit Battan

 --
 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] Method /version/followers/ids.json not functioning properly when cursor parameter is provided

This means that your signing is slightly wrong (and likely has been slightly
wrong for some time) when you're using parameters in your request. Can you
detail the signature base string and authorization header you are using when
building this request?

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 8:00 AM, Jeff bigja...@gmail.com wrote:


 Tuesday morning around 10am CDT I noticed a change in the API
 endpoint /version/followers/ids in how it operates.

 If you provide the cursor parameter, such as:

 /1/followers/ids.json?cursor=-1user_id=12345 the method returns data
 correctly, however it also return the error warning Invalid OAuth
 credentials detected. Here is the response from the API.

   data:{
  responseText:{\previous_cursor\:0,\next_cursor_str\:\0\,
 \previous_cursor_str\:\0\,\ids\:
 [222126862,95945240,169607024,148845934,95447204,94401716],
 \next_cursor\:0},
  headers:{
 Date:Wed, 15 Jun 2011 14:39:54 GMT,
 Server:hi,
 Status:200 OK,
 X-Warning:Invalid OAuth credentials detected,
 X-Transaction:1308148794-15054-58845,
 X-RateLimit-Limit:150,
 X-Frame-Options:SAMEORIGIN,
 Last-Modified:Wed, 15 Jun 2011 14:39:54 GMT,
 X-RateLimit-Remaining:66,
 X-Runtime:0.02003,
 Content-Type:application\/json; charset=utf-8,
 Content-Length:150,
 Pragma:no-cache,
 X-RateLimit-Class:api,
 X-Revision:DEV,
 Expires:Tue, 31 Mar 1981 05:00:00 GMT,
 Cache-Control:no-cache, no-store, must-revalidate, pre-
 check=0, post-check=0,
 X-MID:c7827d770b9045b049f3967663b08dce7704a9fb,
 X-RateLimit-Reset:1308150383,
 Vary:Accept-Encoding,
 Connection:close
  },

 The problem here is that because it thinks the OAuth credentials are
 Invalid it gives me a rate limit of 150.

 If I remove the parameters ?cursor=-1user_id=12345 and simply use
 the endpoint /1/followers/ids.json it accepts my OAuth credentials as
 valid and and returns the appropriate rate limit of 350. Although this
 works, I need pagination as there are a lot of ids I need to retrieve.

 This had been working correctly and I noticed the change yesterday
 morning.

 Any help on resolving this or letting me know if something has changed
 when parameters are used with this endpoint would be greatly
 appreciated.

 Thanks,
 Jeff

 --
 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: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

Hi Jeff,

This is close to what I'm looking for -- it has the authorization header
which is important to see -- but what will really help us debug with you is
the signature base string -- it's a string that contains many of the same
values from the authorization header but presented in a specific format --
this is the string that is signed to create your oauth_signature. This
signature base string is usually the key to all OAuth problems, as the order
of parameters and particular encoding of them in relation to the parameters
on your query string or POST body are extremely important and somewhat
fragile.

I'm not sure which version of EpiOAuth you're using, but there's likely a
method similar to this one. The value you want to debug/capture here is
$signatureBaseString.

 protected function generateSignature($method = null, $url = null,
$params = null)
  {
if(empty($method) || empty($url))
  return false;

// concatenating and encode
$concatenatedParams =
$this-encode_rfc3986($this-buildHttpQueryRaw($params));

// normalize url
$normalizedUrl = $this-encode_rfc3986($this-normalizeUrl($url));
$method = $this-encode_rfc3986($method); // don't need this but why not?

$signatureBaseString = {$method}{$normalizedUrl}{$concatenatedParams};
return $this-signString($signatureBaseString);
  }


@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 8:22 AM, Jeff bigja...@gmail.com wrote:

 Taylor,

 Thanks for the response. Hopefully, this is what you need. I dumped it
 right before the request.

 [
   Expect:,
   Authorization: OAuth realm=\http:\/\/api.twitter.com\/1\/followers
 \/ids.json\,
   oauth_consumer_key=\OlPht6d2h3N1XYwCpCyx5Q\,
   oauth_token=\130232354-
 gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\,
   oauth_nonce=\71cc67f647043054dbd640b9b1f3d8fc\,
   oauth_timestamp=\1308151065\,
   oauth_signature_method=\HMAC-SHA1\,
   oauth_version=\1.0\,
   oauth_signature=\lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
 \,
   User-Agent: 
 ]

 On Jun 15, 10:05 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  This means that your signing is slightly wrong (and likely has been
 slightly
  wrong for some time) when you're using parameters in your request. Can
 you
  detail the signature base string and authorization header you are using
 when
  building this request?
 
  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary
 
 
 
 
 
 
 
  On Wed, Jun 15, 2011 at 8:00 AM, Jeff bigja...@gmail.com wrote:
 
   Tuesday morning around 10am CDT I noticed a change in the API
   endpoint /version/followers/ids in how it operates.
 
   If you provide the cursor parameter, such as:
 
   /1/followers/ids.json?cursor=-1user_id=12345 the method returns data
   correctly, however it also return the error warning Invalid OAuth
   credentials detected. Here is the response from the API.
 
 data:{
responseText:{\previous_cursor\:0,\next_cursor_str\:\0\,
   \previous_cursor_str\:\0\,\ids\:
   [222126862,95945240,169607024,148845934,95447204,94401716],
   \next_cursor\:0},
headers:{
   Date:Wed, 15 Jun 2011 14:39:54 GMT,
   Server:hi,
   Status:200 OK,
   X-Warning:Invalid OAuth credentials detected,
   X-Transaction:1308148794-15054-58845,
   X-RateLimit-Limit:150,
   X-Frame-Options:SAMEORIGIN,
   Last-Modified:Wed, 15 Jun 2011 14:39:54 GMT,
   X-RateLimit-Remaining:66,
   X-Runtime:0.02003,
   Content-Type:application\/json; charset=utf-8,
   Content-Length:150,
   Pragma:no-cache,
   X-RateLimit-Class:api,
   X-Revision:DEV,
   Expires:Tue, 31 Mar 1981 05:00:00 GMT,
   Cache-Control:no-cache, no-store, must-revalidate, pre-
   check=0, post-check=0,
   X-MID:c7827d770b9045b049f3967663b08dce7704a9fb,
   X-RateLimit-Reset:1308150383,
   Vary:Accept-Encoding,
   Connection:close
},
 
   The problem here is that because it thinks the OAuth credentials are
   Invalid it gives me a rate limit of 150.
 
   If I remove the parameters ?cursor=-1user_id=12345 and simply use
   the endpoint /1/followers/ids.json it accepts my OAuth credentials as
   valid and and returns the appropriate rate limit of 350. Although this
   works, I need pagination as there are a lot of ids I need to retrieve.
 
   This had been working correctly and I noticed the change yesterday
   morning.
 
   Any help on resolving this or letting me know if something has changed
   when parameters are used with this endpoint would be greatly
   appreciated.
 
   Thanks,
   Jeff
 
   --
   Twitter developer documentation and resources:
 https://dev.twitter.com/doc
   API updates via Twitter:https://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  https

Re: [twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

Thanks Jeff -- I can see the problem instantaneously -- your query
parameters are attached to the end of the escaped URL rather than be sorted
and ordered with the rest of the parameters (including the OAuth ones).

You correct signature base string would be:
GET
http://api.twitter.com/1/followers/ids.jsoncursor%3D-1%26oauth_consumer_key%3DOlPht6d2h3N1XYwCpCyx5Q%26oauth_nonce%3D7997664e2131b5c8f95fc3400b27c647%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1308152495%26oauth_token%3D130232354-gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY%26oauth_version%3D1.0%26user_id%3D130232354

Notice how the base URL contains no query parameters here, cursor is the
first parameter after the separator () as c comes before o, and user_id
is the final parameter in the sequence as u comes after o.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 8:43 AM, Jeff bigja...@gmail.com wrote:

 Here is a dump of $signatureBaseString

 GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Ffollowers%2Fids.json%3Fcursor
 %3D-1%26user_id%3D130232354oauth_consumer_key%3DOlPht6d2h3N1XYwCpCyx5Q
 %26oauth_nonce
 %3D7997664e2131b5c8f95fc3400b27c647%26oauth_signature_method%3DHMAC-
 SHA1%26oauth_timestamp%3D1308152495%26oauth_token%3D130232354-
 gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY%26oauth_version%3D1.0



 On Jun 15, 10:34 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
  Hi Jeff,
 
  This is close to what I'm looking for -- it has the authorization header
  which is important to see -- but what will really help us debug with you
 is
  the signature base string -- it's a string that contains many of the same
  values from the authorization header but presented in a specific format
 --
  this is the string that is signed to create your oauth_signature. This
  signature base string is usually the key to all OAuth problems, as the
 order
  of parameters and particular encoding of them in relation to the
 parameters
  on your query string or POST body are extremely important and somewhat
  fragile.
 
  I'm not sure which version of EpiOAuth you're using, but there's likely a
  method similar to this one. The value you want to debug/capture here is
  $signatureBaseString.
 
   protected function generateSignature($method = null, $url = null,
  $params = null)
{
  if(empty($method) || empty($url))
return false;
 
  // concatenating and encode
  $concatenatedParams =
  $this-encode_rfc3986($this-buildHttpQueryRaw($params));
 
  // normalize url
  $normalizedUrl = $this-encode_rfc3986($this-normalizeUrl($url));
  $method = $this-encode_rfc3986($method); // don't need this but why
 not?
 
  $signatureBaseString =
 {$method}{$normalizedUrl}{$concatenatedParams};
  return $this-signString($signatureBaseString);
}
 
  @episod http://twitter.com/intent/user?screen_name=episod - Taylor
  Singletary
 
 
 
 
 
 
 
  On Wed, Jun 15, 2011 at 8:22 AM, Jeff bigja...@gmail.com wrote:
   Taylor,
 
   Thanks for the response. Hopefully, this is what you need. I dumped it
   right before the request.
 
   [
 Expect:,
 Authorization: OAuth realm=\http:\/\/api.twitter.com\/1\/followers
   \/ids.json\,
 oauth_consumer_key=\OlPht6d2h3N1XYwCpCyx5Q\,
 oauth_token=\130232354-
   gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\,
 oauth_nonce=\71cc67f647043054dbd640b9b1f3d8fc\,
 oauth_timestamp=\1308151065\,
 oauth_signature_method=\HMAC-SHA1\,
 oauth_version=\1.0\,
 oauth_signature=\lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
   \,
 User-Agent: 
   ]
 
   On Jun 15, 10:05 am, Taylor Singletary taylorsinglet...@twitter.com
   wrote:
This means that your signing is slightly wrong (and likely has been
   slightly
wrong for some time) when you're using parameters in your request.
 Can
   you
detail the signature base string and authorization header you are
 using
   when
building this request?
 
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
 
On Wed, Jun 15, 2011 at 8:00 AM, Jeff bigja...@gmail.com wrote:
 
 Tuesday morning around 10am CDT I noticed a change in the API
 endpoint /version/followers/ids in how it operates.
 
 If you provide the cursor parameter, such as:
 
 /1/followers/ids.json?cursor=-1user_id=12345 the method returns
 data
 correctly, however it also return the error warning Invalid OAuth
 credentials detected. Here is the response from the API.
 
   data:{

  responseText:{\previous_cursor\:0,\next_cursor_str\:\0\,
 \previous_cursor_str\:\0\,\ids\:
 [222126862,95945240,169607024,148845934,95447204,94401716],
 \next_cursor\:0},
  headers:{
 Date:Wed, 15 Jun 2011 14:39:54 GMT,
 Server:hi,
 Status:200 OK,
 X-Warning:Invalid OAuth credentials detected

Re: [twitter-dev] How do I register a non-existent app?

Hi Tamara,

Just use placeholder data on dev.twitter.com/apps while registering your
application. You can use your @username as the name for your application or
something similar. For the callback URL -- this value is really just a
placeholder for all intents and purposes anyway, and so as long as you can
provide a valid URL there, you should be fine. With OAuth, you must specify
your callback URL explicitly on the request token step anyway.

After creating your application record, you can then use your API key and
secret to negotiate OAuth tokens and make calls from there. API methods that
don't require authentication also don't require that you use an API key to
access the resource, instead you could just simply explore the API using
curl or a simple HTTP library and move on from there.

Many beginners with OAuth find the tips on this page useful as well:
http://dev.twitter.com/pages/oauth_single_token

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 9:58 AM, t.williams tamara.mr.willi...@gmail.comwrote:

 Hello Developers:

 I have always heard of Twitter but just recently created a Twitter
 account. I want to develop an app which will use the Twitter API and
 more specifically the REST API to collect public Tweets and then
 perform some processing. I have been reading the documentation but
 still have a long way to go. Therefore, my concern is that my
 application is still in the design phase of the software lifecyle
 which means that I have not yet decided on a name and there is no
 website or callback URL. How then would I be able to perform a
 registration? I wanted the flexibility to code in functions or classes
 and test by making calls to the API instead of waiting until the full
 application was complete. However, in order to get developer access to
 the Twitter API I need to register the app and also according to the
 Authentication pages, registration is needed in order to use OAuth. I
 also looked at Twitter4J which also requires the use of OAuth. I am
 grateful for any advise that you can give. Thank you.

 Cheers,
 T Williams

 --
 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] error 401 from oauth, starting a few days ago

Hi Arlo,

Happy to help.

First, Twitter doesn't support any two-legged OAuth aside from the mandatory
two-leggedness of the request token step of OAuth and the variant xAuth
flow. Two-legged OAuth is where you sign requests and present your API key
but you have no user context (the access/oauth_token). If you're signing
an API request with OAuth, you must include an oauth_token to provide
context on the user who is making the request.

We're more strictly enforcing correctness in OAuth signatures and requests
now. Is the account that you're trying to retrieve the user_timeline for a
protected account? Are you using API urls in the style of
http://api.twitter.com/1/statuses/home_timeline.json ?

If you want to access a resource without a user context, you should simply
directly request the resource without attaching any kind of authorization to
the request at all.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary

On Wed, Jun 15, 2011 at 10:09 AM, arlomedia a...@arlomedia.com wrote:

Last July I installed oauth-php to display items from my user timeline
on my website home page. I then copied the setup to another website
with another Twitter account and both have been working fine.

Then a few days ago both websites started returning error code 401,
This method requires authentication. I can successfully run the
request_token command, but when I run the statuses/user_timeline
command I receive this error.

After experimenting with my own code for a while, I went back to
oauth's Twitter example code here:

http://code.google.com/p/oauth-php/source/browse/trunk/example/client/twoleggedtwitter.php
.
This worked fine when accessing the public timeline, but when I
changed it to access the user timeline, I received the same
authentication error.

I've updated to the latest version of oauth, but that made no
difference. I also reset my consumer key and consumer secret key and
that made no difference, either.

Can someone tell me what might have changed in the last few days, or
how I should proceed with troubleshooting this?

--
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] What changed in the OAuth signature process last few weeks?

Hi there,

We're now a bit stricter with how we evaluate the validity of requests.

Few things to look into for starters -- hopefully will help you discover the
subtle issue:

  - Are you setting your Content-Type:  x-www-form-urlencoded when POSTing
any kind of POST data?
  - Make sure that your signature basestring is properly sorting your
parameters and that any param values requiring percent-encoding are properly
encoded. If your POST body contains any characters that need to be
%-encoded, they'll need to be %-encoded again for your signature base string
  - Double verify that your consumer key and secret are correct and being
used at the right steps.
  - Double verify that you're specifying an oauth_token for resource
requests and that you've signed the request with the composite signing key
made up of your consumer secret and the access token secret, joined by a 
character.
  - If you're using header based auth, make sure that you aren't sending
oauth_* parameters in multiple locations like the query string in addition
to the header

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 15, 2011 at 1:20 PM, @giberti erik.gibe...@gmail.com wrote:

 A few months ago I wrote an application that interfaced with two API
 calls: statuses/user/timeline and statuses/update. It has been working
 fine until about seven days ago when I started receiving 401 status
 codes when reading the user timeline.

 I'm using a hand rolled OAuth / Twitter library that I built using the
 examples provided on the developer docs. I'm not sure where to go from
 here.

 --
 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] Randomly failing OAuth procedure

2011-06-14 Thread Taylor Singletary

Hi Felix,

Are you using a specific OAuth library for the OAuth portion?

I would recommend adding a bit of logging around the OAuth token negotiation
process.. find out the signature base string, the exact URL you're
executing, and the Authorization header you're sending. Log the response
code and body of the response when it fails. With the main OAuth ruby gem
that's out there, some of these details are hard to come by because the
values are hidden in private methods (PSA to OAuth library developers: don't
do this), so you may need to monkey patch the OAuth gem here and there to
debug the values.

What you're mainly looking for is a specific pattern to your failed requests
for a request token -- is some value not being sent correctly? Do you have
some kind of problem where in certain conditions a variable you've set like
your consumer key gets unset somehow? Is your system clock reliable? Is the
library you're using to generate HMAC-SHA1 signatures doing the right thing?
Are you using the right kind of URL encoding? Are you accidentally sending
double parameters for something?

Verify that you're using https://api.twitter.com/oauth/ as the base path for
the OAuth negotiation steps.

While there have been failures in the past in exchanging a request token for
an access token due to some lag, we're not aware of
anything specifically wrong with the process for fetching the request token.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jun 14, 2011 at 7:25 AM, Felix Oldenburg 
oldenburg.fe...@googlemail.com wrote:

 Hi twitter developing community,
 I'm using ruby( on rails) to do the oauth dance manually and finally
 call /1/statuses/update.json to update the status of an authorized
 user.

 Every single step during the oauth procedure is confirmed to be
 working.
 Actually I already tweeted some messages successfully. But for no
 obvious reason(to me), oauth sometimes fails at the very beginning
 while acquiring a request token. Then it just sais: Failed to
 validate oauth signature and token.

 Then I retry it several times until it (suddenly) works.
 The next step, i.e. exchanging the request token for an access token,
 works perfectly every time.
 But when it comes to the actual status update(i.e. calling the /1/
 statuses/update.json endpoint) it sometimes fails, too, saying Failed
 to validate oauth signature and token.

 Again I just retry a few times and all of a sudden it works.

 I don't change the code during this testing sessions, nor do i change
 the text I want to be tweetet.
 It just doesn't work sometimes.
 I can't reproduce this unwanted behavior.

 Did Somebody have the same issue?
 Suggestions are also appreciated.

 Kind regards, Felix.

 --
 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: illegal character in json feed

2011-06-14 Thread Taylor Singletary

Thanks for all the extra info, folks -- this is very useful and I've now got
a reproducible case. We'll look into this.

Thanks!
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jun 14, 2011 at 2:20 PM, Matt guitarroman...@gmail.com wrote:

 Can confirm this is happening to me too, for this request:


 http://search.twitter.com/search.json?q=from%3Atfr%20OR%20from%3ASOIANYCrpp=5callback=jQuery16106527990615355083_1308086280457_=1308086281400

 (I'm fetching tweets from two users - tfr and SOIANYC - if I
 remove SOIANYC from the query, it returns properly-formatted data.
 maybe this helps?)

 On Jun 14, 9:51 pm, Mike McNeil michael.r.mcn...@gmail.com wrote:
  Same thing's happening to me.  Check out:
 
 http://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
 http://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
 
  Should look like this:
  dog(
  {
 
 - -
 results: [
- -
{
   - from_user_id_str: 257702817
   - profile_image_url: 
 
 http://a1.twimg.com/profile_images/1364757456/2011-05-22_13.20.33_nor...
   
   - created_at: Tue, 14 Jun 2011 20:36:33 +
   - from_user: ATLienSince1987
   - id_str: 80735397449183232
   - -
   metadata: {
  - result_type: recent
   }
   - to_user_id: null
   - text: #JimRomeIsBurning
   - id: 80735397449183230
   - from_user_id: 257702817
   - geo: null
   - iso_language_code: is
   - to_user_id_str: null
   - source: lt;a href=quot;http://levelupstudio.com;
   rel=quot;nofollowquot;gt;Plume  lt;/agt;
} ..
 ]
 - max_id: 80735397449183230
 - since_id: 0
 - refresh_url: ?since_id=80735397449183232q=%23jimromeisburning
 - results_per_page: 15
 - page: 1
 - completed_in: 0.185672
 - since_id_str: 0
 - max_id_str: 80735397449183232
 - query: %23jimromeisburning
 
  }
 
  )
 
  But 3/5 times it doesn't, it looks like this:
 
  dog(  ݘYo F ǿʚF݇Z 85b )  M č ] 7 w .ےl ҇ A o 3 oN% hj 7 _ 2nkY * r
  A iH U
2 ȸ
  hϛf X 75 w _ @ \ ńt P   R 2 kS I ~
  ` I# 8i` ^+   Ȏ .댡_0| ` } { P: $
  M 8` E  e  K $Y $N qs= л ԍ i NW E ȯֲ SU~4  _ Vz0Y ,txǧNw Cg |VU
 H ~MMf P sۀ N k V sP4 W Kk g h J n L   i+ d1 M O   g E[ʿZ  { m W g q ]؈ 9
   ֏A ] v9_ ͔wi CF0 a qHE +
  Ǧ P# Um! = Y ` T  K+ 1 c 2  = t v߆   A $ }   * !b› |   v9 h- gj(
 .܇   2  G 4, 5 DcS
  s3FF bɄU*f H O 4 Dd X  5ʍ [0қN B |2h#.D 7 A@s#OĘ @љ @ g Z
 py\ Iw)bA q( ; S$E   F/e= O % d G@*A m Թ K J~B'? hTɦ Fu[I (;c ; Gpʇ E
  dQ IH / . p E$   Q L  * Gb{4 Y S . /$ ۪   υ P f 8 OP-  Z͏ `ky ' D
 Lt D I A~ 'M [ Od E'5 #:sڥj  ǲ9.Z / ]Q Y ~ x d3+ f{ , JIP M = % h$ 圜 m %|
 _M   Q #, * Osj V\ 7B C` p  r  odҡ M n Z1N   p(v) |p (
  Xd fȵP ! @ A p E hW d *iP fPY%5J   ٯ џ R ܶj eW P  'ۡ a
    c 3 b kc p v i O z B u K r .r Do[ uq zf ؤ oSu T M  ۥ${ R u1  E H 5
 -(= 7 ZA   ei8* Tvd TY L yf t = Z w1 H @ p *v ~Ru N ܶ C5
 !jJmVC \ s ptk [ w ^2 ){. q } j wI
  K XնY 3m Am,/o 7x8  p `  @# ż ʸ / l v # vi -  `2娐 ' aE Ɗ % / m !
  D x );
 
  Stackoverflow question:
 http://stackoverflow.com/questions/6348065/sencha-touch-jsonp-error

 --
 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] illegal character in json feed

2011-06-13 Thread Taylor Singletary

Do you have more details about the specific illegal character(s) you're
receiving? How frequently are you polling the API? Have you tried
reproducing your scenario outside of a browser-based environment?

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 13, 2011 at 11:55 AM, miramardesign miramardes...@gmail.comwrote:

 All browsers throw error illegal character in twitter jsonp feed

 http://jsfiddle.net/NBCGf/34/

 Please advise,
 //mh

 --
 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] illegal character in json feed

2011-06-13 Thread Taylor Singletary

It would be very helpful if you could provide a specific Tweet ID that
is exhibiting this behavior -- the test case you're presenting is a bit
artificial. Do you know if the environment you're doing this consumption is
fully capable of understanding the UTF-8 character set? Tweets can contain
just about any UTF-8 character and your parsing should be prepared for
that.

On a side note, executing a specific query against the Search API every six
seconds isn't the most efficient use of the API. Have you considered
increasing the time you wait to poll and using additional Search API feature
like since_id?

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 13, 2011 at 12:49 PM, michael hazzard
miramardes...@gmail.comwrote:

 Oh answers to #2 and #3

 2) I am polling the jsonp api every second in this test but it will be
 changed for production to like 6 seconds and cached after all 30 feeds are
 loaded

 3) No, I haven't tried outside the browser since this is strictly a jsonp
 feed and I chose jsonp over server-side xml but now regretting a bit.

 //mh



 On Mon, Jun 13, 2011 at 3:43 PM, michael hazzard 
 miramardes...@gmail.comwrote:

 Taylor();

 I took a pic of firebug here:

 https://docs.google.com/leaf?id=0B1lcI5OlKM2xNDczZDdmYTMtMjFjZi00Y2E2LWE4MTMtM2YyM2I5ZTM4Njhlsort=namelayout=listnum=50


 It is similar to this case (I believe the same chars)

 http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7567404004266db5?pli=1

 It is reproducible on the jsfiddle url if you look at the error console
 usually 10-20 iterations.

 http://jsfiddle.net/NBCGf/34/

 (Note: I recently added window.onerror to get around it for now and
 continue loading feeds.)

 Thanks,
 //mh


 On Mon, Jun 13, 2011 at 3:13 PM, Taylor Singletary 
 taylorsinglet...@twitter.com wrote:

 Do you have more details about the specific illegal character(s) you're
 receiving? How frequently are you polling the API? Have you tried
 reproducing your scenario outside of a browser-based environment?

 @episod http://twitter.com/intent/user?screen_name=episod - Taylor
 Singletary



 On Mon, Jun 13, 2011 at 11:55 AM, miramardesign miramardes...@gmail.com
  wrote:

 All browsers throw error illegal character in twitter jsonp feed

 http://jsfiddle.net/NBCGf/34/

 Please advise,
 //mh

 --
 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




 --
 Thank You,

 Michael Hazzard
 (954) 247-4461 https://www.google.com/voice#phones





 --
 Thank You,

 Michael Hazzard
 (954) 247-4461 https://www.google.com/voice#phones


  --
 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] Search all tweets by application

2011-06-13 Thread Taylor Singletary

Hi Juan,

There's no way to effectively retrieve all tweets sent by a given
application using primary methods of any of our APIs. The Search API has
some advanced operators that allow you to specify a specific tweet source
(effectively the string of text that represents the application that posted
the Tweet), but that operator must be used in conjunction with another
portion of your query.

One could also use the Streaming API to estimate a specific client's
tweeting velocity by measuring from the sample hose (which represents 1% of
the total tweets being posted) and extrapolate from there, but in the case
of measuring a Twitter client's popularity this would not be super-effective
since tweeting is just one activity that a client can perform.

Is there something with that information you're specifically wanting to
accomplish?

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote:

 Hi there,

 I cannot find a way of retrieving all the tweets coming from a given
 application. For example, can I retrieve all the tweets posted using
 TweeDeck?

 Nothings comes up on the documentation or in google, any idea?

 Cheers!

 Juan

 --
 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] Previously working app now failing with Not authorized to use this endpoint, code: 37

2011-06-09 Thread Taylor Singletary

Hi Peter,

You should make sure that you're using the api.twitter.com domain and a
version number in your URLs -- instead of the API call you're making, it
should be to https://api.twitter.com/1/followers/ids.json -- you aren't
using the API correctly otherwise and can have issues like this and
countless others effect you as a result.

The relocation to the api.twitter.com domain and version 1 of the API
occurred almost two years ago -- please review your code and migrate all
usage of the API to the correct endpoints.

Also, I notice that you're passing an oauth_body_hash parameter which is not
valid OAuth 1.0A but belongs to an extension to OAuth that Twitter does not
support. I recommend suppressing the usage of that parameter in calls you
make so that it doesn't further complicate your use of the API.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Thu, Jun 9, 2011 at 12:26 PM, digitalacorn digitalac...@gmail.comwrote:

 A previously working app now failing with Not authorized to use this
 endpoint, code: 37

 The url I am hitting is


 http://twitter.com/followers/ids.json?oauth_body_hash=XXXuser_id=oauth_nonce=oauth_timestamp=

 Has something changed?

 Kind Regards,

 Peter.

 --
 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] Translate app description to different languages

2011-06-08 Thread Taylor Singletary

Agree that this would be a great feature for the platform to have, but as
Scott  Tom said, it's currently not supported.

Your description can be up to 200 characters long - if your message is
simple, you might be able to present a few languages in the same field.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 8, 2011 at 6:40 AM, Tom van der Woerdt i...@tvdw.eu wrote:

 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


-- 
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

2011-06-08 Thread Taylor Singletary

Hi Christian,

The act of examining the non-string versions of the integers in an
environment that is actively trying to understand the Integer will almost
always yield a munged representation of the number. It's
like Schrödinger's Cat.

We don't actively support the extended featureset of @Anywhere and it may
have not been updated to understand the larger integers now used for tweet
ids. When using any feature of @Anywhere not explicitly documented on
dev.twitter.com, you're in unsupported territory that is susceptible to some
more recent complications in the Twitter platform like these larger
integers.

That said, thanks for the heads up that there are still some cases where
we're not using id_str where we should be.

Thanks,
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Wed, Jun 8, 2011 at 2:52 PM, Christian Rishøj christ...@rishoj.netwrote:

 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


-- 
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] follow JS Event + user Web Intent

2011-06-07 Thread Taylor Singletary

Hi Jonathan,

Glad you're finding the Intents Events useful!

I've tried reproducing this with the user/follow intent and have events
triggering as expected -- can you share some of the code you are using or
the browser environment you're encountering this on?

This simplest use case:
script type=text/javascript src=http://platform.twitter.com/widgets.js
/script
script type=text/javascript charset=utf-8
  twttr.events.bind('follow', function(event) {
console.warn(A follow happened.);
console.warn(event);
  });
/script
pa href=http://twitter.com/intent/user?screen_name=qwerty;Follow
@qwerty/a/p

In Firebug, this triggers the bound event after the follow action is
completed in the intent.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Tue, Jun 7, 2011 at 12:54 AM, Jonathan Strauss jonat...@awe.sm wrote:

 Congrats on the launch of JS Events, they make Web Intents that much more
 powerful!

 I managed to get follow event tracking working fine with the new Follow
 Button. But when I try to implement my own custom button UI using the user
 Web Intent (e.g. http://twitter.com/intent/user?screen_name=jhstrauss),
 the follow event doesn't seem to work the same.

 Is this a known issue or is there a different approach for tracking JS
 Events from Web Intents rather than from Twitter-hosted buttons?

 Thanks,
 -jonathan

 --
 Jonathan Strauss, Co-Founder
 http://awe.sm

 We're hiring! http://awe.sm/jobs

 Blog: http://jonathanhstrauss.com
 Twitter: http://twitter.com/jhstrauss

 --
 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] What is the correct way to get user permission to publish a tweet

2011-06-06 Thread Taylor Singletary

Hi Adam,

This kind of permission can be granted in many ways -- it's ultimately your
responsibility to ensure that you and the author of the tweet are on the
same page before using their tweets on physical goods or otherwise.

@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary


On Mon, Jun 6, 2011 at 12:35 PM, Adam Green 140...@gmail.com wrote:

 I have a client who wants to print tweets on t-shirts and other
 products. The API TOS says to get the users' permission, but doesn't
 say how. Is it enough to send them a tweet asking to use one of their
 past tweets, and then get a tweeted permission from them? Or does this
 permission have to be in writing?

 --
 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] API tweet ID field issue

It's also possible that whatever you're using to parse the resultant XML is
greedily selecting any field that is labeled id -- if there is a place_id
associated with the Tweet, it will be embedded in a deeper node of the
status object. In fact, the string-based id you presented represents a
location in Great Britain: ( GET
http://api.twitter.com/1/geo/id/3a1d856bf1925a2e.json ). You might want to
review how your XML  parsing handles nested objects.

@episod http://twitter.com/episod - Taylor Singletary


On Thu, Jun 2, 2011 at 6:44 AM, Scott Wilcox sc...@dor.ky wrote:

 The parser you're using can't handle the 'snowflake' generated IDs, the
 numbers are too huge for it.

 Use id_str instead.

 On 2 Jun 2011, at 13:47, gavinb wrote:

  Hi all
 
  Was hoping to get a little help with a quick questions, if possible?
 
  I currently use statuses/home_timeline.xml to get the recent timeline
  (including retweets) of the signed in user, but I have a slight issue
  in that it returns tweet id's such as id = 3a1d856bf1925a2e; if the
  poster is using geo tagging.  With these types of ID's i cant
  retweet.   How can i get twitter api to return the normal format id's
  such as id = 76174785381535744;
 
  any help appreciated
 
  Gavin
 

 --
 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


-- 
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] Pagination using cursors to retrieve follower ID's

Hi Correa,

I can't reproduce this issue -- can you share which account you're using to
test this? Is it an account with more than 5000 followers?

For example, I tried making these requests for @ev, who has 1.3M+ followers.

The first request with cursor=-1 begins with 309873322 and ends
with 107800155.
The second request with cursor=1370144140325967611 begins with 307280112 and
ends with 301233284

Make sure that you're using cursor_str instead of cursor from the response
of these methods if you're making the requests in languages like Javascript
where the act of consuming the Integer representation truncates/malforms the
integer. Malformed cursors may be the cause of your duplicated data.

@episod http://twitter.com/episod - Taylor Singletary


On Thu, Jun 2, 2011 at 1:11 PM, Correa Denzil mcen...@gmail.com wrote:

 Hi all,

 The Twitter API mentions that in order to retrieve more than 5000 user
 followers one must set the cursor = -1 and use the next_cursor_str and
 previous_cursor_str options to paginate over the results.

 However, I observe that I am retrieved similar results(follower ids)
 on each pagination call. The API suggests that Querying without the
 cursor parameter is deprecated and should be avoided.

 https://dev.twitter.com/doc/get/followers/ids

 --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

Re: [twitter-dev] Pagination using cursors to retrieve follower ID's

You've almost got it right -- in your second request, your params should
include cursor=1370145116766924316 -- cursor=-1 needn't be included, as -1
is the value for cursor in the first step, and then you adjust cursor for
each subsequent request. The response tells you what your *next* cursor=
value should be, not the name of key/value pair to include.

So step 1:
  https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1
And step 2:

https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=1370145116766924316
And so on.

@episod http://twitter.com/episod - Taylor Singletary


On Thu, Jun 2, 2011 at 1:53 PM, Correa Denzil mcen...@gmail.com wrote:

 Taylor :

 Thanks for the response. I make the calls in JSON. Here's how I make
 the calls. The first call is for :
 https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1

 This call returns with next_cursor_str:1370145116766924316

 I make the next cursor call as :


 https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1next_cursor=1370145116766924316

 Is this correct?  If that's the case, each of these calls return a
 'ids' list which consist of the list of followers (5000 per call). I
 see that the ids are overlapping on each call which shouldn't happen
 ideally.

 --Regards,
 Denzil




 On Fri, Jun 3, 2011 at 2:06 AM, Taylor Singletary
 taylorsinglet...@twitter.com wrote:
  Hi Correa,
  I can't reproduce this issue -- can you share which account you're using
 to
  test this? Is it an account with more than 5000 followers?
  For example, I tried making these requests for @ev, who has 1.3M+
 followers.
  The first request with cursor=-1 begins with 309873322 and ends
  with 107800155.
  The second request with cursor=1370144140325967611 begins with 307280112
 and
  ends with 301233284
  Make sure that you're using cursor_str instead of cursor from the
 response
  of these methods if you're making the requests in languages like
 Javascript
  where the act of consuming the Integer representation truncates/malforms
 the
  integer. Malformed cursors may be the cause of your duplicated data.
  @episod - Taylor Singletary
 
 
  On Thu, Jun 2, 2011 at 1:11 PM, Correa Denzil mcen...@gmail.com wrote:
 
  Hi all,
 
  The Twitter API mentions that in order to retrieve more than 5000 user
  followers one must set the cursor = -1 and use the next_cursor_str and
  previous_cursor_str options to paginate over the results.
 
  However, I observe that I am retrieved similar results(follower ids)
  on each pagination call. The API suggests that Querying without the
  cursor parameter is deprecated and should be avoided.
 
  https://dev.twitter.com/doc/get/followers/ids
 
  --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] Is the sample stream still delivering 1% of all public tweets?

Hi Ed,

Yes, 1% sampling rate is still the current percentage.

@episod http://twitter.com/episod - Taylor Singletary


On Thu, Jun 2, 2011 at 12:25 PM, M. Edward (Ed) Borasky 
zn...@borasky-research.net wrote:

 I'm just getting back to my code that uses the sample Streaming endpoint.
 Is that still delivering 1% of all public tweets?

 --
 http://twitter.com/znmeb http://borasky-research.net

 A mathematician is a device for turning coffee into theorems. -- Paul
 Erdos



 --
 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 comment on Error responses ?

2011-05-31 Thread Taylor Singletary

To add to Arnaud's comment...

There was a past where Twitter's error messages were very unstructured.
Newer API features follow a more descriptive, human-readable,
and programmatically consumable error structure. Version 1 of the API has
mixed error response formats depending on when the feature was introduced
(some introduced before versioning was present in the API). One can expect
that future versions of the API will have a unified error response structure
that will be able to adapt as needs and wisdom change.

I know that it's hard to pre-prepare your code for error conditions you may
not typically come across and we'll work this week on better documenting
both the less structured and more structured error responses for everyone's
benefit.

@episod http://twitter.com/episod - Taylor Singletary


On Tue, May 31, 2011 at 9:47 AM, Arnaud Meunier arn...@twitter.com wrote:

 Hey Maomor,

 The Error codes don't follow a logic in particular.
 I'd recommend that you rely on the (error message string + HTTP Code)
 combination.

 Hope that helps,
 Arnaud / @rno http://twitter.com/rno



 On Mon, May 30, 2011 at 6:05 AM, Maomor maldw...@gmail.com wrote:

 I do not understand why twitter will not tell us how we should handle
 their error codes.

 Our applications need to distinguish between an error response such as
 7 ( No data for a place ) and 10 ( Geo services currently
 unavailable ).

 Can Twitter understand that we have the need to do this ?

 And, if so, why do they remain silent on this issue ?

 --
 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] Introducing the Follow Button

2011-05-31 Thread Taylor Singletary

Hi Ed,

@Anywhere is an effort to provide a client-side authentication 
authorization flow to Twitter REST API integrations: a simpler, more
frictionless experience for common Twitter actions. While @Anywhere meets
this criteria, there is obvious room for continued simplification, both for
end-users and implementors. @Anywhere applications still require a developer
to register an application and the end-user to make additional approvals for
that application construct.

The Twitter for Websites arm of the Twitter Platform (Tweet Button, Follow
Button, and Web Intents) provides integrators with even simpler solutions
that don't require API keys. By utilizing the end user's logged in state,
the gulf between the user's intention to act and the action being
accomplished is bridged. While the Buttons, like @anywhere, use Javascript,
the building blocks they use, Web Intents, provide perhaps the most atomic
form of frictionless integration: simple URLs that can be linked from any
web-enabled context, with or without Javascript.

Web Intents and the Tweet  Follow Buttons are the best fit for a wide swath
of integration points. Deeper integrations are still best serviced by
server-side REST integrations or @Anywhere.

@episod http://twitter.com/episod - Taylor Singletary


On Tue, May 31, 2011 at 3:24 PM, M. Edward (Ed) Borasky 
zn...@borasky-research.net wrote:

 Now I'm getting curious about the road map for @anywhere and all the
 miscellaneous Twitter plugins, especially for WordPress. Last year, when
 Twitter announced @anywhere, I tried a couple of plugins before settling on
 one. What I got from that was hovercards, tweet boxes and follow buttons.

 A few months later, I discovered that the trips to Twitter servers were
 slowing down my blog's page loads, so I stopped using @anywhere. Since then,
 there have been some other JavaScript tools from Twitter, and now this
 Follow Button.

 So I've put a follow button on my blog. So far it doesn't seem to be
 slowing it down, but it's only been up a couple of hours. In any event, is
 @anywhere deprecated, in favor of the most popular single functions from
 the collection, like follow buttons? Or are there always going to be
 multiple JavaScript / HTML widgets and gizmos coming from Twitter that
 users need to track?


 --
 http://twitter.com/znmeb http://borasky-research.net

 A mathematician is a device for turning coffee into theorems. -- Paul
 Erdos



 Quoting Arnaud Meunier arn...@twitter.com:

  Hey developers,

 Today we're launching the Follow Button!  Similar to the Tweet Button,
 it's a new widget that lets users easily follow a Twitter account from
 any web page. The Follow Button has a single click follow experience,
 simple implementation model, and is configurable to fit the needs of
 your website.

 Read our announcement on the Twitter blog, and use the resources below
 to set up your own Follow Button:

 - Create a Follow Button here:
 http://twitter.com/about/resources/followbutton
 - Detailed documentation: http://dev.twitter.com/pages/follow_button

 We’ve also added a Javascript layer to our Buttons and Web Intents
 that makes it possible for you to detect how users are interacting
 with these tools, and to hook them up to your own web analytics. More
 details on: http://dev.twitter.com/pages/intents-events

 We're excited to see how you guys will implement the Follow Button.
 Let us know what you think, or if you have any questions.

 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


 --
 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] https://dev.twitter.com/apps over capacity since at least 8am EDT today (5/27/11)

Hi Kyle,

I'm unable to reproduce.. Have you tried logging out and logging back in?

A few other questions to help diagnose:
 -- If you go to https://twitter.com are you logged in?
 -- Are you using SSL always on on your Twitter profile?

Thanks
@episod http://twitter.com/episod - Taylor Singletary


On Fri, May 27, 2011 at 8:14 AM, Kyle Bragger kyle.brag...@gmail.comwrote:

 Hi all, anyone have any insight into what's going on with app
 management on Twitter? https://dev.twitter.com/apps has been sending
 over capacity responses for any POST for at least the last 3 hours.

 This occurs for both new apps and existing, and across multiple
 accounts.

 Thanks
 Kyle

 --
 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: New 2 Android twitter app

This is very Java/Android specific code here which makes it difficult for a
generalist to provide assistance to you. There are quite a few reasons for
an OAuth signature to fail validation, and many libraries abstract the OAuth
process to a point where you cannot clearly determine what aspect of the
request is at fault.

It would appear the callback scheme here is the protocol/scheme used for the
callback to hit (which likely needs to be registered  understood by the
device) and the callback URL is the path in your application that can
understand and consume the HTTP callback it will receive.

If you can provide more basic/primitive details on how this is failing, at
the HTTP level or examples of your signature base strings (generally made
difficult to obtain by overly-complex OAuth libraries) we can help you with
much more ease.

Finally, often OAuth failures are for really simple reasons: the clock being
off on the device for example.

Do you have much experience with OAuth outside of the usage of this
library?

@episod http://twitter.com/episod - Taylor Singletary


On Fri, May 27, 2011 at 1:23 PM, marcio quique...@gmail.com wrote:

 Ive been told its a twitter api problem because only changing the
 key/secret causes the error.

 --
 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: New 2 Android twitter app

All other concerns aside, this error here indicates that for some reason
your code is not able to reach out to
api.twitter.com/oauth/request_tokenvia SSL.

Can you provide a brief overview of the settings you've made for your keys
on dev.twitter.com? Application type (should be Client with a placeholder
callback) and R/W or RO or RW+DM status?

Thanks,
Taylor

On Fri, May 27, 2011 at 2:44 PM, marcio quique...@gmail.com wrote:

 Caused by: java.io.FileNotFoundException:
 https://api.twitter.com/oauth/request_token
 05-27 14:40:25.984: WARN/System.err(441): at
 org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:532)


-- 
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: New 2 Android twitter app

The sample code you're showing me uses a callback (a custom URI callback
URL) so you'll need your application settings to client (Desktop restricts
dynamic callbacks). Just put a placeholder HTTP-based URL in the callback
field, select the Client radio button and save your app -- it might be the
reason you're getting the error -- assuming that your library is obfuscating
the true nature of the error.

@episod http://twitter.com/episod - Taylor Singletary


On Fri, May 27, 2011 at 3:06 PM, marcio quique...@gmail.com wrote:

 @Anywhere settings...but there is nothing there.
 API KEY (which incidentally is the same as the OAuth Key)
 Callback URL is empty because i chose Client type.
 General Access Level : Read  Write Permissions
 OAuth 1.0 Settings
 Consumer Key
 Consumer Secret
 Request Token URL
 Access Token URL
 Authorize URL

 thats 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


-- 
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: New 2 Android twitter app