[twitter-dev] post to twitter from iPhone app
Hello, Is there a library that does this with a nice user interface? Amir
Re: [twitter-dev] Re: Getting friends as usernames instead of user ids
unfortunately, yes. On Thu, Dec 24, 2009 at 12:12 PM, Michael wrote: > Ok, thanks! > > So, in the meantime you would say that the only way to do this is run > through all the ids, call http://twitter.com/users/show.xml on each > id, and parse out the ursername from the xml returned? > > > > On Dec 24, 2:52 pm, Raffi Krikorian wrote: > > we are working on releasing a "bulk lookup API" (i don't have a release > date > > on it yet), and you will be able to use that for this purpose. > > > > On Thu, Dec 24, 2009 at 10:31 AM, Michael wrote: > > > I am using thehttp://twitter.com/friends/ids.xml?screen_name=$username > > > method to get a list of friends for a user. However, the friends come > > > back as ids. Is there anyway I can convert these ids to their > > > usernames? > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Getting friends as usernames instead of user ids
Ok, thanks! So, in the meantime you would say that the only way to do this is run through all the ids, call http://twitter.com/users/show.xml on each id, and parse out the ursername from the xml returned? On Dec 24, 2:52 pm, Raffi Krikorian wrote: > we are working on releasing a "bulk lookup API" (i don't have a release date > on it yet), and you will be able to use that for this purpose. > > On Thu, Dec 24, 2009 at 10:31 AM, Michael wrote: > > I am using thehttp://twitter.com/friends/ids.xml?screen_name=$username > > method to get a list of friends for a user. However, the friends come > > back as ids. Is there anyway I can convert these ids to their > > usernames? > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Testing HTTP Response Codes
Done: http://code.google.com/p/twitter-api/issues/detail?id=1315 Well, assuming you have a wrapper library of some sort in your app, you could just set a property of that library from your unit tests that invoke that particular error code. For now, I've found it easiest just to 404 it and mangle the URL with some extra characters. Requires testing code in the library itself, but at least I can be sure. On Dec 24, 2:47 pm, Raffi Krikorian wrote: > please do - coincidentally, we were talking about something like the other > day. > > it is a catch-22, however - if you are doing a full test, then you would > have to pass a different parameter you would never pass in production, etc., > etc. > > > > > > On Wed, Dec 23, 2009 at 9:04 PM, Tim Dorr wrote: > > Well, as a recommendation, a parameter similar to > > suppress_response_codes would be very helpful for complete testing. > > invoke_response_code or something along those lines. I'll file an > > enhancement issue for it, though. > > > -Tim > > > On Dec 23, 10:47 pm, Raffi Krikorian wrote: > > > you can probably simulate certain error conditions (when we throw 404s > > and > > > the like), and you can probably force it to get to a rate limit error - > > but > > > a particular 500 error, no. > > > > On Wed, Dec 23, 2009 at 4:43 PM, Tim Dorr wrote: > > > > Is there a way to force Twitter's API to respond with a particular > > > > HTTP response code? I'd like to make sure that if there happens to be > > > > a 500 error, my app isn't going to crash/infinite loop/collapse into a > > > > black hole and consume the Earth. I can probably fake it in my app, > > > > but I wanted to test the full stack of things to be sure. > > > > -- > > > Raffi Krikorian > > > Twitter Platform Teamhttp://twitter.com/raffi > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] block exists problem
Hello, I am trying to execute the following API url: http://twitter.com/blocks/blocking/ids.json every time I hit this, I get : "Not Found". I also tried with the xml format, I used users who should have blocked ids. Any idea is appreciated. Thanks.
Re: [twitter-dev] Tweets with !, ', and other characters refused..
Make sure you are using UTF-8 and not a ISO-8859-x. Zac Bowling On Tue, Dec 22, 2009 at 9:49 PM, thetwitmaniac wrote: > Hi, > > I'm building a desktop twitter client and for some reason whenever I > try to post a tweet with an exclamation mark or apostrophe, the tweet > is rejected and I am presented with a request to provide login > credential for the Twitter API. > > Has anyone run into this issue or have any idea why this would occur? > > Thanks! >
Re: [twitter-dev] newRTs coming through Search API are missing retweeted_status->id
> its on the road map, but i don't have a date for it. Right on, just wanted to make sure it was on the radar. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- New political correctness is but old fascism writ large. -- Dr Digby James -
Re: [twitter-dev] newRTs coming through Search API are missing retweeted_status->id
hi cameron. its on the road map, but i don't have a date for it. On Wed, Dec 23, 2009 at 10:20 AM, Cameron Kaiser wrote: > When a newRT is found via the Search API, the tweet does not appear to have > any of the retweeted_status information. Is this going to be added on? > > -- > personal: > http://www.cameronkaiser.com/ -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * > ckai...@floodgap.com > -- God is Real, unless declared Integer. -- Stan Sieler > --- > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Getting friends as usernames instead of user ids
we are working on releasing a "bulk lookup API" (i don't have a release date on it yet), and you will be able to use that for this purpose. On Thu, Dec 24, 2009 at 10:31 AM, Michael wrote: > I am using the http://twitter.com/friends/ids.xml?screen_name=$username > method to get a list of friends for a user. However, the friends come > back as ids. Is there anyway I can convert these ids to their > usernames? > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Help - need location data for each tweet for a particular search without using a radius
hi - you can't, unfortunately. soon - we will be releasing the geo-hose ( http://www.slideshare.net/raffikrikorian/whats-happening-here) which will allow you to track locations, but, still no the entire world at one shot. On Thu, Dec 24, 2009 at 8:50 AM, seeta.g...@langland.co.uk < seeta.g...@langland.co.uk> wrote: > Does anyone know? > > I need help to create a twitter app, which does a twitter search like > http://search.twitter.com/search.atom?q=christmas, but I want the > location tag e.g. google:location to be returned in the xml doc so > that I can use it to position a marker on google maps. > > I know how to do this using a radius and the geocode, eg > > http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%2C2500km > but I don't want to be limited by the radius, i.e. any global > location. > > Thanks for your help. > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Testing HTTP Response Codes
please do - coincidentally, we were talking about something like the other day. it is a catch-22, however - if you are doing a full test, then you would have to pass a different parameter you would never pass in production, etc., etc. On Wed, Dec 23, 2009 at 9:04 PM, Tim Dorr wrote: > Well, as a recommendation, a parameter similar to > suppress_response_codes would be very helpful for complete testing. > invoke_response_code or something along those lines. I'll file an > enhancement issue for it, though. > > -Tim > > On Dec 23, 10:47 pm, Raffi Krikorian wrote: > > you can probably simulate certain error conditions (when we throw 404s > and > > the like), and you can probably force it to get to a rate limit error - > but > > a particular 500 error, no. > > > > On Wed, Dec 23, 2009 at 4:43 PM, Tim Dorr wrote: > > > Is there a way to force Twitter's API to respond with a particular > > > HTTP response code? I'd like to make sure that if there happens to be > > > a 500 error, my app isn't going to crash/infinite loop/collapse into a > > > black hole and consume the Earth. I can probably fake it in my app, > > > but I wanted to test the full stack of things to be sure. > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Getting friends as usernames instead of user ids
I am using the http://twitter.com/friends/ids.xml?screen_name=$username method to get a list of friends for a user. However, the friends come back as ids. Is there anyway I can convert these ids to their usernames?
[twitter-dev] Help - need location data for each tweet for a particular search without using a radius
Does anyone know? I need help to create a twitter app, which does a twitter search like http://search.twitter.com/search.atom?q=christmas, but I want the location tag e.g. google:location to be returned in the xml doc so that I can use it to position a marker on google maps. I know how to do this using a radius and the geocode, eg http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%2C2500km but I don't want to be limited by the radius, i.e. any global location. Thanks for your help.
[twitter-dev] Re: Cursoring: Addition of string-encoded equivalents of JSON cursor parameters starts 1/11/2010
Thanks ! It will help ! .-)
Best Wishes to all Twitter Api Team and all dev 'round here !
Jacopo
On 23 déc, 01:43, Wilhelm Bierbaum wrote:
> In response to complaints we've been receiving about cursor IDs being
> difficult to deal with because of their length (for example,
> JavaScript can't deal with them -- seehttp://bit.ly/cursors),
> we're adding string equivalents of next_cursor and previous cursor to
> those methods that return cursors when the JSON format is used.
>
> A detailed account of the problems with big numbers and JavaScript
> can be found athttp://bit.ly/tooManyNumbers.
>
> If you strictly parse your top-level returned JSON (which seems
> unlikely given the spirit of the standard), you may need to make
> some adjustments to your code.
>
> Where the JSON with cursor parameters used to look like
>
> {
> "users":[{}}, ...],
> "next_cursor":319261365477361289,
> "previous_cursor":0
> }
>
> it will now return equivalent string values for next_cursor and
> previous_cursor called next_cursor_str and previous_cursor_str,
> respectively:
>
> {
> "users":[{}}, ...],
> "next_cursor":319261365477361289,
> "next_cursor_str":"319261365477361289",
> "previous_cursor":0,
> "previous_cursor":"0"
> }
>
> We hope this helps out those of you who were previously experiencing
> trouble with cursors.
>
> If you have any questions or comments, please feel free to post them
> to twitter-development-talk.
>
> Thanks!
>
> --
> Wilhelm Bierbaum
> Twitter Platform Team
[twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
I agree with PJB. The previous announcements only said that the
pagination will be deprecated.
1.
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/41369cb133175d0f#
2.
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/52d4e68040d4ca45#
However, both of the announcements did not say that the API call
"without" page parameter to get
all IDs will be removed or replaced with cursor pagination.
The deprecation of this method is not being documented as PJB said.
On Dec 24, 5:00 pm, PJB wrote:
> Why hasn't this been announced before? Why does the API suggest
> something totally different? At the very least, can you please hold
> off on deprecation of this until 2/11/2010? This is a new API change.
>
> On Dec 23, 7:45 pm, Raffi Krikorian wrote:
>
>
>
> > yes - if you do not pass in cursors, then the API will behave as though you
> > requested the first cursor.
>
> > > Willhelm:
>
> > > Your announcement is apparently expanding the changeover from page to
> > > cursor in new, unannounced ways??
>
> > > The API documentation page says: "If the cursor parameter is not
> > > provided, all IDs are attempted to be returned, but large sets of IDs
> > > will likely fail with timeout errors."
>
> > > Yesterday you wrote: "Starting soon, if you fail to pass a cursor, the
> > > data returned will be that of the first cursor (-1) and the
> > > next_cursor and previous_cursor elements will be included."
>
> > > I can understand the need to swap from page to cursor, but was pleased
> > > that a single call was still available to return (or attempt to
> > > return) all friend/follower ids. Now you are saying that, in addition
> > > to the changeover from page to cursor, you are also getting rid of
> > > this?
>
> > > Can you please confirm/deny?
>
> > > On Dec 22, 4:13 pm, Wilhelm Bierbaum wrote:
> > > > We noticed that some clients are still calling social graph methods
> > > > without cursor parameters. We wanted to take time to make sure that
> > > > people were calling the updated methods which return data with cursors
> > > > instead of the old formats that do not.
>
> > > > As previously announced in September (http://bit.ly/46x1iL) and
> > > > November (http://bit.ly/3UQ0LU), the legacy data formats returned
> > > > as a result of calling social graph endpoints without a cursor
> > > > parameter are deprecated and will be removed.
>
> > > > These formats have been removed from the API wiki since September.
>
> > > > You should always pass a cursor parameter. Starting soon, if you fail
> > > > to pass a cursor, the data returned will be that of the first cursor
> > > > (-1) and the next_cursor and previous_cursor elements will be included.
>
> > > > If you aren't seeing next_cursor and previous_cursor in your results,
> > > > you are getting data back in the old format. You will need to adjust
> > > > your parser to handle the new format.
>
> > > > We're going to start assuming you want data in the new format
> > > > (users_list / users / user or id_list / ids / id) instead of the old
> > > > format (users / user or ids / id) regardless of your passing a cursor
> > > > parameter as of 1/11/2010.
>
> > > > * The old formats will no longer be returned after 1/11/2010.
> > > > * Start using the new formats now by passing the 'cursor' parameter.
>
> > > > To recap, the old endpoints at
>
> > > > /statuses/friends.xml
> > > > /statuses/followers.xml
>
> > > > returned
>
> > > >
> > > >
> > > >
> > > >
> > > >
>
> > > > or JSON like [{/*user record*/ /*, .../]
>
> > > > whereas
>
> > > > /statuses/friends.xml?cursor=n
> > > > /statuses/followers.xml?cursor=n
>
> > > > return data that looks like
>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 7128872798413429387
> > > > 0
> > > >
>
> > > > or, the JSON equivalent:
>
> > > > {"users":[{/*user record*/} /*, ...*/], "next_cursor":0,
> > > > "previous_cursor":0}
>
> > > > and the old endpoints at
>
> > > > /friends/ids.xml
> > > > /followers/ids.xml
>
> > > > returned data that looks like
>
> > > >
> > > > 1
> > > > 2
> > > > 3
> > > >
>
> > > > whereas
>
> > > > /friends/ids.xml?cursor=n
> > > > /followers/ids.xml?cursor=n
>
> > > > return data that looks like
>
> > > >
> > > >
> > > > 1
> > > > 2
> > > > 3
> > > >
> > > > 1288724293877798413
> > > > -1300794057949944903
> > > >
>
> > > > or, the JSON equivalent:
>
> > > > {"ids":[1, 2, 3], "next_cursor":0, "previous_cursor":0}
>
> > > > If you have any questions or comments, please feel free to post them
> > > > to twitter-development-talk.
>
> > > > Thanks!
>
> > > > --
> > > > Wilhelm Bierbaum
> > > > Twitter Platform Team
>
> > --
> > Raffi Krikorian
> > Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Tweets with !, ', and other characters refused..
hi duane, what language are u talking about ? anand anand On 12/23/09, Duane Roelands wrote: > > What language are you working in? Also, are you using an existing > library or writing your own? > > On Dec 23, 12:49 am, thetwitmaniac wrote: > > Hi, > > > > I'm building a desktop twitter client and for some reason whenever I > > try to post a tweet with an exclamation mark or apostrophe, the tweet > > is rejected and I am presented with a request to provide login > > credential for the Twitter API. > > > > Has anyone run into this issue or have any idea why this would occur? > > > > Thanks! >
[twitter-dev] Re: Testing HTTP Response Codes
Well, as a recommendation, a parameter similar to suppress_response_codes would be very helpful for complete testing. invoke_response_code or something along those lines. I'll file an enhancement issue for it, though. -Tim On Dec 23, 10:47 pm, Raffi Krikorian wrote: > you can probably simulate certain error conditions (when we throw 404s and > the like), and you can probably force it to get to a rate limit error - but > a particular 500 error, no. > > On Wed, Dec 23, 2009 at 4:43 PM, Tim Dorr wrote: > > Is there a way to force Twitter's API to respond with a particular > > HTTP response code? I'd like to make sure that if there happens to be > > a 500 error, my app isn't going to crash/infinite loop/collapse into a > > black hole and consume the Earth. I can probably fake it in my app, > > but I wanted to test the full stack of things to be sure. > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
+1 - I'm currently relying on retrieving a complete social graph when
no cursor is passed. Your announcing this change right around Xmas+new
years to take effect almost immediately thereafter...
On Dec 23, 2009, at 10:00 PM, PJB wrote:
Why hasn't this been announced before? Why does the API suggest
something totally different? At the very least, can you please hold
off on deprecation of this until 2/11/2010? This is a new API change.
On Dec 23, 7:45 pm, Raffi Krikorian wrote:
yes - if you do not pass in cursors, then the API will behave as
though you
requested the first cursor.
Willhelm:
Your announcement is apparently expanding the changeover from page
to
cursor in new, unannounced ways??
The API documentation page says: "If the cursor parameter is not
provided, all IDs are attempted to be returned, but large sets of
IDs
will likely fail with timeout errors."
Yesterday you wrote: "Starting soon, if you fail to pass a cursor,
the
data returned will be that of the first cursor (-1) and the
next_cursor and previous_cursor elements will be included."
I can understand the need to swap from page to cursor, but was
pleased
that a single call was still available to return (or attempt to
return) all friend/follower ids. Now you are saying that, in
addition
to the changeover from page to cursor, you are also getting rid of
this?
Can you please confirm/deny?
On Dec 22, 4:13 pm, Wilhelm Bierbaum wrote:
We noticed that some clients are still calling social graph methods
without cursor parameters. We wanted to take time to make sure that
people were calling the updated methods which return data with
cursors
instead of the old formats that do not.
As previously announced in September (http://bit.ly/46x1iL) and
November (http://bit.ly/3UQ0LU), the legacy data formats returned
as a result of calling social graph endpoints without a cursor
parameter are deprecated and will be removed.
These formats have been removed from the API wiki since September.
You should always pass a cursor parameter. Starting soon, if you
fail
to pass a cursor, the data returned will be that of the first
cursor
(-1) and the next_cursor and previous_cursor elements will be
included.
If you aren't seeing next_cursor and previous_cursor in your
results,
you are getting data back in the old format. You will need to
adjust
your parser to handle the new format.
We're going to start assuming you want data in the new format
(users_list / users / user or id_list / ids / id) instead of the
old
format (users / user or ids / id) regardless of your passing a
cursor
parameter as of 1/11/2010.
* The old formats will no longer be returned after 1/11/2010.
* Start using the new formats now by passing the 'cursor'
parameter.
To recap, the old endpoints at
/statuses/friends.xml
/statuses/followers.xml
returned
or JSON like [{/*user record*/ /*, .../]
whereas
/statuses/friends.xml?cursor=n
/statuses/followers.xml?cursor=n
return data that looks like
7128872798413429387
0
or, the JSON equivalent:
{"users":[{/*user record*/} /*, ...*/], "next_cursor":0,
"previous_cursor":0}
and the old endpoints at
/friends/ids.xml
/followers/ids.xml
returned data that looks like
1
2
3
whereas
/friends/ids.xml?cursor=n
/followers/ids.xml?cursor=n
return data that looks like
1
2
3
1288724293877798413
-1300794057949944903
or, the JSON equivalent:
{"ids":[1, 2, 3], "next_cursor":0, "previous_cursor":0}
If you have any questions or comments, please feel free to post
them
to twitter-development-talk.
Thanks!
--
Wilhelm Bierbaum
Twitter Platform Team
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Spurious SMS notifications
I've started getting new spurious SMS messages again. The latest set of messages started coming in yesterday evening. - h On Wed, Dec 9, 2009 at 21:14, Mark McBride wrote: > We believe we've addressed this issue. If you see any further SMSs or > tweets please let me know. > > On Wed, Dec 9, 2009 at 5:46 PM, Howard Siegel wrote: > > Just got my first errant SMS message today. This one is from someone > that I > > am following. > > > > - h > > > > On Wed, Dec 9, 2009 at 16:15, mccv wrote: > >> > >> Ok, thanks for the info. We have people working on this. > >> > >> On Dec 9, 3:51 pm, Howard Siegel wrote: > >> > I've been getting errant SMS messages from Twitter for a few days, > >> > though I > >> > have not received any today (as yet). I have turned on SMS only for > DMs > >> > and > >> > none of these were DMs to me. I have not yet actually verified that I > >> > am > >> > following all of the folks from whom I've gotten the errant SMSes > >> > though. > >> > > >> > - h > >> > > >> > > >> > > >> > On Wed, Dec 9, 2009 at 15:02, Kee Hinckley > wrote: > >> > > I am receiving spurious SMS notifications for tweets sent by people > I > >> > > am > >> > > following, but do not have notifications turned on for. These are > >> > > *not* > >> > > retweets, I've even asked a couple of the original senders to check > >> > > and see > >> > > if the item had been retweeted, and the answer was no. Furthermore, > I > >> > > only > >> > > have my account (@nazgul) set to receive text messages for about > four > >> > > users, > >> > > and none of them retweeted these messages. Possibly related, I have > a > >> > > friend > >> > > who turned off *all* phone notifications over a day ago, and is > still > >> > > getting random new text messages from people she follows but didn't > >> > > set to > >> > > send her notificationqs. > >> > > >> > > Examples: > >> > > >> > > I confirmed that these were not retweeted by anyone for whom I get > >> > > notifications (or in one case, by anyone at all). > >> > > >> > >http://twitter.com/stevegarfield/status/6463021810 > >> > >http://twitter.com/daddyclaxton/status/6463935419 > >> > > >> > > Others I haven't had a chance to investigate, but which it seems > >> > > highly > >> > > unlikely were retweeted by anyone who sends me notifications. > >> > >http://twitter.com/kevinmarks/status/6500306267 > >> > >http://twitter.com/stoweboyd/status/6497224194 > > > > > > > > -- >---Mark > > http://twitter.com/mccv >
