date:20090709

If you use Gmail or Google Apps for email (and maybe others) you can use
4braham+secrettwitteracc...@gmail.com4braham%2bsecrettwitteracc...@gmail.comto
sign up and unless you tell people what the string after the + no
one
will be able to find you.

Abraham

On Wed, Jul 8, 2009 at 21:10, Scott Haneda talkli...@newgeo.com wrote:


 On Jul 8, 2009, at 4:22 PM, Doug Williams wrote:

  It is not possible to view a user's email address. Additionally, it is not
 possible to perform a user lookup based on an email address.


 This is not entirely true, though can not be done through the API.  I had
 friends find me on twitter, and for month, never knew why.  It is quote
 simple to load an email into gmail, and add that to twitter and it will look
 up any user with that email.

 I wish this feature was able to be disabled.  I have had to create a junk
 email account in twitter, just so I have some privacy.  I get that the posts
 are not private, but I had an account that was not something I wanted people
 to connect with me.  That is too late now.

 No where on the twitter Web site is it explained that your email address
 can be used as a way for users to locate you.

 I personally believe, this should be explained in detail on the join page
 where you enter in your email address.  And I should be able to opt out of
 this feature.
 --
 Scott * If you contact me off list replace talklists@ with scott@ *




-- 
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: About OAuth authorization


1. OAuth allows your user to authenticate without ever exposing his
Twitter credentials to your application.

2. OAuth allows a user to revoke your application's access to their
account.

3. If you don't use OAuth, tweets posted from your application will
show up as from API (I believe).  You can't put the name of your
application in there unless you use OAuth.

4. Basic Auth will eventually be deprecated.  If the first three
reasons don't convince you, you should give this one serious
consideration. :)

I have some issues with OAuth, but they're minor and hardly
insurmountable.  Moreover, if you use a library that handles OAuth for
you, implementing it is not a major endeavor.

Regards,
--Duane

On Jul 9, 7:56 am, praveen kumar praveen.neteli...@gmail.com wrote:
 Hi,

 I would like to develop a tool on Twitter, i have few  doubts. Please
 clarify.

 1. What is the use of OAuth authorization ?

 2. From Twitter API we can update tweets without OAuth authorization. Why
 this OAuth authorization?

 --
 Regards,
 Praveen Kumar .N
 Software Engineer
 Netelixir e-Marketing Solutions
 Hyderabadwww.netelixir.com

[twitter-dev] Re: stopping bit.ly automatic shortening of urls

2009-07-09 Thread infopete



My current idea is to go with the flow and use bit.ly to store my
structured url and have my silverlight application use the bit.ly api
to get the structured data. I had hoped that i could have meaningful
url's in the tweet but it's not over important.

I'll use the extra space in the tweet for location information.

Thanks everyone for your input.



On Jul 7, 4:20 pm, Dean Collins d...@cognation.net wrote:
 Yeh we have the same problem withwww.LiveBaseballChat.com
 http://www.livebaseballchat.com/  

 Even though we keep the messages under 140 characters and put the CHurl
 links at the start of the message Twitter still truncates the urls into
 bitly links. which wouldn't be so bad if it was just a URL but our
 CHurls are structured links eg this fake link below.

 *       http://www.livebaseballchat.com/CHurl/09/04/11/10/A1234F







  Made up of the following constitute parts

  URL/ Live Baseballchat.com

  CHurl/ Word

  09/ Year

  04/ Month

  11/ Date

  10/ Room number

  A1234FG/ Message number

 I'm hoping that eventually once Twitter starts offering commercial
 accounts that 'non bitly' truncation is one of the features that paid
 accounts will be able to pay for.

 Regards,

 Dean Collins
 Cognation Inc
 d...@cognation.net
 mailto:d...@cognation.net +1-212-203-4357   New York
 +61-2-9016-5642   (Sydney in-dial).
 +44-20-3129-6001 (London in-dial).

 

 From: twitter-development-talk@googlegroups.com
 [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Abraham
 Williams
 Sent: Tuesday, July 07, 2009 9:11 AM
 To: twitter-development-talk@googlegroups.com
 Subject: [twitter-dev] Re: stopping bit.ly automatic shortening of urls

 There is no way to turn URL shortening off.

 Two ways you could handle this though are:
 1) Keep the URLs short enough that Twitter does not turn them into bitly
 links. I don't think the exact size/composition is published so you
 would have to experiment to see where that line is.
 2) Shorten it yourself so you can control what comes after the /. It
 would not be a direct link but you could parse it.

 Abraham

 On Tue, Jul 7, 2009 at 06:42, infopete p...@infonote.com wrote:

 we're writing an application to do live gps tracking with Twitter.

 We'd like to be able to have a full url in a message which we could
 parse or use as a direct web link.

 GPS logging will be done on pocket pc based phones and we already have
 a test application available (Twittrack).

 We're extending the functionality of our silverlight 
 applicationhttp://tweepware.infonote.comto be able to display live gps updates
 from Twitter.

 But..

 When we post to Twitter using the api our url is always shrunk to a
 bit.ly url.

 How can we stop this?

 Regards

 Pete

 --
 Abraham Williams | Community Evangelist |http://web608.org
 Hacker |http://abrah.am|http://twitter.com/abraham
 Project |http://fireeagle.labs.poseurtech.com
 This email is: [ ] blogable [x] ask first [ ] private.- Hide quoted text -

 - Show quoted text -

[twitter-dev] Re: OAuth pin only works first try?


You don't get a second chance, and this is by design.  OAuth requests
have a unique signature; once a particular request is submitted, it
can't be submitted again.

There's no real way to validate the pin before you submit.  All you
can do is ensure that they typed in six digits.  If the authentication
fails, you'll need to show a message to your user letting them know
that they'll have to get a new PIN.

On Jul 9, 11:50 am, Grant Emsley grant.ems...@gmail.com wrote:
 I'm not sure if this is a problem with my code, the libraries I'm
 using (perl Net::Twitter::Role::OAuth) or something else entirely.

 My program gets a request token, shows the user the website URL, and
 waits for the pin.

 If they enter the pin correctly, all it well, I get an access token.
 If they enter the pin wrong, I get 401 Unauthorized - which is
 expected.
 But if they then try again to enter the pin, even the correct pin
 shows as unauthorized.

 Is there a way to give the user a second chance to get the pin right,
 or do they have to go to the website and get a new one? Is there some
 way to validate the pin before using it?

[twitter-dev] Re: OAuth pin only works first try?

2009-07-09 Thread Grant Emsley


I thought it might be by design, but couldn't find that mentioned
anywhere.  I guess it is necessary to prevent apps guessing the pin,
though it may be annoying for users.

[twitter-dev] Re: OAuth pin only works first try?

2009-07-09 Thread Doug Williams

Indeed, this is by design. As Grant said, it is to prevent brute force
attacks.

Thanks,
Doug




On Thu, Jul 9, 2009 at 10:58 AM, Grant Emsley grant.ems...@gmail.comwrote:


 I thought it might be by design, but couldn't find that mentioned
 anywhere.  I guess it is necessary to prevent apps guessing the pin,
 though it may be annoying for users.

[twitter-dev] Re: Design of Invite Twitter friends

2009-07-09 Thread Xavier Mathews


Just curious to know. Because of number three this would only work for
users who have there stream set to private?

On 07/09/2009, chachra sumit.chac...@gmail.com wrote:

 Hi,

 I'm trying to design a invite twitter friends feature (similar to
 the invite facebook friends concept).

 Sadly its not drop some code, like Facebook is... I'll have to develop
 from scratch. Wondering whats the most scalable way of doing this?
 Details:

 #1 By friends of course means followers since I can direct message
 them
 #2 The graph API call returns ID's, I would have to make $n api calls
 to get details on each of the $n id's right? Getting the users name,
 picture etc. ?
 #3 Then when the user selects users to invite, and presses submit
 then I'll have to make $m direct message calls ($m  $n)?

 Sounds like a lot of API calls to achieve something really simple.
 anyone have ways of doing this nicely? I would love to eliminate calls
 in #2 if possible.

 Cheers!
 Sumit



-- 
Sent From Sony Slim-Line PSP

Xavier A. Mathews
Web-Developer

[twitter-dev] OAuth failing to validate signature

2009-07-09 Thread Bojan Rajkovic


Is there a way that we can get more information on why a signature is
not being validated? My OAuth library suddenly stopped validating
signatures earlier. I've reset the consumer key and consumer signature
several times since then, and things still keep failing. I've compared
the requests being made that fail to the request that worked, and they
appear to be same on the outside.

[twitter-dev] Re: OAuth failing to validate signature


Is it just certain sorts of requests that are failing, or all of them?

I'm running my OAuth-enabled client right now and things seem to be
working.

On Jul 9, 4:26 pm, Bojan Rajkovic severedcr...@gmail.com wrote:
 Is there a way that we can get more information on why a signature is
 not being validated? My OAuth library suddenly stopped validating
 signatures earlier. I've reset the consumer key and consumer signature
 several times since then, and things still keep failing. I've compared
 the requests being made that fail to the request that worked, and they
 appear to be same on the outside.

[twitter-dev] Re: OAuth failing to validate signature

2009-07-09 Thread JDG

That's something that I would really like to see as well -- even if it was a
development parameter (ala debug=true) that could be put in the signature.

On Thu, Jul 9, 2009 at 14:41, Bojan Rajkovic severedcr...@gmail.com wrote:


 On Jul 9, 4:26 pm, Bojan Rajkovic severedcr...@gmail.com wrote:
  Is there a way that we can get more information on why a signature is
  not being validated? My OAuth library suddenly stopped validating
  signatures earlier. I've reset the consumer key and consumer signature
  several times since then, and things still keep failing. I've compared
  the requests being made that fail to the request that worked, and they
  appear to be same on the outside.

 Well, I solved my issue in the meantime (came down to requesting
 www.twitter.com vs twitter.com), but I would still like to know if we
 can get some more information with the validation failed message.




-- 
Internets. Serious business.

[twitter-dev] How to insure that all tweets are retrieved in a search?

2009-07-09 Thread owkaye


I'm building an app that uses the atom search API to retrieve recent
posts which contain a specific keyword.  The API docs say:

Clients may request up to 1,500 statuses via the page and rpp
parameters for the search method.

But this 1500 hits per search cannot be done in a single request
because of the rpp limit.  Instead I have to perform 15 sequential
requests in order to get only 100 items returned on each page ... for
a total of 1500 items.

This is certainly a good way to increase the server load, since 15
connections at 100 results each takes far more server resources than 1
connection returring all 1500 results.  Therefore I'm wondering if I'm
misunderstanding something here, or if this is really the only way I
can get the maximum of 1500 items via atom search?

[twitter-dev] Re: How to insure that all tweets are retrieved in a search?

2009-07-09 Thread Chad Etzel


Yep, you gotta do 15 requests at 100 rpp each.
-Chad

On Thu, Jul 9, 2009 at 5:45 PM, owkayeowk...@gmail.com wrote:

 I'm building an app that uses the atom search API to retrieve recent
 posts which contain a specific keyword.  The API docs say:

 Clients may request up to 1,500 statuses via the page and rpp
 parameters for the search method.

 But this 1500 hits per search cannot be done in a single request
 because of the rpp limit.  Instead I have to perform 15 sequential
 requests in order to get only 100 items returned on each page ... for
 a total of 1500 items.

 This is certainly a good way to increase the server load, since 15
 connections at 100 results each takes far more server resources than 1
 connection returring all 1500 results.  Therefore I'm wondering if I'm
 misunderstanding something here, or if this is really the only way I
 can get the maximum of 1500 items via atom search?

[twitter-dev] Re: How to insure that all tweets are retrieved in a search?

2009-07-09 Thread owkaye


Thanks Chad, that's what I was afraid of.  I wonder if you
know about this next question:

Twitter API docs say search is rate limited to something
more than REST which is 150 requests per hour, but for the
sake of argument let's say the search rate limit is actually
150 hits per hour ...

Since I have to do 15 consecutive searches to make sure I've
retrieved the last 1500 matching items, does this mean I can
only do 10 sets of 15 searches per hour = 150 request per
hour?

If so, this is only one set of searches every 6 minutes, and
it seems to me that on a trending topic there might be lots
more than 1500 new tweets every 6 minutes.

How can I get around this limit?

I'm not trying to hurt Twitter, but business applications that
require ALL tweets to be recorded cannot deal with these
types of limitations on a practical basis, and if Twitter doesn't
come up with a better way I can see this hindering its future
revenue streams from businesses like mine that want to build
on a solid and easy-to-use foundation.

So getting back to my question of What do I do now ...

Do I have to put my automated search code on a bunch of
separate servers so the IP's are spread around -- such that
none of them hit the limit of 150 searches per hour?

Seems to me that this is the only realistic way to insure
that I can always retrieve all the matching results I need
without hitting the API limits ... but if you or others have
a better suggestion please let me know, thanks.


On Jul 9, 5:52 pm, Chad Etzel jazzyc...@gmail.com wrote:
 Yep, you gotta do 15 requests at 100 rpp each.
 -Chad

 On Thu, Jul 9, 2009 at 5:45 PM, owkayeowk...@gmail.com wrote:

  I'm building an app that uses the atom search API to retrieve recent
  posts which contain a specific keyword.  The API docs say:

  Clients may request up to 1,500 statuses via the page and rpp
  parameters for the search method.

  But this 1500 hits per search cannot be done in a single request
  because of the rpp limit.  Instead I have to perform 15 sequential
  requests in order to get only 100 items returned on each page ... for
  a total of 1500 items.

  This is certainly a good way to increase the server load, since 15
  connections at 100 results each takes far more server resources than 1
  connection returring all 1500 results.  Therefore I'm wondering if I'm
  misunderstanding something here, or if this is really the only way I
  can get the maximum of 1500 items via atom search?

[twitter-dev] Re: How to insure that all tweets are retrieved in a search?

2009-07-09 Thread Scott Haneda



You are correct, you have to do 15 requests.  However, you can cache  
the results in your end, so when you come back, you are only getting  
the new stuff.


Twitter has pretty good date handling, so you specify your last date,  
and pull forward from there.  You may even be able to get the last id  
of the last tweet you pulled, and just tell it to get you all the new  
ones.


On Jul 9, 2009, at 2:45 PM, owkaye wrote:


I'm building an app that uses the atom search API to retrieve recent
posts which contain a specific keyword.  The API docs say:

Clients may request up to 1,500 statuses via the page and rpp
parameters for the search method.

But this 1500 hits per search cannot be done in a single request
because of the rpp limit.  Instead I have to perform 15 sequential
requests in order to get only 100 items returned on each page ... for
a total of 1500 items.

This is certainly a good way to increase the server load, since 15
connections at 100 results each takes far more server resources than 1
connection returring all 1500 results.  Therefore I'm wondering if I'm
misunderstanding something here, or if this is really the only way I
can get the maximum of 1500 items via atom search?


--
Scott * If you contact me off list replace talklists@ with scott@ *

[twitter-dev] Re: How to insure that all tweets are retrieved in a search?

2009-07-09 Thread owkaye


 You are correct, you have to do 15 requests.  However,
 you can cache the results in your end, so when you come
 back, you are only getting the new stuff.

Thanks Scott.  I'm storing the results in a database on my server but
that doesn't stop the search from retrieving the same results
repetitively, because the search string/terms are still the same.

My problem is going to occur when thousands of people start tweeting
my promo codes every minute and I'm not able to retrieve all those
tweets because of the search API limitations.

If I'm limited to retrieving 1500 tweets every 6 minutes and people
post 1000 tweets every minute I need some way of retrieving the
missing 4500 tweets -- but apparently Twitter doesn't offer anything
even remotely close to this capability -- so I can see where it has a
long way to go before it's ready to support the kind of search
capabilities I need.


 Twitter has pretty good date handling, so you specify
 your last date, and pull forward from there.  You may
 even be able to get the last id of the last tweet you
 pulled, and just tell it to get you all the new ones.

Yep, that's what I'm doing ... pulling from the records I haven't
already retrieved based on the since_id value.

But when the new tweets total more than 1500 in a short time, the
excess tweets will get lost and there's no way to retrieve them --
unless I run my searches from multiple servers to avoid Twitter's ip
address limits -- and doing this would be a real kludge that I'm not
tempted to bother with.


  I'm building an app that uses the atom search API to retrieve recent
  posts which contain a specific keyword.  The API docs say:

  Clients may request up to 1,500 statuses via the page and rpp
  parameters for the search method.

  But this 1500 hits per search cannot be done in a single request
  because of the rpp limit.  Instead I have to perform 15 sequential
  requests in order to get only 100 items returned on each page ... for
  a total of 1500 items.

  This is certainly a good way to increase the server load, since 15
  connections at 100 results each takes far more server resources than 1
  connection returring all 1500 results.  Therefore I'm wondering if I'm
  misunderstanding something here, or if this is really the only way I
  can get the maximum of 1500 items via atom search?

 --
 Scott * If you contact me off list replace talklists@ with scott@ *

[twitter-dev] Re: OAuth failing to validate signature


Same problem here, all my Oauth requests are receiving a Could not
authenticate you. answer with a 401. Don't understand why, I didn't
change anything, and this just started to happen a few minutes ago.
The application type is Browser, with the Twitter for login option.

Quite a big problem on my side, as I can't synchronize accounts
anymore. Had to stop the service.
Anyone knowing what's going on?

Arnaud.


On Jul 9, 10:43 pm, JDG ghil...@gmail.com wrote:
 That's something that I would really like to see as well -- even if it was a
 development parameter (ala debug=true) that could be put in the signature.

 On Thu, Jul 9, 2009 at 14:41, Bojan Rajkovic severedcr...@gmail.com wrote:

  On Jul 9, 4:26 pm, Bojan Rajkovic severedcr...@gmail.com wrote:
   Is there a way that we can get more information on why a signature is
   not being validated? My OAuth library suddenly stopped validating
   signatures earlier. I've reset the consumer key and consumer signature
   several times since then, and things still keep failing. I've compared
   the requests being made that fail to the request that worked, and they
   appear to be same on the outside.

  Well, I solved my issue in the meantime (came down to requesting
 www.twitter.comvs twitter.com), but I would still like to know if we
  can get some more information with the validation failed message.

 --
 Internets. Serious business.

[twitter-dev] Has something with OAuth changed?

2009-07-09 Thread dean.j.robinson


Everyone just magically got logged out of my hahlo4 beta, which was
working fine an hour ago, and now when they reauthorize its not
sticking.

OAuth login works fine, redirect back to hahlo4, but all api calls are
returning 401 status codes.

Saw mention in another topic regarding whether  twitter.com or www.twitter.com
should be used when making api call, all my calls are currently using
https://twitter.com

Anyone else experiencing anything similar?

[twitter-dev] Re: Has something with OAuth changed?

2009-07-09 Thread Matt Sanford



Hi all,

Some changes were just deployed and it looks like there may be a  
bug. I'm looking into it now … hold tight and I'll update you all when  
I know more.


Thanks;
 – Matt Sanford / @mzsanford
 Twitter Dev

On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote:



Everyone just magically got logged out of my hahlo4 beta, which was
working fine an hour ago, and now when they reauthorize its not
sticking.

OAuth login works fine, redirect back to hahlo4, but all api calls are
returning 401 status codes.

Saw mention in another topic regarding whether  twitter.com or www.twitter.com
should be used when making api call, all my calls are currently using
https://twitter.com

Anyone else experiencing anything similar?

[twitter-dev] Re: Has something with OAuth changed?


Yes, my application - which was working this morning - is now getting
401s on every OAuth request.

Something changed.

On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
wrote:
 Everyone just magically got logged out of my hahlo4 beta, which was
 working fine an hour ago, and now when they reauthorize its not
 sticking.

 OAuth login works fine, redirect back to hahlo4, but all api calls are
 returning 401 status codes.

 Saw mention in another topic regarding whether  twitter.com orwww.twitter.com
 should be used when making api call, all my calls are currently 
 usinghttps://twitter.com

 Anyone else experiencing anything similar?

[twitter-dev] Re: Has something with OAuth changed?

2009-07-09 Thread Michael Pelz-Sherman

I just did a successful authorization with my iphone app.

Hopefully it was just a temporary glitch.

From: Duane Roelands duane.roela...@gmail.com
To: Twitter Development Talk twitter-development-talk@googlegroups.com
Sent: Thursday, July 9, 2009 7:29:28 PM
Subject: [twitter-dev] Re: Has something with OAuth changed?

Yes, my application - which was working this morning - is now getting
401s on every OAuth request.

Something changed.

On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
wrote:
 Everyone just magically got logged out of my hahlo4 beta, which was
 working fine an hour ago, and now when they reauthorize its not
 sticking.

 OAuth login works fine, redirect back to hahlo4, but all api calls are
 returning 401 status codes.

 Saw mention in another topic regarding whether  twitter.com orwww.twitter.com
 should be used when making api call, all my calls are currently 
 usinghttps://twitter.com

 Anyone else experiencing anything similar?

[twitter-dev] Re: Has something with OAuth changed?

2009-07-09 Thread dean.j.robinson


Thanks for the super speedy response Matt.

On Jul 10, 9:26 am, Matt Sanford m...@twitter.com wrote:
 Hi all,

      Some changes were just deployed and it looks like there may be a  
 bug. I'm looking into it now … hold tight and I'll update you all when  
 I know more.

 Thanks;
   – Matt Sanford / @mzsanford
       Twitter Dev

 On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote:



  Everyone just magically got logged out of my hahlo4 beta, which was
  working fine an hour ago, and now when they reauthorize its not
  sticking.

  OAuth login works fine, redirect back to hahlo4, but all api calls are
  returning 401 status codes.

  Saw mention in another topic regarding whether  twitter.com 
  orwww.twitter.com
  should be used when making api call, all my calls are currently using
 https://twitter.com

  Anyone else experiencing anything similar?

[twitter-dev] Re: How to insure that all tweets are retrieved in a search?

2009-07-09 Thread Scott Haneda




You are correct, you have to do 15 requests.  However,
you can cache the results in your end, so when you come
back, you are only getting the new stuff.


Thanks Scott.  I'm storing the results in a database on my server but
that doesn't stop the search from retrieving the same results
repetitively, because the search string/terms are still the same.

My problem is going to occur when thousands of people start tweeting
my promo codes every minute and I'm not able to retrieve all those
tweets because of the search API limitations.

If I'm limited to retrieving 1500 tweets every 6 minutes and people
post 1000 tweets every minute I need some way of retrieving the
missing 4500 tweets -- but apparently Twitter doesn't offer anything
even remotely close to this capability -- so I can see where it has a
long way to go before it's ready to support the kind of search
capabilities I need.



Have you read this:
http://apiwiki.twitter.com/Rate-limiting

Section on search rate limiting.  I do not believe there is a rate  
limit on search.  I am sure there is a very high limit, but you should  
be ok.  I would also suggest you get whitelisted, that bumps you up to  
20,000 request per hour I believe.


Further, you could make the users o-auth, in which case, the hit  
counts to them, not you.


You will still get stuck with the fact that search is a pretty broad  
thing, and not exacting, but you should be able to complete your  
searches in the amount you want.  I have seen apps that I know are  
using search on their back end, and they are not requiring auth by the  
user, and they are further pretty heavily hit.

--
Scott * If you contact me off list replace talklists@ with scott@ *

[twitter-dev] oauth seems to be broken (or down) since 4PM PST

2009-07-09 Thread goodtest


all of a sudden I am getting cannot authenticate

[twitter-dev] Re: oauth seems to be broken (or down) since 4PM PST


The problem is known, cf this thread, for example:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/39306c36ecc9cdb8
Matt has also updated the twitterapi account to let us know he was
working on it.

Arnaud.

On Jul 10, 1:56 am, goodtest goodtest...@gmail.com wrote:
 all of a sudden I am getting cannot authenticate

[twitter-dev] Re: Has something with OAuth changed?

2009-07-09 Thread dean.j.robinson


Awesome, thanks Matt, seems to be all working normally here too.

On Jul 10, 10:37 am, Matt Sanford m...@twitter.com wrote:
 Hi all,

      The issue has been fixed and from my testing it looks like things  
 are back to normal.

 Sorry for the disruption;
   – Matt Sanford / @mzsanford
       Twitter Dev

 On Jul 9, 2009, at 4:38 PM, dean.j.robinson wrote:



  Thanks for the super speedy response Matt.

  On Jul 10, 9:26 am, Matt Sanford m...@twitter.com wrote:
  Hi all,

       Some changes were just deployed and it looks like there may be a
  bug. I'm looking into it now … hold tight and I'll update you all  
  when
  I know more.

  Thanks;
    – Matt Sanford / @mzsanford
        Twitter Dev

  On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote:

  Everyone just magically got logged out of my hahlo4 beta, which was
  working fine an hour ago, and now when they reauthorize its not
  sticking.

  OAuth login works fine, redirect back to hahlo4, but all api calls  
  are
  returning 401 status codes.

  Saw mention in another topic regarding whether  twitter.com  
  orwww.twitter.com
  should be used when making api call, all my calls are currently  
  using
 https://twitter.com

  Anyone else experiencing anything similar?

[twitter-dev] Re: Has something with OAuth changed?

Still not working here.
http://twitter.com/oauth/request_token?oauth_consumer_key=***oauth_nonce=8995570oauth_signature_method=HMAC-SHA1oauth_timestamp=1247187445oauth_version=1.0oauth_signature=s9fxOOJhdVjLr3pacFF0uvBXxFE%3d;

...gets 401 Unauthorized.

On Jul 9, 8:53 pm, dean.j.robinson dean.j.robin...@gmail.com
wrote:
Awesome, thanks Matt, seems to be all working normally here too.

On Jul 10, 10:37 am, Matt Sanford m...@twitter.com wrote:

Hi all,

The issue has been fixed and from my testing it looks like things
are back to normal.

Sorry for the disruption;
– Matt Sanford / @mzsanford
Twitter Dev

On Jul 9, 2009, at 4:38 PM, dean.j.robinson wrote:

Thanks for the super speedy response Matt.

On Jul 10, 9:26 am, Matt Sanford m...@twitter.com wrote:
Hi all,

Some changes were just deployed and it looks like there may be a
bug. I'm looking into it now … hold tight and I'll update you all
when
I know more.

Thanks;
– Matt Sanford / @mzsanford
Twitter Dev

On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote:

Everyone just magically got logged out of my hahlo4 beta, which was
working fine an hour ago, and now when they reauthorize its not
sticking.

OAuth login works fine, redirect back to hahlo4, but all api calls
are
returning 401 status codes.

Saw mention in another topic regarding whether twitter.com
orwww.twitter.com
should be used when making api call, all my calls are currently
using
https://twitter.com

Anyone else experiencing anything similar?

[twitter-dev] Grouping API calls

2009-07-09 Thread Kevin Mesiab

Is there a faculty for grouping several API calls together to reduce round
trips?

-- 
Kevin Mesiab
CEO, Mesiab Labs L.L.C.

208-447-6016

http://www.mesiablabs.com
http://www.plsadvise.com

[twitter-dev] Re: Has something with OAuth changed?

2009-07-09 Thread johann


Hi,

Same here, we re getting 401 on every OAuth requests.

thanks,

johann

@romefort
CTO @ Seesmic

On Jul 9, 4:29 pm, Duane Roelands duane.roela...@gmail.com wrote:
 Yes, my application - which was working this morning - is now getting
 401s on every OAuth request.

 Something changed.

 On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
 wrote:

  Everyone just magically got logged out of my hahlo4 beta, which was
  working fine an hour ago, and now when they reauthorize its not
  sticking.

  OAuth login works fine, redirect back to hahlo4, but all api calls are
  returning 401 status codes.

  Saw mention in another topic regarding whether  twitter.com 
  orwww.twitter.com
  should be used when making api call, all my calls are currently 
  usinghttps://twitter.com

  Anyone else experiencing anything similar?

[twitter-dev] Native OAuth Flow PIN Checksum

2009-07-09 Thread Joshua Perry


I opened an issue for this if anyone is interested in starring it:
http://code.google.com/p/twitter-api/issues/detail?id=823

[twitter-dev] Re: Grouping API calls

Nope. They best you could do is make parallel calls.

Abraham

On Thu, Jul 9, 2009 at 20:00, Kevin Mesiab ke...@mesiablabs.com wrote:

 Is there a faculty for grouping several API calls together to reduce round
 trips?

 --
 Kevin Mesiab
 CEO, Mesiab Labs L.L.C.

 208-447-6016

 http://www.mesiablabs.com
 http://www.plsadvise.com




-- 
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] 400 error on create but not exists?

2009-07-09 Thread mikepuerto


Hi

I'm working on integrating the API into a script that just follows a
user. I have used 
http://twitter.com/friendships/exists.$format?user_a=$user_IDAauser_b=$user_IDB
and successfully gotten the response of true or false... but as soon
as I try using, http://twitter.com/friendships/create/$user_ID.xml I
get a 400 error. Would this be a rate limit issue? I'm using php with
curl... Is this a rate limit issue even though I can still use the
other method without error?

[twitter-dev] Re: 400 error on create but not exists?

What is the text that Twitter is sending back with the request?

2 recommendations:

Try
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentialsto
make sure the account credentials are correct.

Make sure you are doing a POST request and not a GET request.

Abraham

On Thu, Jul 9, 2009 at 20:36, mikepuerto mikepue...@gmail.com wrote:


 Hi

 I'm working on integrating the API into a script that just follows a
 user. I have used
 http://twitter.com/friendships/exists.$format?user_a=$user_IDAauser_b=$user_IDB
 and successfully gotten the response of true or false... but as soon
 as I try using, http://twitter.com/friendships/create/$user_ID.xml I
 get a 400 error. Would this be a rate limit issue? I'm using php with
 curl... Is this a rate limit issue even though I can still use the
 other method without error?




-- 
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Missing mentions #replies

2009-07-09 Thread David Bill


Hi,

We (@cotweet) have been seeing large amounts of missing tweets in
statuses/mentions for the past couple hours, and this problem is
apparent when comparing search.twitter.com to #replies on the
Twitter.com site as well.  Specific test case we are examining is
mentions for @cotweet, which have many hits in search for past hour,
but only two in mentions in past hour on website or via API.

Is this a known issue?

Thanks.

- David

[twitter-dev] Re: Missing mentions #replies


Some changes were deployed earlier today which broke OAuth
authentication.  They have since posted that it was fixed, but it's
not working for everybody.  It's possible that other things are broken
as well. :(

On Jul 9, 9:54 pm, David Bill davidb...@gmail.com wrote:
 Hi,

 We (@cotweet) have been seeing large amounts of missing tweets in
 statuses/mentions for the past couple hours, and this problem is
 apparent when comparing search.twitter.com to #replies on the
 Twitter.com site as well.  Specific test case we are examining is
 mentions for @cotweet, which have many hits in search for past hour,
 but only two in mentions in past hour on website or via API.

 Is this a known issue?

 Thanks.

 - David

[twitter-dev] Re: Missing mentions #replies

2009-07-09 Thread David Bill


Thanks Duane,

I believe this is a separate issue as it is apparent whether logging
in via OAuth, basic auth, or to the website directly.

- David

On Jul 9, 7:04 pm, Duane Roelands duane.roela...@gmail.com wrote:
 Some changes were deployed earlier today which broke OAuth
 authentication.  They have since posted that it was fixed, but it's
 not working for everybody.  It's possible that other things are broken
 as well. :(

 On Jul 9, 9:54 pm, David Bill davidb...@gmail.com wrote:

  Hi,

  We (@cotweet) have been seeing large amounts of missing tweets in
  statuses/mentions for the past couple hours, and this problem is
  apparent when comparing search.twitter.com to #replies on the
  Twitter.com site as well.  Specific test case we are examining is
  mentions for @cotweet, which have many hits in search for past hour,
  but only two in mentions in past hour on website or via API.

  Is this a known issue?

  Thanks.

  - David

[twitter-dev] Re: How to insure that all tweets are retrieved in a search?

2009-07-09 Thread David Fisher


Err, the Search API isn't limited to 150 requests per hour. It's much
higher than that. Much, but not unlimited.

As John said, read into the Search API more, and check into the
Streaming API as well.

It is certainly possible to get more than 1,500 results for a term,
but not by using simple paging. I've been able to pull 2M+ results for
a query before. It took 8 hours or so, but it worked. Read up more on
the Search API and you should be able to figure it out.

-David Fisher
http://WebecologyProject.org

On Jul 9, 8:16 pm, John Kalucki jkalu...@gmail.com wrote:
 First, I wouldn't expect that thousands are going to post your promo
 code
 per minute. That doesn't seem realistic.

 Second, in addition to the Search API, which is quite liberal, you can
 use
 the /track method on the Streaming API, which will return all keyword
 matches up to a certain limit with no other rate limiting. Contact us
 if the
 default limits are an issue.

 -John Kalucki
 Services, Twitter Inc.

 On Jul 9, 3:51 pm, owkaye owk...@gmail.com wrote:



   You are correct, you have to do 15 requests.  However,
   you can cache the results in your end, so when you come
   back, you are only getting the new stuff.

  Thanks Scott.  I'm storing the results in a database on my server but
  that doesn't stop the search from retrieving the same results
  repetitively, because the search string/terms are still the same.

  My problem is going to occur when thousands of people start tweeting
  my promo codes every minute and I'm not able to retrieve all those
  tweets because of the search API limitations.

  If I'm limited to retrieving 1500 tweets every 6 minutes and people
  post 1000 tweets every minute I need some way of retrieving the
  missing 4500 tweets -- but apparently Twitter doesn't offer anything
  even remotely close to this capability -- so I can see where it has a
  long way to go before it's ready to support the kind of search
  capabilities I need.

   Twitter has pretty good date handling, so you specify
   your last date, and pull forward from there.  You may
   even be able to get the last id of the last tweet you
   pulled, and just tell it to get you all the new ones.

  Yep, that's what I'm doing ... pulling from the records I haven't
  already retrieved based on the since_id value.

  But when the new tweets total more than 1500 in a short time, the
  excess tweets will get lost and there's no way to retrieve them --
  unless I run my searches from multiple servers to avoid Twitter's ip
  address limits -- and doing this would be a real kludge that I'm not
  tempted to bother with.

I'm building an app that uses the atom search API to retrieve recent
posts which contain a specific keyword.  The API docs say:

Clients may request up to 1,500 statuses via the page and rpp
parameters for the search method.

But this 1500 hits per search cannot be done in a single request
because of the rpp limit.  Instead I have to perform 15 sequential
requests in order to get only 100 items returned on each page ... for
a total of 1500 items.

This is certainly a good way to increase the server load, since 15
connections at 100 results each takes far more server resources than 1
connection returring all 1500 results.  Therefore I'm wondering if I'm
misunderstanding something here, or if this is really the only way I
can get the maximum of 1500 items via atom search?

   --
   Scott * If you contact me off list replace talklists@ with scott@ *

[twitter-dev] Re: Has something with OAuth changed?


On my side, things are back to normal since Matt announcement.

On the previous bug, the error message attached in the body was Could
not authenticate you. Are you receiving the same error message?

Arnaud.

On Jul 10, 1:34 am, johann romef...@gmail.com wrote:
 Hi,

 Same here, we re getting 401 on every OAuth requests.

 thanks,

 johann

 @romefort
 CTO @ Seesmic

 On Jul 9, 4:29 pm, Duane Roelands duane.roela...@gmail.com wrote:

  Yes, my application - which was working this morning - is now getting
  401s on every OAuth request.

  Something changed.

  On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
  wrote:

   Everyone just magically got logged out of my hahlo4 beta, which was
   working fine an hour ago, and now when they reauthorize its not
   sticking.

   OAuth login works fine, redirect back to hahlo4, but all api calls are
   returning 401 status codes.

   Saw mention in another topic regarding whether  twitter.com 
   orwww.twitter.com
   should be used when making api call, all my calls are currently 
   usinghttps://twitter.com

   Anyone else experiencing anything similar?

[twitter-dev] Re: Has something with OAuth changed?


I'm getting the same thing I was getting earlier: 401 Unauthorized

On Jul 9, 10:16 pm, Arnaud Meunier arnaud.meun...@twitoaster.com
wrote:
 On my side, things are back to normal since Matt announcement.

 On the previous bug, the error message attached in the body was Could
 not authenticate you. Are you receiving the same error message?

 Arnaud.

 On Jul 10, 1:34 am, johann romef...@gmail.com wrote:



  Hi,

  Same here, we re getting 401 on every OAuth requests.

  thanks,

  johann

  @romefort
  CTO @ Seesmic

  On Jul 9, 4:29 pm, Duane Roelands duane.roela...@gmail.com wrote:

   Yes, my application - which was working this morning - is now getting
   401s on every OAuth request.

   Something changed.

   On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
   wrote:

Everyone just magically got logged out of my hahlo4 beta, which was
working fine an hour ago, and now when they reauthorize its not
sticking.

OAuth login works fine, redirect back to hahlo4, but all api calls are
returning 401 status codes.

Saw mention in another topic regarding whether  twitter.com 
orwww.twitter.com
should be used when making api call, all my calls are currently 
usinghttps://twitter.com

Anyone else experiencing anything similar?

[twitter-dev] Re: 400 error on create but not exists?

2009-07-09 Thread Mike Puerto

Thanks so much... I was using GET instead of POST!

On Thu, Jul 9, 2009 at 9:45 PM, Abraham Williams 4bra...@gmail.com wrote:

 What is the text that Twitter is sending back with the request?

 2 recommendations:

 Try
 http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentialsto
  make sure the account credentials are correct.

 Make sure you are doing a POST request and not a GET request.

 Abraham


 On Thu, Jul 9, 2009 at 20:36, mikepuerto mikepue...@gmail.com wrote:


 Hi

 I'm working on integrating the API into a script that just follows a
 user. I have used
 http://twitter.com/friendships/exists.$format?user_a=$user_IDAauser_b=$user_IDB
 and successfully gotten the response of true or false... but as soon
 as I try using, http://twitter.com/friendships/create/$user_ID.xml I
 get a 400 error. Would this be a rate limit issue? I'm using php with
 curl... Is this a rate limit issue even though I can still use the
 other method without error?




 --
 Abraham Williams | Community Evangelist | http://web608.org
 Hacker | http://abrah.am | http://twitter.com/abraham
 Project | http://fireeagle.labs.poseurtech.com
 This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] OAuth appears to be working again


My gratitude to the Twitter crew for getting things resolved!

[twitter-dev] Re: Design of Invite Twitter friends

2009-07-09 Thread whoiskb


I had a similar question last night and found this thread that offered
some insight into the most efficient way to do something like this.
Here is the thread that discusses the best approach to get details on
all of the friends or followers of a user:

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8e255670186b52b3/54602c14899f42ff?lnk=gstq=list+friends#

On Jul 9, 12:20 pm, chachra sumit.chac...@gmail.com wrote:
 Hi,

 I'm trying to design a invite twitter friends feature (similar to
 the invite facebook friends concept).

 Sadly its not drop some code, like Facebook is... I'll have to develop
 from scratch. Wondering whats the most scalable way of doing this?
 Details:

 #1 By friends of course means followers since I can direct message
 them
 #2 The graph API call returns ID's, I would have to make $n api calls
 to get details on each of the $n id's right? Getting the users name,
 picture etc. ?
 #3 Then when the user selects users to invite, and presses submit
 then I'll have to make $m direct message calls ($m  $n)?

 Sounds like a lot of API calls to achieve something really simple.
 anyone have ways of doing this nicely? I would love to eliminate calls
 in #2 if possible.

 Cheers!
 Sumit

[twitter-dev] Re: Has something with OAuth changed?


Unauthorized probably referes to the official description of the
HTTP 401 Code. I was wondering what was the Twitter error message you
received (if any) in the body of your response. Could be something
like Invalid / used nonce or Invalid / expired token...

Arnaud.

On Jul 10, 4:18 am, Duane Roelands duane.roela...@gmail.com wrote:
 I'm getting the same thing I was getting earlier: 401 Unauthorized

 On Jul 9, 10:16 pm, Arnaud Meunier arnaud.meun...@twitoaster.com
 wrote:

  On my side, things are back to normal since Matt announcement.

  On the previous bug, the error message attached in the body was Could
  not authenticate you. Are you receiving the same error message?

  Arnaud.

  On Jul 10, 1:34 am, johann romef...@gmail.com wrote:

   Hi,

   Same here, we re getting 401 on every OAuth requests.

   thanks,

   johann

   @romefort
   CTO @ Seesmic

   On Jul 9, 4:29 pm, Duane Roelands duane.roela...@gmail.com wrote:

Yes, my application - which was working this morning - is now getting
401s on every OAuth request.

Something changed.

On Jul 9, 7:25 pm, dean.j.robinson dean.j.robin...@gmail.com
wrote:

 Everyone just magically got logged out of my hahlo4 beta, which was
 working fine an hour ago, and now when they reauthorize its not
 sticking.

 OAuth login works fine, redirect back to hahlo4, but all api calls are
 returning 401 status codes.

 Saw mention in another topic regarding whether  twitter.com 
 orwww.twitter.com
 should be used when making api call, all my calls are currently 
 usinghttps://twitter.com

 Anyone else experiencing anything similar?

[twitter-dev] Re: Changing domains for image hosting

2009-07-09 Thread roamlog


it seems there are some issues with the new pics server
the https is failed, please check it..

e.g. :
http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
is ok

but

https://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
is failed..

[twitter-dev] Re: Missing mentions #replies

2009-07-09 Thread David Bill


Appears to be resolved now.

On Jul 9, 7:07 pm, David Bill davidb...@gmail.com wrote:
 Thanks Duane,

 I believe this is a separate issue as it is apparent whether logging
 in via OAuth, basic auth, or to the website directly.

 - David

 On Jul 9, 7:04 pm, Duane Roelands duane.roela...@gmail.com wrote:

  Some changes were deployed earlier today which broke OAuth
  authentication.  They have since posted that it was fixed, but it's
  not working for everybody.  It's possible that other things are broken
  as well. :(

  On Jul 9, 9:54 pm, David Bill davidb...@gmail.com wrote:

   Hi,

   We (@cotweet) have been seeing large amounts of missing tweets in
   statuses/mentions for the past couple hours, and this problem is
   apparent when comparing search.twitter.com to #replies on the
   Twitter.com site as well.  Specific test case we are examining is
   mentions for @cotweet, which have many hits in search for past hour,
   but only two in mentions in past hour on website or via API.

   Is this a known issue?

   Thanks.

   - David

[twitter-dev] Twitter API: User's last login date

2009-07-09 Thread luisfigo


Hi guys,

Do you guys know if Twitter API provides a method for user's last
login date?

Thanks.

[twitter-dev] Re: Twitter API: User's last login date