[twitter-dev] Possible to increase DM count?

[olympyx]

I'm developing an application that is dependent on DMs. I realize that
whitelisting only affects/increases API requests.

Is it possible for specific accounts to have their DM allotment
increased? If so, how does one go about requesting this? If not, would
you please consider offering this?

Thanks!

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] getting authenticated user's rate-limit-using rest API.

[Rushikesh Bhanage]

Hi,
(Note: In my app, single white listed useraccount's requests are not
sufficient to complete particular task, so i need to switch from one account
to another without breaking operation, if previous A/C's hits got over. )
   In my case both the users are authenticated. Now problem is that how to
switch from one user to another, when  next user comes, he should come up
with it's hits for the operations, when previous user's hits got over. In
such situation how can i use rate_limit_status method.

Thank you in advance,

rishibhanage

On Mon, Mar 22, 2010 at 1:19 AM, Chris Thomson  wrote:

> The rate_limit_status method does not take a username as a parameter. All
> account methods act on the authenticating user's account (or in the case of
> an unauthenticated call, the requesting IP address). In order to get each
> other's rate limit information, you'll need to have both the user's
> authenticated as themselves.
>
> --
> Chris Thomson
>
> On Mar 21, 2010, at 8:01 AM, Rushikesh Bhanage wrote:
>
> Hi, there,
>  I am using rest api method in my app, in that, I have two users(i.e
> white-listed user accounts.) and need to get each user's account rate-limit
> request balance, I am using following URL to get request balance.
>
> ' 
> http://twitter.com/account/rate_limit_status/'.$unm.'.xml'.
>  Here $unm is user name passed through ratelimit() function .
>
>  Below is the code logic: (using cURL functions )
>
> [ function Checklimit()
> {
> for($i=0; $i<2; $i++)
> {
> $usrlimit =
> $this->ratelimit($this->u[$i]);  // ratelimit($unm)
> function will give array containing remaining hits.
> foreach($usrlimit as $key=>$val)
>  // $this->u[]  is the array used for fetching users with $i.
> {
> if($key == 'remaining-hits')
> {
> if($val != 0)
>
> {// here
> will return array element which is having hits.
>return
> $i; // here it doesn't
> come inside when value of ratelimit of first user comes to an end
>  }
>
> }
> }
>   // Actually here it goes to second user but does not get it's
> hits from api using ratelimit function. gets same 0 as like first user. It
> will return -1 when no user is having hits.
> }
> return -1;
> }
>
> ]
>
> Can I have some clue, please.
>
> Thank You in advance.
>
> with regards,
> rishibhanage.
>
>
>
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>
>
>  To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] how registered application user can follow the logged in user in rails

[bhagi]

Hi,
I am developing an application which is using twitter's apis for
authentication and twitting.
Through "/friendships/show?target_id" api logged in user can follow
the my application user but now i want to follow that user with my
registered application's user id.
So can anybody help me out for this.

How can we achieved these

Kindly help me out on this email.
bhagirath6...@gmail.com

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Importing contacts from Twitter to other site

[inderpreet.dbydx.com]

How can I export my twitter contacts to my site.

I have tried using some API, but in all of them I don't get the email
id of the user's contacts.

Is it possible to fetch the email id's of friends ??

If I need to export the email ids , is there an API available for the
same?




To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Streaming API , statuses/filter using track

[Kislay]

Hi ,

I would like to know whether the streaming API allows us to get older
tweets using filter with track predicate . Say , I have created a
filter using a certain set of keywords , and if the real time stream
does NOT contain any matching tweets , does it look in the older set
of tweets , or will I get no results till the stream content contains
tweets matching my keyword list ?

Thanks

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Google Maps / Twitter Mashup

[barkclark]

Hi, i was using this as a base code to workout a google maps / twitter
mashup for my website.

http://code.google.com/p/geo-api/source/browse/#svn/trunk/demos/twitter-neighborhoods

Problem is i do not what the neighbourhood function in it and only
want tweets from scotland. Every time i try to change the code to
remove the neighbourhood function it doesnt work. How do i do this?

I am a complete beginner at this.

Regards,
Simon

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Importing contacts from Twitter to other site

[Taylor Singletary]

Hi,

There's no way to retrieve email address for friends or otherwise in the
Twitter APIs.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Mon, Mar 22, 2010 at 6:16 AM, inderpreet.dbydx.com wrote:

> How can I export my twitter contacts to my site.
>
> I have tried using some API, but in all of them I don't get the email
> id of the user's contacts.
>
> Is it possible to fetch the email id's of friends ??
>
> If I need to export the email ids , is there an API available for the
> same?
>
>
>
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Streaming API , statuses/filter using track

[John Kalucki]

The Streaming API only serves current statuses and a short history,
controlled by the count parameter. Use one of the REST APIs to backfill.

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.


On Mon, Mar 22, 2010 at 5:26 AM, Kislay  wrote:

> Hi ,
>
> I would like to know whether the streaming API allows us to get older
> tweets using filter with track predicate . Say , I have created a
> filter using a certain set of keywords , and if the real time stream
> does NOT contain any matching tweets , does it look in the older set
> of tweets , or will I get no results till the stream content contains
> tweets matching my keyword list ?
>
> Thanks
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: Send Cyrillic character (OAuth)

[Taylor Singletary]

Hi Patrick,

The entry point to the app is in HomeController#index -- but there's not
much interesting stuff there.

The most interesting parts of OAuth are handled in both the
service_provider.rb model, the TheDanceController for the various OAuth
steps, and then the api_request.rb model for the individual API requests.

The tool relies on the OAuth ruby gem to do much of the work, but a number
of methods throughout the gem are overridden to provide extra debugging
information and additional options in the included oauth_ghostbuster plugin
you'll find in the vendor directory.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Sat, Mar 20, 2010 at 10:32 PM, Patrick Kennedy wrote:

> I'm new to Rails, and I am in process of studying this oauth example.
> Since there is no index file entry point at /public, where is the
> entry point of your oauth-dancer app?  This is a newbie question of
> Rails, but it looks like a fun app for the oauth dancing purposes, and
> I wanted to follow the logic.
>
> Thanks.  Pat
>
> On Thu, Mar 18, 2010 at 10:02 PM, Taylor Singletary
>  wrote:
> > Hi Z-13,
> > Using my OAuth Dancer tool ( http://bit.ly/oauth-dancer ), it's fairly
> easy
> > to setup a test scenario where you're posting a status with Cyrillic
> > characters, as long as you're using the UTF-8 representation.
> > While I don't know what specific code you'll need to write for Adobe AIR,
> > through the OAuth and HTTP request cycle, this is how it's represented:
> >
> > Full Request URI
> >
> > http://api.twitter.com/1/statuses/update.xml
> >
> > HTTP Method
> >
> > post
> >
> > Request Body
> >
> > status=тест+on+behalf+of+another
> >
> > Content-Type
> >
> > application/x-www-form-urlencoded
> >
> > Headers
> >
> > Content-Type: application/x-www-form-urlencoded
> >
> > The OAuth Dance
> >
> > Signature Base String
> >
> > POST&http%3A%2F%2Fapi.twitter.com
> %2F1%2Fstatuses%2Fupdate.xml&oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3Dn4uOLc7RCCf3PtKeEPpBiV1EdRXLyFAM72Q60J80w8s%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1268924223%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3D%25D1%2582%25D0%25B5%25D1%2581%25D1%2582%2520on%2520behalf%2520of%2520another
> >
> > Signature
> >
> > 6FcKffKploa26usTJuoADrtqp9Y=
> >
> > Authorization Header
> >
> > OAuth oauth_nonce="n4uOLc7RCCf3PtKeEPpBiV1EdRXLyFAM72Q60J80w8s",
> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1268924223",
> > oauth_consumer_key="ri8JxYK2ddwSV5xIUfNNvQ",
> > oauth_token="119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8",
> > oauth_signature="6FcKffKploa26usTJuoADrtqp9Y%3D", oauth_version="1.0"
> > Notice the encoding on the signature base string. Here's the response you
> > get back for a successful POST, which includes the special characters as
> > UTF-8 entities:
> >  
> >
> > 
> >   Thu Mar 18 14:57:04 + 2010
> >   10674682220
> >   тест on behalf of another
> >    > rel="nofollow">Crying Indian
> >   false
> >   
> >   
> >   false
> >   
> >   
> > 119476949
> > OAuth Dancer
> > oauth_dancer
> > San Francisco, CA
> > 
> >
> > 
> http://a3.twimg.com/profile_images/730275945/oauth-dancer_normal.jpg
> 
> > http://bit.ly/oauth-dancer
> > false
> > 9
> > C0DEED
> > 33
> > 0084B4
> > DDEEF6
> > C0DEED
> > 11
> > Wed Mar 03 19:37:35 + 2010
> > 0
> > 
> > 
> >
> > 
> http://a3.twimg.com/profile_background_images/80151733/oauth-dance.png
> 
> > true
> > false
> > false
> > false
> > false
> > 17
> > en
> > false
> >   
> >   
> >   
> >   
> >   
> > 
> >
> > Hope this helps you.
> > Taylor Singletary
> > Developer Advocate, Twitter
> > http://twitter.com/episod
> >
> >
> > On Thu, Mar 18, 2010 at 3:38 AM, Z-13  wrote:
> >>
> >> Who can help me?
> >
> >
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] new suggested users api

[Quy]

How do I page through this API call?

users/suggestions/category

Do we always just get the first page of suggested users for a
category?

Quy

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Best practice for personal alerts?

[MaartenB]

Hi Andrew,

Thanks for your response, afaik will the whitelist only affect the
number of API calls and not the number of updates you're allowed to
create.
Thanks for the DM tip that seems to work! However in this particular
case I'll prefer sending public readable tweets instead of private
DM's.

Maarten

On 21 mrt, 17:33, Andrew Badera  wrote:
> 1) Look into whitelisting.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: 401 Unauthorized

[Uladzimir Pashkevich]

Hi Mark,

Thanks for your reply! Screen name of the account is dmlreach. Please
see the request and 2 responses.

Request:

GET /1/account/verify_credentials.xml HTTP/1.1
Authorization: Basic 
Host: api.twitter.com

OK response headers:

Status: 200 OK
X-Transaction: 1269267625-43203-17004
X-RateLimit-Limit: 2
X-RateLimit-Remaining: 19998
X-Runtime: 0.06217
Pragma: no-cache
X-RateLimit-Class: api_whitelisted
X-Revision: DEV
X-RateLimit-Reset: 1269271222
Content-Length: 2730
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Content-Type: application/xml; charset=utf-8
Date: Mon, 22 Mar 2010 14:20:25 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
ETag: "1f0dfa0c9c82fe48bec465b9bad3793a"
Last-Modified: Mon, 22 Mar 2010 14:20:25 GMT
Set-Cookie: guest_id=1269267625681; path=/,lang=en;
path=/,_twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCOn2PoYnAToHaWQi
%250AJWIyNDJhNjNkZjI1MzVkZDBmMWE5ODExZWMxOGE1ZjRkIgpmbGFzaElDOidB
%250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
bbde5312124b201f3cead86cb3d7e2947579ab88; domain=.twitter.com; path=/
Server: hi
Vary: Accept-Encoding
Connection: close

401 response headers:

Status: 401 Unauthorized
X-Runtime: 0.00763
Content-Length: 155
Cache-Control: no-cache, max-age=1800
Content-Type: application/xml; charset=utf-8
Date: Mon, 22 Mar 2010 14:04:48 GMT
Set-Cookie: guest_id=1269266688016;
path=/,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBeoMIYnAToHaWQiJWE1ZjZhMDdjZDA5OWUy
%250AZjM1ZDFmMmY5Mzc1YWFjMTQ4IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
fcdae0e1bde0a38c30903e86171f6b7a26afa0d0; domain=.twitter.com; path=/
Server: hi
WWW-Authenticate: Basic realm="Twitter API"
Expires: Mon, 22 Mar 2010 14:34:47 GMT
Vary: Accept-Encoding
Connection: close


So, in response to the same request I got two different responses.
Both requests were made from the same server.

I would be very grateful if someone could help me with this issue.

On Mar 17, 7:29 pm, Mark McBride  wrote:
> Without more details it's tough to say.  Do you at least have the screen
> name of the account in question, and details on both the success and failure
> environments?
>
>   ---Mark
>
> http://twitter.com/mccv
>
> On Wed, Mar 17, 2010 at 1:39 AM, Uladzimir Pashkevich <
>
> v.pashkev...@gmail.com> wrote:
> > Does anyone has any ideas? Any help is really appreciated, because I
> > can't understand this kind of the API's behavior.
>
> > On Mar 12, 6:40 pm, Uladzimir Pashkevich 
> > wrote:
> > > Hi everyone,
>
> > > I am developing an application using Twitter API and I have
> > > encountered into a strange behavior connected with 401 error. I am
> > > using basic auth. When I run my application locally, it works just
> > > fine and I never get any 401 errors. However, when I run my
> > > application on another environment, I get 401 error in approximately
> > > 80% cases. I am completely sure that the credentials are correct.
>
> > > What makes this situation even more weird is that I am working with
> > > several accounts, and most of them work fine in both environments. I
> > > am experiencing problems only with one account. All accounts I work
> > > with are whitelisted, so rate limit should not be an issue here.
>
> > > I have no idea what may cause this behavior. Could you please explain
> > > me the possible reasons I am getting 401?
>
> > > Thanks,
> > > Uladzimir

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Why does changing this one char invalidate this message

[Oli]

Hi again Mark. I have just used realterm to connect instead of
hyperterminal (shows every char including hidden ones) and I have had
success with my first example, however I am still struggling to get
the full example working (I had tried to simplify to a working/non-
working example as much as possible). Could you give this a quick try
please?

POST http://twitter.com/statuses/update.json HTTP/1.1
Host: twitter.com
Authorization: Basic xxx
Content-type: application/x-www-form-urlencoded
Content-length: 47
Connection: Close

status=ALARM%3A+Test_Unit+t1%3A+35litres+2425+C

If you have success, could you let me know exactly how you have tested
this (software etc) so I can duplicate it?

I really appreciate your help and advice on this - It's one of the
final sticking problems of this project.

Many thanks

On Mar 19, 5:51 pm, Mark McBride  wrote:
> Now that I'm clear...
>
> 1) It works for me using telnet.  This may or may not be subtly different
> from hyperterminal.
> 2) Note that if you do this repeatedly with the same status text you'll get
> rejections due to duplicate tweets.  On twitter.com this returns a 200 with
> no response body.  You shouldn't be using this endpoint anyway, please use
> api.twitter.com instead.
>
>   ---Mark
>
> http://twitter.com/mccv
>
> On Fri, Mar 19, 2010 at 10:33 AM, Oli  wrote:
> > Hi Mark, thanks for your response but I think you may be mistaken.
>
> > In the first call, I do send 36 bytes I state prior to sending -
> > "status=ALAhM%3A+Test_Unit+t1%3A35tej"
> > In the second call, I do send the 35 bytes I state prior to sending -
> > "status=ALAhM%3A+Test_Unit+t1%3A35te"
>
> > Additionally, I am 100% sure there are no spaces at the end / other
> > chars that are hidden.
>
> > I am dealing with the raw socket and to rule out any software mishap I
> > have been testing manually using hyperterminal (winsock) to diagnose
> > the problem.
>
> > I'm at a dead end on this until somebody can figure out what I am
> > doing wrong / if there is genuinely a problem elsewhere. Thanks again
>
> > On Mar 19, 4:58 pm, Mark McBride  wrote:
> > > On to the real problem, are you using a library to make that POST
> > request,
> > > or raw sockets?  What is likely happening is you're telling the server to
> > > expect 36 bytes of info in the first call.  You send 35.  The server
> > waits
> > > and waits then hangs up.  In the second call you're telling the server to
> > > expect 35, you send 35, the server does it's deal, and everybody is
> > happy.
>
> > >   ---Mark
>
> > >http://twitter.com/mccv
>
> > > On Fri, Mar 19, 2010 at 9:55 AM, Mark McBride 
> > wrote:
> > > > Missed the part about the one letter change.  Clever!
>
> > > >   ---Mark
>
> > > >http://twitter.com/mccv
>
> > > > On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride  > >wrote:
>
> > > >> You'll almost certainly want to change the password on that account
> > > >> immediately, as the basic auth header is easily decrypted.
>
> > > >>   ---Mark
>
> > > >>http://twitter.com/mccv
>
> > > >> On Fri, Mar 19, 2010 at 9:20 AM, Oli  wrote:
>
> > > >>> Also worth noting: there was no error returned - it hung up after 3/4
> > > >>> seconds. If you connect to twitter.com port 80 using hyperterminal /
> > > >>> winsock, you can copy and paste (replacing the authorisation, and
> > > >>> enabling append line feeds onto line ends in hyperterminal options)
> > my
> > > >>> examples and see this for yourself.
>
> > > >>> Any other ideas? I would really appreciate any comments on this
> > issue.
>
> > > >>> On Mar 19, 3:16 pm, Oli  wrote:
> > > >>> > Hi there,
>
> > > >>> > I've just been playing about and have come across a curious bug (I
> > > >>> > have changed one letter of the hashcode) - connecting and sending
>
> > > >>> > POSThttp://twitter.com/statuses/update.jsonHTTP/1.1
> > > >>> > Host: twitter.com
> > > >>> > Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ==
> > > >>> > Content-type: application/x-www-form-urlencoded
> > > >>> > Content-length: 36
> > > >>> > Connection: Close
>
> > > >>> > status=ALAhM%3A+Test_Unit+t1%3A35tej
>
> > > >>> > DOESN'T WORK but
>
> > > >>> > POSThttp://twitter.com/statuses/update.jsonHTTP/1.1
> > > >>> > Host: twitter.com
> > > >>> > Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ==
> > > >>> > Content-type: application/x-www-form-urlencoded
> > > >>> > Content-length: 35
> > > >>> > Connection: Close
>
> > > >>> > status=ALAhM%3A+Test_Unit+t1%3A35te
>
> > > >>> > DOES - why is this?? Many thanks in advance
>
> > > >>> To unsubscribe from this group, send email to
> > twitter-development-talk+
> > > >>> unsubscribegooglegroups.com or reply to this email with the words
> > > >>> "REMOVE ME" as the subject.
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or

[twitter-dev] Geolocation says wrong town

[tux_advocate_hpu]

Last week, geolocation was OK, but today, it says the wrong town.

I am sending Lat/Long with my tweets... the exact same Lat/Long as
last week.  But now it says 'Jamestown, NC' instead of 'High Point,
NC'.

This is not good b/c our organization is called 'High Point
University' and it looks pretty bad to say 'Jamestown, NC'.

I am going to disable geolocation for now, but what happened?  Is
there a fix?

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Geolocation says wrong town

[tux_advocate_hpu]

I got this fixed.  I am now adding a 'place_id' to all my Tweets.  I
still do not know why this problem starting happening in the first
place...

I figured out the correct place_id using instructions from this page:
https://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-geo-reverse_geocode


On Mar 22, 11:18 am, tux_advocate_hpu  wrote:
> Last week, geolocation was OK, but today, it says the wrong town.
>
> I am sending Lat/Long with my tweets... the exact same Lat/Long as
> last week.  But now it says 'Jamestown, NC' instead of 'High Point,
> NC'.
>
> This is not good b/c our organization is called 'High Point
> University' and it looks pretty bad to say 'Jamestown, NC'.
>
> I am going to disable geolocation for now, but what happened?  Is
> there a fix?

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Open Source Project website

[IanQuigley]

Are you sure they check this forum for update requests? You might want
to email them directly. I did.

Ian

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: Why does changing this one char invalidate this message

[Mark McBride]

I tested this by

1) Replacing the basic auth header with my own
2) Opening a connection via telnet on OS X

  telnet twitter.com 80

3) Pasting in the sample
4) Looking at the response

And it works for me.  Note that if I do it a second time I get a 200 and an
empty response, as you're going to twitter.com instead of api.twitter.com.

  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 8:09 AM, Oli  wrote:

> Hi again Mark. I have just used realterm to connect instead of
> hyperterminal (shows every char including hidden ones) and I have had
> success with my first example, however I am still struggling to get
> the full example working (I had tried to simplify to a working/non-
> working example as much as possible). Could you give this a quick try
> please?
>
> POST http://twitter.com/statuses/update.json HTTP/1.1
> Host: twitter.com
> Authorization: Basic xxx
> Content-type: application/x-www-form-urlencoded
> Content-length: 47
> Connection: Close
>
> status=ALARM%3A+Test_Unit+t1%3A+35litres+2425+C
>
> If you have success, could you let me know exactly how you have tested
> this (software etc) so I can duplicate it?
>
> I really appreciate your help and advice on this - It's one of the
> final sticking problems of this project.
>
> Many thanks
>
> On Mar 19, 5:51 pm, Mark McBride  wrote:
> > Now that I'm clear...
> >
> > 1) It works for me using telnet.  This may or may not be subtly different
> > from hyperterminal.
> > 2) Note that if you do this repeatedly with the same status text you'll
> get
> > rejections due to duplicate tweets.  On twitter.com this returns a 200
> with
> > no response body.  You shouldn't be using this endpoint anyway, please
> use
> > api.twitter.com instead.
> >
> >   ---Mark
> >
> > http://twitter.com/mccv
> >
> > On Fri, Mar 19, 2010 at 10:33 AM, Oli  wrote:
> > > Hi Mark, thanks for your response but I think you may be mistaken.
> >
> > > In the first call, I do send 36 bytes I state prior to sending -
> > > "status=ALAhM%3A+Test_Unit+t1%3A35tej"
> > > In the second call, I do send the 35 bytes I state prior to sending -
> > > "status=ALAhM%3A+Test_Unit+t1%3A35te"
> >
> > > Additionally, I am 100% sure there are no spaces at the end / other
> > > chars that are hidden.
> >
> > > I am dealing with the raw socket and to rule out any software mishap I
> > > have been testing manually using hyperterminal (winsock) to diagnose
> > > the problem.
> >
> > > I'm at a dead end on this until somebody can figure out what I am
> > > doing wrong / if there is genuinely a problem elsewhere. Thanks again
> >
> > > On Mar 19, 4:58 pm, Mark McBride  wrote:
> > > > On to the real problem, are you using a library to make that POST
> > > request,
> > > > or raw sockets?  What is likely happening is you're telling the
> server to
> > > > expect 36 bytes of info in the first call.  You send 35.  The server
> > > waits
> > > > and waits then hangs up.  In the second call you're telling the
> server to
> > > > expect 35, you send 35, the server does it's deal, and everybody is
> > > happy.
> >
> > > >   ---Mark
> >
> > > >http://twitter.com/mccv
> >
> > > > On Fri, Mar 19, 2010 at 9:55 AM, Mark McBride 
> > > wrote:
> > > > > Missed the part about the one letter change.  Clever!
> >
> > > > >   ---Mark
> >
> > > > >http://twitter.com/mccv
> >
> > > > > On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride <
> mmcbr...@twitter.com
> > > >wrote:
> >
> > > > >> You'll almost certainly want to change the password on that
> account
> > > > >> immediately, as the basic auth header is easily decrypted.
> >
> > > > >>   ---Mark
> >
> > > > >>http://twitter.com/mccv
> >
> > > > >> On Fri, Mar 19, 2010 at 9:20 AM, Oli 
> wrote:
> >
> > > > >>> Also worth noting: there was no error returned - it hung up after
> 3/4
> > > > >>> seconds. If you connect to twitter.com port 80 using
> hyperterminal /
> > > > >>> winsock, you can copy and paste (replacing the authorisation, and
> > > > >>> enabling append line feeds onto line ends in hyperterminal
> options)
> > > my
> > > > >>> examples and see this for yourself.
> >
> > > > >>> Any other ideas? I would really appreciate any comments on this
> > > issue.
> >
> > > > >>> On Mar 19, 3:16 pm, Oli  wrote:
> > > > >>> > Hi there,
> >
> > > > >>> > I've just been playing about and have come across a curious bug
> (I
> > > > >>> > have changed one letter of the hashcode) - connecting and
> sending
> >
> > > > >>> > POSThttp://twitter.com/statuses/update.jsonHTTP/1.1
> > > > >>> > Host: twitter.com
> > > > >>> > Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ==
> > > > >>> > Content-type: application/x-www-form-urlencoded
> > > > >>> > Content-length: 36
> > > > >>> > Connection: Close
> >
> > > > >>> > status=ALAhM%3A+Test_Unit+t1%3A35tej
> >
> > > > >>> > DOESN'T WORK but
> >
> > > > >>> > POSThttp://twitter.com/statuses/update.jsonHTTP/1.1
> > > > >>> > Host: twitter.com
> > > > >>> > Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ==
> > > > 

Re: [twitter-dev] getting authenticated user's rate-limit-using rest API.

[Mark McBride]

Authenticate as the second user.

  ---Mark

http://twitter.com/mccv


On Sun, Mar 21, 2010 at 11:55 PM, Rushikesh Bhanage
wrote:

> Hi,
> (Note: In my app, single white listed useraccount's requests are not
> sufficient to complete particular task, so i need to switch from one account
> to another without breaking operation, if previous A/C's hits got over. )
>In my case both the users are authenticated. Now problem is that how to
> switch from one user to another, when  next user comes, he should come up
> with it's hits for the operations, when previous user's hits got over. In
> such situation how can i use rate_limit_status method.
>
> Thank you in advance,
>
> rishibhanage
>
> On Mon, Mar 22, 2010 at 1:19 AM, Chris Thomson  wrote:
>
>> The rate_limit_status method does not take a username as a parameter. All
>> account methods act on the authenticating user's account (or in the case of
>> an unauthenticated call, the requesting IP address). In order to get each
>> other's rate limit information, you'll need to have both the user's
>> authenticated as themselves.
>>
>>  --
>> Chris Thomson
>>
>> On Mar 21, 2010, at 8:01 AM, Rushikesh Bhanage wrote:
>>
>> Hi, there,
>>  I am using rest api method in my app, in that, I have two users(i.e
>> white-listed user accounts.) and need to get each user's account rate-limit
>> request balance, I am using following URL to get request balance.
>>
>> ' 
>> http://twitter.com/account/rate_limit_status/'.$unm.'.xml'.
>>  Here $unm is user name passed through ratelimit() function .
>>
>>  Below is the code logic: (using cURL functions )
>>
>> [ function Checklimit()
>> {
>> for($i=0; $i<2; $i++)
>> {
>> $usrlimit =
>> $this->ratelimit($this->u[$i]);  // ratelimit($unm)
>> function will give array containing remaining hits.
>> foreach($usrlimit as $key=>$val)
>>  // $this->u[]  is the array used for fetching users with $i.
>> {
>> if($key == 'remaining-hits')
>> {
>> if($val != 0)
>>
>> {// here
>> will return array element which is having hits.
>>return
>> $i; // here it doesn't
>> come inside when value of ratelimit of first user comes to an end
>>  }
>>
>> }
>> }
>>   // Actually here it goes to second user but does not get it's
>> hits from api using ratelimit function. gets same 0 as like first user. It
>> will return -1 when no user is having hits.
>> }
>> return -1;
>> }
>>
>> ]
>>
>> Can I have some clue, please.
>>
>> Thank You in advance.
>>
>> with regards,
>> rishibhanage.
>>
>>
>>
>>
>>  To unsubscribe from this group, send email to twitter-development-talk+
>> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
>> ME" as the subject.
>>
>>
>>  To unsubscribe from this group, send email to twitter-development-talk+
>> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
>> ME" as the subject.
>>
>
>  To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: Open Source Project website

[Mark McBride]

Done
  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 9:38 AM, IanQuigley  wrote:

> Are you sure they check this forum for update requests? You might want
> to email them directly. I did.
>
> Ian
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: 403 on statuses longer than 140 characters

[Mark McBride]

Complete is probably overly optimistic.  However for the case of when we
return 403s on status updates and how you can tell why we did so the
documentation is now more up to date.  Enjoy!

  ---Mark

http://twitter.com/mccv


On Fri, Mar 19, 2010 at 11:08 PM, Andy Freeman  wrote:

> I don't suppose that the API documentation will be updated and made
> complete
>
> On Mar 19, 9:52 am, Mark McBride  wrote:
> > Abraham is correct.  We only truncate text in the case of SMS tweets.  We
> > won't chop text off of tweets when posted via the API, however we will
> > shorten URLs if it will get the tweet to fit into 140 characters.
> >
> >   ---Mark
> >
> > http://twitter.com/mccv
> >
> >
> >
> > On Fri, Mar 19, 2010 at 8:52 AM, Abraham Williams <4bra...@gmail.com>
> wrote:
> > > The URLs might be shortened not the text of the status itself.
> >
> > > Abraham
> >
> > > On Thu, Mar 18, 2010 at 22:03, Andy Freeman 
> wrote:
> >
> > >> What in the return JSON tells us that you've shortened?
> >
> > >> For example, are you setting/returning "truncate"?  Are you returning
> > >> the shortened tweet in "status"?
> >
> > >> On Mar 18, 12:30 pm, Mark McBride  wrote:
> > >> > I should clarify.  Returning a 403 is what we do right now.  Later
> today
> > >> > (hopefully) we will correct the behavior to return a 200 in this
> case.
> > >>  So
> > >> > short story: we'll be doing what you want us to do.
> >
> > >> >   ---Mark
> >
> > >> >http://twitter.com/mccv
> >
> > >> > On Thu, Mar 18, 2010 at 11:57 AM, Dewald Pretorius
> > >> > wrote:
> >
> > >> > > In the announcement, Mark said, "...in the case that a long status
> can
> > >> > > be reduced to under 140 characters by shortening URLs.  In this
> case
> > >> > > we return a 403 but successfully create the status."
> >
> > >> > > Any chance that you can instead return a 200?
> >
> > >> > > Returning a 403 while you actually created the status will cause
> > >> > > confusion.- Hide quoted text -
> >
> > >> > - Show quoted text -
> >
> > >> To unsubscribe from this group, send email to
> twitter-development-talk+
> > >> unsubscribegooglegroups.com or reply to this email with the words
> "REMOVE
> > >> ME" as the subject.
> >
> > > --
> > > Abraham Williams | Community Advocate |http://abrah.am
> > > TwitterOAuth |http://github.com/abraham/twitteroauth
> > > This email is: [ ] shareable [x] ask first [ ] private.
> >
> > > To unsubscribe from this group, send email to twitter-development-talk+
> > > unsubscribegooglegroups.com or reply to this email with the words
> "REMOVE
> > > ME" as the subject.- Hide quoted text -
> >
> > - Show quoted text -
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: 401 Unauthorized

[Mark McBride]

Everything looks fine with your POST conversation.  Can you email directly
with more details?
1) What library/tool are you using to make your POSTs?
2) What are the OS/architectures you're running on in your different
environments?
3) Are there odd characters in the password? (could this be a character
encoding issue?)

These are shots in the dark.  We're not seeing this with other
users/environments that I know of.

  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 7:29 AM, Uladzimir Pashkevich <
v.pashkev...@gmail.com> wrote:

> Hi Mark,
>
> Thanks for your reply! Screen name of the account is dmlreach. Please
> see the request and 2 responses.
>
> Request:
>
> GET /1/account/verify_credentials.xml HTTP/1.1
> Authorization: Basic 
> Host: api.twitter.com
>
> OK response headers:
>
> Status: 200 OK
> X-Transaction: 1269267625-43203-17004
> X-RateLimit-Limit: 2
> X-RateLimit-Remaining: 19998
> X-Runtime: 0.06217
> Pragma: no-cache
> X-RateLimit-Class: api_whitelisted
> X-Revision: DEV
> X-RateLimit-Reset: 1269271222
> Content-Length: 2730
> Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
> check=0
> Content-Type: application/xml; charset=utf-8
> Date: Mon, 22 Mar 2010 14:20:25 GMT
> Expires: Tue, 31 Mar 1981 05:00:00 GMT
> ETag: "1f0dfa0c9c82fe48bec465b9bad3793a"
> Last-Modified: Mon, 22 Mar 2010 14:20:25 GMT
> Set-Cookie: guest_id=1269267625681; path=/,lang=en;
>
> path=/,_twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCOn2PoYnAToHaWQi
> %250AJWIyNDJhNjNkZjI1MzVkZDBmMWE5ODExZWMxOGE1ZjRkIgpmbGFzaElDOidB
> %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
> bbde5312124b201f3cead86cb3d7e2947579ab88; domain=.twitter.com; path=/
> Server: hi
> Vary: Accept-Encoding
> Connection: close
>
> 401 response headers:
>
> Status: 401 Unauthorized
> X-Runtime: 0.00763
> Content-Length: 155
> Cache-Control: no-cache, max-age=1800
> Content-Type: application/xml; charset=utf-8
> Date: Mon, 22 Mar 2010 14:04:48 GMT
> Set-Cookie: guest_id=1269266688016;
>
> path=/,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBeoMIYnAToHaWQiJWE1ZjZhMDdjZDA5OWUy
> %250AZjM1ZDFmMmY5Mzc1YWFjMTQ4IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
> %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
> fcdae0e1bde0a38c30903e86171f6b7a26afa0d0; domain=.twitter.com; path=/
> Server: hi
> WWW-Authenticate: Basic realm="Twitter API"
> Expires: Mon, 22 Mar 2010 14:34:47 GMT
> Vary: Accept-Encoding
> Connection: close
>
>
> So, in response to the same request I got two different responses.
> Both requests were made from the same server.
>
> I would be very grateful if someone could help me with this issue.
>
> On Mar 17, 7:29 pm, Mark McBride  wrote:
> > Without more details it's tough to say.  Do you at least have the screen
> > name of the account in question, and details on both the success and
> failure
> > environments?
> >
> >   ---Mark
> >
> > http://twitter.com/mccv
> >
> > On Wed, Mar 17, 2010 at 1:39 AM, Uladzimir Pashkevich <
> >
> > v.pashkev...@gmail.com> wrote:
> > > Does anyone has any ideas? Any help is really appreciated, because I
> > > can't understand this kind of the API's behavior.
> >
> > > On Mar 12, 6:40 pm, Uladzimir Pashkevich 
> > > wrote:
> > > > Hi everyone,
> >
> > > > I am developing an application using Twitter API and I have
> > > > encountered into a strange behavior connected with 401 error. I am
> > > > using basic auth. When I run my application locally, it works just
> > > > fine and I never get any 401 errors. However, when I run my
> > > > application on another environment, I get 401 error in approximately
> > > > 80% cases. I am completely sure that the credentials are correct.
> >
> > > > What makes this situation even more weird is that I am working with
> > > > several accounts, and most of them work fine in both environments. I
> > > > am experiencing problems only with one account. All accounts I work
> > > > with are whitelisted, so rate limit should not be an issue here.
> >
> > > > I have no idea what may cause this behavior. Could you please explain
> > > > me the possible reasons I am getting 401?
> >
> > > > Thanks,
> > > > Uladzimir
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Geolocation revisited

[Ken]

On Mar 22, 06:20 am, Raffi Krikorian  wrote:
>
>
> > So if a user enables geolocation on Twitter, but refuses geolocation
> > in Firefox, their location will not show when tweeting through the
> > web? Also, any such user of a moblie device would have to disable
> > transmission of geodata? If so, any links to the instructions for
> > doing that on various devices?
>
> We have a geolocation best practices document around that we hand off
> to developers - that details a recommended UX model that makes it
> clear how users should be presented with the choice to geolocate.

I guess you mean this page: 
http://apiwiki.twitter.com/Geotagging-API-Best-Practices

>
> So, in short, yes - your users would need to enable geo, but disable
> it in the browser.

cool, "Geo" is our app name

In our case, it is not the app that risks to disclose the user's
current location, unless that is the location they have deliberately
chosen to associate with their tweet. It is the act of enabling
geolocation in Twitter that could get them into trouble depending on
the device(s) or browser(s) they subsequently use to tweet. I guess
what I wish for is an API-specific geo-enable switch. Nothing to do
with tracking a user's current location, nothing that creeps anyone
out, nothing that requires elaborate warnings or disclaimers.

>
> that's the main reason we're doing it! It's all about context and
> relevancy!
>
>
> > I am just a bit surprised to find myself alone in promoting a use case
> > whereby arbitrary geo-metadata is manually assigned to a tweet in order
> > to enhance its searchability and interestingness.

Sure we agree on the benefits. Still, most of the discussion has
focused on automated geolocation. The best practices page is all about
that. But I want to tweet about the great shawarma I recently ate in
Amman and pinpoint it on a map, or say, we just issued a press release
on our project in Mongolia, or a social issue in a place I can't even
get a visa for, and I want to locate my tweet there! This is API-only
for now, not the browser- or device-based tweeting that I've seen
discussed.

On Mar 21, 10:04 pm, Raffi Krikorian  wrote:
> > The other day, when map pins and cute little maps began to appear with
> > our tweets, we thought that was very cool indeed and we began thinking
> > again about promoting this app. (Oddly, the geodata only shows when we
> > are logged in - maybe that will change..?)
>
> that's a bug that is being addressed.
>
> > In order for a user to geo-tweet using our app, they needed to have
> > "Enable geotagging" checked in their settings. This has since been
> > changed to "Add a location to your tweets". On a support page dated 12
> > November 2009 (which I suspect has been updated more recently),
> > Twitter states, "Twitter won't show any location information unless
> > you've opted-in to the feature, and have allowed your device or
> > browser to transmit your coordinates to us," but the part about the
> > device or browser does not seem to apply to to the use of third-party
> > apps like ours. On the same page Twitter says that "Tweet With Your
> > Location is only available in the United States" which again does not
> > appear to apply to users of third party browser apps. (We are not in
> > the US)
>
> a user needs to have "enable geotagging" on in order for them to send
> geotagged tweets from their account.  what i would possibly do is tell your
> users to turn on geotagging, but also just inform them what will happen on
> twitter.com.  the status quo hasn't really changed, except we have added
> some new features to twitter.com.  if your users aren't in the US, then, for
> now, they won't see any "add location" stuff to tweets.  they will
> eventually, and i think its more important to just explain to them that, by
> default, twitter.com won't expose precise coordinates -- but instead
> neighborhood information.
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] /filter question

[rob]

Quick question:

When consuming the Streaming API on the "Filter" endpoint can you
provide both the "track" and "follow" predicates?

ex: ?track=foo&follow=1234566

We would like to have a single user with elevated access for both the
"track" and "follow" roles and utilize a single connection.

Thanks,

Rob

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] /filter question

[Mark McBride]

You can.  However this will be a logical ORing of predicates.  So you'll get
all tweets from user 1234566, and all tweets with the keyword "foo"

  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 11:28 AM, rob  wrote:

> Quick question:
>
> When consuming the Streaming API on the "Filter" endpoint can you
> provide both the "track" and "follow" predicates?
>
> ex: ?track=foo&follow=1234566
>
> We would like to have a single user with elevated access for both the
> "track" and "follow" roles and utilize a single connection.
>
> Thanks,
>
> Rob
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Does users/search have a much lower limit? Blocked after 70 calls.

[raffi]

hi roy.

i just added a note to 
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users-search
that states that this endpoint is limited to 60 calls per hour.  hope
that helps!

On Mar 18, 4:14 am, Roy Rodenstein  wrote:
> Hi, I'm still having an issue from a couple of weeks ago.
> I am writing an app that searches for your LinkedIn contacts' names on
> Twitter, paginated to only 10 per page, and there are 10 Twitter API
> calls per page.
>
> I am whitelisted, and am printing out the rate limit left after each
> call, and it says Exceeded after only 70 calls.
>
> Here is the output starting from scratch after several hours of
> inactivity:
>
> how2startup Rate Limit Left: 2
> how2startup Rate Limit Left: 1
> ...
> how2startup Rate Limit Left: 19931
> how2startup Rate Limit Left: 19930
> /1/users/search.xml?q=John Rate limit exceeded.
>
> As you can see, everything is proceeding normally but out of the blue
> I'm blocked after just 70 calls.
>
> Ok here is the really strange part. I can *still* make calls to
> *other* authenticated methods.
> e.g. calls to direct_messages after this work just fine. Just not
> users/search.
>
> Is there a much lower limit to users/search, even for whitelisted
> apps? I do not see this at all in the documentation.
>
> Thanks for any guidance!
>
> Best,
> Roy

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Regarding Recent vs Most Popular parameters in Search api

[Jeffrey Greenberg]

I understand where your headed regarding 'search'... What i'd like is
that the default on the current search API be unchanged, so that it
still returns "recent" by default...  That way I don't have to change
my existing application: www.tweettronics.com to ensure it's adherence
to the current behavior.

ok?

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Announcing push.ly

[Chad Etzel]

Hi all,

I have recently launched http://push.ly/ - twitter mentions pushed to
your phone (and free)!

Right now it has iPhone integration with Tweetie, TweetDeck, and
Echofon. If you have written (or know of) other iPhone twitter clients
that have custom URI schemes that allow you to open the app from other
apps, please let me know so that I can support those as well.

Also, check it out and let me know what you think!

Thanks,
-Chad

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] OAuth Echo progress, next steps?

[Jaanus]

How is OAuth Echo going? What are the next steps? I would really like
to start posting pictures from @cremeapp to all sorts of places, and
also build my own serverside stuff, but it's all pending on Twitter's
next steps.

I guess there will be more news at Chirp but I won't be there and it's
still weeks away, so... nudge ;)


rgds,
Jaanus

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Search API fails with Chinese

[Irokez]

http://search.twitter.com/search.json?q=^_^&lang=en - works perfectly
http://search.twitter.com/search.json?q=^_^&lang=zh - Twitter search
has timed out
Is there a way to solve the problem?

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] How To: Test the upcoming Content-Type HTTP header change in advance

[Taylor Singletary]

Hey Everyone!

We wanted to let you all know that you can now opt-in to testing the Twitter
API setting the appropriate Content-Type header
to application/x-www-form-urlencoded on the OAuth-related token exchange
steps (request_token, access_token).

Some background: To date we've been returning the incorrect Content-Type in
our responses to these requests: we've been sending back text/html. To be in
agreement with the actual content we respond to you with, we want to
permanently change our Content-Type HTTP header to respond with
application/x-www-form-urlencoded starting on April 20th, 2010.

To test this in advance of April 20th, simply include an additional HTTP
header to your request_token and access_token requests:
"X-Twitter-Content-Type-Accept" and set it to
"application/x-www-form-urlencoded" -- when you send this HTTP header, we'll
correctly respond with a Content-Type header set to
"application/x-www-form-urlencoded"

If you're using the OAuth gem for Ruby, this can be easily included in your
@consumer.get_request_token and @consumer.get_access_token method calls like
so:

headers = { "X-Twitter-Content-Type-Accept" =>
"application/x-www-form-urlencoded"}

@request_token = @consumer.get_request_token({:oauth_callback =>
callback_url}, nil, headers)

@consumer.get_access_token(request_token, { :oauth_verifier =>
oauth_verifier}, headers)


Implementation in whatever library you're using should be trivial. Most
OAuth libraries should already properly handle the Content-Type response of
application/x-www-form-urlencoded since it's the "to-spec" representation of
responses.

Please let us know if you have any questions or concerns.

Thanks!

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Fri, Mar 12, 2010 at 5:21 PM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> We'll be correcting this on Monday instead of today, folks.
>
> Have a great weekend.
>
> Taylor
>
> On Friday, March 12, 2010, Taylor Singletary
>  wrote:
> > Hello Developers,
> >
> > Though it certainly would be more correct for us to properly set the
> > Content-Type HTTP header throughout the OAuth token acquisition
> > process to "application/x-www-form-urlencoded," it has caused some
> > issues with a number of applications. This afternoon we will restore
> > the original behavior of setting the Content-Type header to "text/
> > html".
> >
> > Being in compliance with the OAuth specification is important to us.
> > Consider our old behavior now on deprecation notice. In four weeks or
> > so we'll begin setting the Content-Type header correctly again. We'll
> > announce a more formal deprecation date within a week of deployment.
> >
> > We invite you to do the right thing with us.
> >
> > Thanks!
> >
> > Taylor
> > http://twitter.com/episod
> >
>
> --
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] 403 on duplicate post - when?

[Dewald Pretorius]

When is the change going live to return a 403 response code on a
duplicate post?

I'm still getting the old behavior. A 200 OK is returned with the
details of the latest successful tweet on the account.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] 403 on duplicate post - when?

[Mark McBride]

On api.twitter.com/1/statuses/update.json?

  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius  wrote:

> When is the change going live to return a 403 response code on a
> duplicate post?
>
> I'm still getting the old behavior. A 200 OK is returned with the
> details of the latest successful tweet on the account.
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: 403 on duplicate post - when?

[Dewald Pretorius]

Yes, I just tried it again.

URL: https://api.twitter.com/1/statuses/update.json

Headers:

Date: Mon, 22 Mar 2010 21:09:39 GMT
Server: hi
Status: 200 OK
X-Transaction: 1269292179-62279-30903
ETag: "05ef33cb30cec1cfa0c5887d4862c9df"
Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT
X-Runtime: 0.26340
Content-Type: application/json; charset=utf-8
Content-Length: 1274
Pragma: no-cache
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
Set-Cookie: guest_id=1269292179683; path=/
Set-Cookie: lang=en; path=/
Set-Cookie: [snipped]
Vary: Accept-Encoding
Connection: close

The  and  returned were the latest successful tweet, not the
duplicate text I was trying to post.

On Mar 22, 6:08 pm, Mark McBride  wrote:
> On api.twitter.com/1/statuses/update.json?
>
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius  wrote:
> > When is the change going live to return a 403 response code on a
> > duplicate post?
>
> > I'm still getting the old behavior. A 200 OK is returned with the
> > details of the latest successful tweet on the account.
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.- Hide quoted text -
>
> - Show quoted text -

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: 403 on duplicate post - when?

[Mark McBride]

I just tried it and got a 403.  Can you give me a screen name you're using,
the data posted, and the data returned?

  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius  wrote:

> Yes, I just tried it again.
>
> URL: https://api.twitter.com/1/statuses/update.json
>
> Headers:
>
> Date: Mon, 22 Mar 2010 21:09:39 GMT
> Server: hi
> Status: 200 OK
> X-Transaction: 1269292179-62279-30903
> ETag: "05ef33cb30cec1cfa0c5887d4862c9df"
> Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT
> X-Runtime: 0.26340
> Content-Type: application/json; charset=utf-8
> Content-Length: 1274
> Pragma: no-cache
> 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
> Set-Cookie: guest_id=1269292179683; path=/
> Set-Cookie: lang=en; path=/
> Set-Cookie: [snipped]
> Vary: Accept-Encoding
> Connection: close
>
> The  and  returned were the latest successful tweet, not the
> duplicate text I was trying to post.
>
> On Mar 22, 6:08 pm, Mark McBride  wrote:
> > On api.twitter.com/1/statuses/update.json?
> >
> >   ---Mark
> >
> > http://twitter.com/mccv
> >
> >
> >
> > On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius 
> wrote:
> > > When is the change going live to return a 403 response code on a
> > > duplicate post?
> >
> > > I'm still getting the old behavior. A 200 OK is returned with the
> > > details of the latest successful tweet on the account.
> >
> > > To unsubscribe from this group, send email to twitter-development-talk+
> > > unsubscribegooglegroups.com or reply to this email with the words
> "REMOVE
> > > ME" as the subject.- Hide quoted text -
> >
> > - Show quoted text -
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: 403 on duplicate post - when?

[Dewald Pretorius]

I will email the details to a...@twitter.com, so be on the look out for
a ticket from me.

On Mar 22, 6:27 pm, Mark McBride  wrote:
> I just tried it and got a 403.  Can you give me a screen name you're using,
> the data posted, and the data returned?
>
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius  wrote:
> > Yes, I just tried it again.
>
> > URL:https://api.twitter.com/1/statuses/update.json
>
> > Headers:
>
> > Date: Mon, 22 Mar 2010 21:09:39 GMT
> > Server: hi
> > Status: 200 OK
> > X-Transaction: 1269292179-62279-30903
> > ETag: "05ef33cb30cec1cfa0c5887d4862c9df"
> > Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT
> > X-Runtime: 0.26340
> > Content-Type: application/json; charset=utf-8
> > Content-Length: 1274
> > Pragma: no-cache
> > 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
> > Set-Cookie: guest_id=1269292179683; path=/
> > Set-Cookie: lang=en; path=/
> > Set-Cookie: [snipped]
> > Vary: Accept-Encoding
> > Connection: close
>
> > The  and  returned were the latest successful tweet, not the
> > duplicate text I was trying to post.
>
> > On Mar 22, 6:08 pm, Mark McBride  wrote:
> > > On api.twitter.com/1/statuses/update.json?
>
> > >   ---Mark
>
> > >http://twitter.com/mccv
>
> > > On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius 
> > wrote:
> > > > When is the change going live to return a 403 response code on a
> > > > duplicate post?
>
> > > > I'm still getting the old behavior. A 200 OK is returned with the
> > > > details of the latest successful tweet on the account.
>
> > > > To unsubscribe from this group, send email to twitter-development-talk+
> > > > unsubscribegooglegroups.com or reply to this email with the words
> > "REMOVE
> > > > ME" as the subject.- Hide quoted text -
>
> > > - Show quoted text -
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.- Hide quoted text -
>
> - Show quoted text -

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: 403 on duplicate post - when?

[Dewald Pretorius]

Ticket #915557

On Mar 22, 6:27 pm, Mark McBride  wrote:
> I just tried it and got a 403.  Can you give me a screen name you're using,
> the data posted, and the data returned?
>
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius  wrote:
> > Yes, I just tried it again.
>
> > URL:https://api.twitter.com/1/statuses/update.json
>
> > Headers:
>
> > Date: Mon, 22 Mar 2010 21:09:39 GMT
> > Server: hi
> > Status: 200 OK
> > X-Transaction: 1269292179-62279-30903
> > ETag: "05ef33cb30cec1cfa0c5887d4862c9df"
> > Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT
> > X-Runtime: 0.26340
> > Content-Type: application/json; charset=utf-8
> > Content-Length: 1274
> > Pragma: no-cache
> > 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
> > Set-Cookie: guest_id=1269292179683; path=/
> > Set-Cookie: lang=en; path=/
> > Set-Cookie: [snipped]
> > Vary: Accept-Encoding
> > Connection: close
>
> > The  and  returned were the latest successful tweet, not the
> > duplicate text I was trying to post.
>
> > On Mar 22, 6:08 pm, Mark McBride  wrote:
> > > On api.twitter.com/1/statuses/update.json?
>
> > >   ---Mark
>
> > >http://twitter.com/mccv
>
> > > On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius 
> > wrote:
> > > > When is the change going live to return a 403 response code on a
> > > > duplicate post?
>
> > > > I'm still getting the old behavior. A 200 OK is returned with the
> > > > details of the latest successful tweet on the account.
>
> > > > To unsubscribe from this group, send email to twitter-development-talk+
> > > > unsubscribegooglegroups.com or reply to this email with the words
> > "REMOVE
> > > > ME" as the subject.- Hide quoted text -
>
> > > - Show quoted text -
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.- Hide quoted text -
>
> - Show quoted text -

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] /filter question

[John Kalucki]

However, the roles system currently does not allow elevated access for
multiple parameters. On the same account, you can get a track elevation or a
follow elevation, but not both. In this rare case, we'll just have to
maintain a second connection with a second account name.

Note that follow is not rate limited -- so if you only need to follow a
small number of users, elevated track access will give you what you need.

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.


On Mon, Mar 22, 2010 at 11:39 AM, Mark McBride  wrote:

> You can.  However this will be a logical ORing of predicates.  So you'll
> get all tweets from user 1234566, and all tweets with the keyword "foo"
>
>   ---Mark
>
> http://twitter.com/mccv
>
>
> On Mon, Mar 22, 2010 at 11:28 AM, rob  wrote:
>
>> Quick question:
>>
>> When consuming the Streaming API on the "Filter" endpoint can you
>> provide both the "track" and "follow" predicates?
>>
>> ex: ?track=foo&follow=1234566
>>
>> We would like to have a single user with elevated access for both the
>> "track" and "follow" roles and utilize a single connection.
>>
>> Thanks,
>>
>> Rob
>>
>> To unsubscribe from this group, send email to twitter-development-talk+
>> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
>> ME" as the subject.
>>
>
>  To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Almost real time

[Alberty Pascal]

Hi all,

while it's not possible to use AND search predicate in filter
streaming, how it could be possible to get back "almost real time"
search results ?

My goal is to be sure that I got all the tweets for a complex search
as fast as possible.

Get a small amount (rpp) of tweets very often (every 10 seconds ?) ?
Work with pagination ? How to be sure that I got every tweets ?

Thanks

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Wrong User ID for a reply

[Vikas]

Hi,

 I am trying to fetch the User ID to include in the Reply field and it
fetches the correct user ID if you are following the person and some
wrong User ID if you are just replying to a Tweet from the Search
topics. Has anyone seen this kind of behavior and what could possibly
be wrong here? I appreciate the help.

Thanks
Vikas

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Wrong User ID for a reply

[S Wang]

>From the API documentation: 
>http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search

Warning:  The user ids in the Search API are different from those in
the REST API (about the two APIs). This defect is being tracked by
Issue 214. This means that the to_user_id  and from_user_id field vary
from the actualy user id on Twitter.com. Applications will have to
perform a screen name-based lookup with the users/show method to get
the correct user id if necessary.
- Shuan

On Mar 22, 4:05 pm, Vikas  wrote:
> Hi,
>
>  I am trying to fetch the User ID to include in the Reply field and it
> fetches the correct user ID if you are following the person and some
> wrong User ID if you are just replying to a Tweet from the Search
> topics. Has anyone seen this kind of behavior and what could possibly
> be wrong here? I appreciate the help.
>
> Thanks
> Vikas

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Search API fails with Chinese

[S Wang]

Pretty odd, I am able to use curl to get 
http://search.twitter.com/search.json?q=^_^&lang=zh
but have the same problem as you fetching it through Firefox/Safari.

On Mar 22, 12:51 pm, Irokez  wrote:
> http://search.twitter.com/search.json?q=^_^&lang=en - works 
> perfectlyhttp://search.twitter.com/search.json?q=^_^&lang=zh - Twitter search
> has timed out
> Is there a way to solve the problem?

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Almost real time

[John Kalucki]

Pick the lowest frequency term to track upon, then post-filter on your end.
Repeated automated searches should not be run against search.twitter.com

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.


On Mon, Mar 22, 2010 at 3:30 PM, Alberty Pascal wrote:

> Hi all,
>
> while it's not possible to use AND search predicate in filter
> streaming, how it could be possible to get back "almost real time"
> search results ?
>
> My goal is to be sure that I got all the tweets for a complex search
> as fast as possible.
>
> Get a small amount (rpp) of tweets very often (every 10 seconds ?) ?
> Work with pagination ? How to be sure that I got every tweets ?
>
> Thanks
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Search API fails with Chinese

[twitterdoug]

This is most likely because there are extremely few results in chinese
that match the query.

Right now Twitter Search handles lang queries in a relatively
inefficient way, so that queries for common terms that match extremely
few results may time out. We can (and will) make this better, but the
point is that you probably wouldn't have gotten many, if any, results
for this query in any case.

d

On Mar 22, 12:51 pm, Irokez  wrote:
> http://search.twitter.com/search.json?q=^_^&lang=en - works 
> perfectlyhttp://search.twitter.com/search.json?q=^_^&lang=zh - Twitter search
> has timed out
> Is there a way to solve the problem?

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] public_timeline

[Josh Roesslein]

I thought twitter was reconsidering keeping public timeline around.
Not sure if there has been a final verdict yet.

Josh

On Sun, Mar 21, 2010 at 4:09 AM, Patrick  wrote:

> Since pubic_timeline is not going to be deprecated, and since I am
> using epiTwitter for oAuth, how should I display public_timeline
> *before* user logs in?
>
> I want to sprouse up the logon page, and some public_timeline tweets
> would be perfect.  As I don't have an oAuth token to setToken( ) and
> make calls thru epiTwitter, is it okay to use basic auth type ideas
> for the public_timeline tweets as a good opener?
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] public_timeline

[Patrick Kennedy]

Yes, it was announced here that they're keeping it.  Anyways, a cURL
request should be perfect for public_timeline tweets.

On Tue, Mar 23, 2010 at 7:44 AM, Josh Roesslein  wrote:
> I thought twitter was reconsidering keeping public timeline around.
> Not sure if there has been a final verdict yet.
> Josh
>
> On Sun, Mar 21, 2010 at 4:09 AM, Patrick  wrote:
>>
>> Since pubic_timeline is not going to be deprecated, and since I am
>> using epiTwitter for oAuth, how should I display public_timeline
>> *before* user logs in?
>>
>> I want to sprouse up the logon page, and some public_timeline tweets
>> would be perfect.  As I don't have an oAuth token to setToken( ) and
>> make calls thru epiTwitter, is it okay to use basic auth type ideas
>> for the public_timeline tweets as a good opener?
>>
>> To unsubscribe from this group, send email to
>> twitter-development-talk+unsubscribegooglegroups.com or reply to this email
>> with the words "REMOVE ME" as the subject.
>
> To unsubscribe from this group, send email to
> twitter-development-talk+unsubscribegooglegroups.com or reply to this email
> with the words "REMOVE ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Bulk User Relationship Lookup?

[Orian Marx (@orian)]

The bulk users/lookup call recently added to the API is a great new
tool for developers. This call would become even more useful with a
corresponding bulk lookup for user relationships. Are there any plans
for this?

Also, I'm assuming that the  and  nodes
returned in the user objects of the users/lookup call should be
considered unreliable as is stated for users/show.

Thanks,
@orian

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Bulk User Relationship Lookup?

[Abraham Williams]

I provide a simple API that returns common friends and follower of two
specific Twitter users. It currently works for the 5000 most recent
(although soon to be increasing) and only on public accounts.

http://github.com/abraham/intersect/blob/master/README

Abraham

On Mon, Mar 22, 2010 at 19:41, Orian Marx (@orian) wrote:

> The bulk users/lookup call recently added to the API is a great new
> tool for developers. This call would become even more useful with a
> corresponding bulk lookup for user relationships. Are there any plans
> for this?
>
> Also, I'm assuming that the  and  nodes
> returned in the user objects of the users/lookup call should be
> considered unreliable as is stated for users/show.
>
> Thanks,
> @orian
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>



-- 
Abraham Williams | Community Advocate | http://abrah.am
TwitterOAuth | http://github.com/abraham/twitteroauth
This email is: [ ] shareable [x] ask first [ ] private.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Open Source Project website

[Ricky]

@Ian: I think we have our answer.

@Mark: Thanks!

Ricky

On Mar 22, 1:15 pm, Mark McBride  wrote:
> Done
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, Mar 22, 2010 at 9:38 AM, IanQuigley  wrote:
> > Are you sure they check this forum for update requests? You might want
> > to email them directly. I did.
>
> > Ian
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] Re: Open Source Project website

[Ricky]

@Mark: Sorry to bother you a second time, but you missed the link on
the open source page. http://apiwiki.twitter.com/Open+source#NET

Thanks again,
Ricky

On Mar 22, 1:15 pm, Mark McBride  wrote:
> Done
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, Mar 22, 2010 at 9:38 AM, IanQuigley  wrote:
> > Are you sure they check this forum for update requests? You might want
> > to email them directly. I did.
>
> > Ian
>
> > To unsubscribe from this group, send email to twitter-development-talk+
> > unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> > ME" as the subject.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: Open Source Project website

[Mark McBride]

Ok, got that one too.

  ---Mark

http://twitter.com/mccv


On Mon, Mar 22, 2010 at 9:32 PM, Ricky  wrote:

> @Mark: Sorry to bother you a second time, but you missed the link on
> the open source page. http://apiwiki.twitter.com/Open+source#NET
>
> Thanks again,
> Ricky
>
> On Mar 22, 1:15 pm, Mark McBride  wrote:
> > Done
> >   ---Mark
> >
> > http://twitter.com/mccv
> >
> >
> >
> > On Mon, Mar 22, 2010 at 9:38 AM, IanQuigley  wrote:
> > > Are you sure they check this forum for update requests? You might want
> > > to email them directly. I did.
> >
> > > Ian
> >
> > > To unsubscribe from this group, send email to twitter-development-talk+
> > > unsubscribegooglegroups.com or reply to this email with the words
> "REMOVE
> > > ME" as the subject.
>
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.