[twitter-dev] Re: Tweets with !, ', and other characters refused..
What language are you working in? Also, are you using an existing library or writing your own? On Dec 23, 12:49 am, thetwitmaniac alon.a.ta...@gmail.com 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] [Problem] since date or since_id is too old
This bug wasn't fixed? I have been look around the groups and found this link: http://code.google.com/p/twitter-api/issues/detail?id=742 My service try to execute this link: http://search.twitter.com/search?rpp=100lang=ptto=timtimportimtimsince_id=6566066234 and get this message 403 : since date or since_id is too old So, how I solve this problem? If this id is too old, how i know what id is valid after this? I hope some1 help me. Thank you.
[twitter-dev] Re: statuses/featured broken with api.twitter.com/1/ endpoint
I'd imagine it's unsupported as it's not listed on the API docs
On Dec 22, 3:25 am, Andrew Stone stone_des...@mac.com wrote:
http://api.twitter.com/1/statuses/featured.json
doesn't work - giving a 404:
{request:/1/statuses/featured.json,error:Not found}
but it's ancestor:
http://twitter.com/statuses/featured.json
work fines
(Paste those into a browser to verify)
Andrew Stone
Twitter / @twittelatorhttp://www.stone.com
got iPhone?
http://tinyurl.com/twitpro
http://tinyurl.com/intentionizer
http://tinyurl.com/gesture-buy
http://tinyurl.com/igraffiti
http://tinyurl.com/talkingpics
http://tinyurl.com/mobilemix
http://tinyurl.com/soundbite
http://tinyurl.com/icreated
http://tinyurl.com/pulsar-app
[twitter-dev] newRTs coming through Search API are missing retweeted_status-id
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 ---
[twitter-dev] API and web UI differ on access to protected users' friends
This seems inconsistent: The API docs (http://bit.ly/TVwXI) state that to successfully call /statuses/friends on a protected user, you must authenticate and be allowed to see the user. OTOH, twitter.com lets you see the friends/followers list of protected users if you're simply logged in - no need to be granted access by the user. Terry
Re: [twitter-dev] API and web UI differ on access to protected users' friends
hi - this is being tracked on the google code tracker (and owned by me). please feel free to star the issue! On Wed, Dec 23, 2009 at 11:23 AM, Terry Jones te...@jon.es wrote: This seems inconsistent: The API docs (http://bit.ly/TVwXI) state that to successfully call /statuses/friends on a protected user, you must authenticate and be allowed to see the user. OTOH, twitter.com lets you see the friends/followers list of protected users if you're simply logged in - no need to be granted access by the user. Terry -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] How can we change ownership of an app?
This has been asked before but not answered. How can we move ownership of an app to a different twitter user account? Thanks, Chris
[twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
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 wilh...@twitter.com 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
users type=array
user
!-- ... omitted ... --
/user
/users
or JSON like [{/*user record*/ /*, .../]
whereas
/statuses/friends.xml?cursor=n
/statuses/followers.xml?cursor=n
return data that looks like
users_list
users type=array
user
!-- ... omitted ... --
/user
/users
next_cursor7128872798413429387/next_cursor
previous_cursor0/previous_cursor
/users_list
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
ids
id1/id
id2/id
id3/id
/ids
whereas
/friends/ids.xml?cursor=n
/followers/ids.xml?cursor=n
return data that looks like
id_list
ids
id1/id
id2/id
id3/id
/ids
next_cursor1288724293877798413/next_cursor
previous_cursor-1300794057949944903/previous_cursor
/id_list
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
[twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
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. There was no reference in any of the previous announcements to deprecating this valuable ability. Is it now also doomed for the ash- heap, and we shall never get more than 5000 ids at a time with these calls? That was never indicated to be the case in the prior announcements, nor does the API documentation page hint at this new change...?!
[twitter-dev] Re: Where We're At With Location
I might look at swapping over to the reverse geocoder provided by geoapi.com as an alternative to the google maps api which has a tendency to give some weird results. On Dec 24, 9:04 am, Marcel Molina mar...@twitter.com wrote: For the last few months, the Platform team has been really excited about all the possibilities that open up when geo is added throughout our APIs. Recently, we've launched support for geo tagging tweets (http://bit.ly/4pFY77) as well as the imminent availability of a local trends API (http://bit.ly/12M84f). We're psyched about geo and today we have some big news. Twitter has acquired Mixer Labs, creators of GeoAPI (http://geoapi.com/). As Ev just said over on our main blog (http://bit.ly/88nZ6B), the team from Mixer Labs will be joining Twitter. We're currently looking at how to integrate the work Mixer Labs has done with the Twitter Platform to provide powerful new possibilities. We wanted to give everyone here a heads up on the good news. We look forward to supporting lots more geo functionality. Start your engines! -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
Re: [twitter-dev] How can we change ownership of an app?
On Thu, Dec 24, 2009 at 3:45 AM, chrisLiveFyre cbecker...@gmail.com wrote: This has been asked before but not answered. How can we move ownership of an app to a different twitter user account? Thanks, Chris I had the same issue. I just removed the app. Then add the same name in other account. Then I updated the tokens. It worked. -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
[twitter-dev] Testing HTTP Response Codes
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.
[twitter-dev] Re: How can we change ownership of an app?
But your users all have to reauthenticate against what is technically a new app in the system. And if you do anything offline from the user, you won't have access under the new OAuth key to their account. On Dec 23, 7:01 pm, shiplu shiplu@gmail.com wrote: On Thu, Dec 24, 2009 at 3:45 AM, chrisLiveFyre cbecker...@gmail.com wrote: This has been asked before but not answered. How can we move ownership of an app to a different twitter user account? Thanks, Chris I had the same issue. I just removed the app. Then add the same name in other account. Then I updated the tokens. It worked. -- Shiplu Mokaddim My talks,http://talk.cmyweb.net Follow me,http://twitter.com/shiplu SUST Programmers,http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
Re: [twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
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 wilh...@twitter.com 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
users type=array
user
!-- ... omitted ... --
/user
/users
or JSON like [{/*user record*/ /*, .../]
whereas
/statuses/friends.xml?cursor=n
/statuses/followers.xml?cursor=n
return data that looks like
users_list
users type=array
user
!-- ... omitted ... --
/user
/users
next_cursor7128872798413429387/next_cursor
previous_cursor0/previous_cursor
/users_list
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
ids
id1/id
id2/id
id3/id
/ids
whereas
/friends/ids.xml?cursor=n
/followers/ids.xml?cursor=n
return data that looks like
id_list
ids
id1/id
id2/id
id3/id
/ids
next_cursor1288724293877798413/next_cursor
previous_cursor-1300794057949944903/previous_cursor
/id_list
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 Team
http://twitter.com/raffi
Re: [twitter-dev] Testing HTTP Response Codes
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 timd...@gmail.com 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 Team http://twitter.com/raffi
Re: [twitter-dev] Re: How can we change ownership of an app?
there is no way to change ownership of an app. sorry. this is so that user doesn't have anything strange happen with the applications they have authorized with their accounts. On Wed, Dec 23, 2009 at 4:40 PM, Tim Dorr timd...@gmail.com wrote: But your users all have to reauthenticate against what is technically a new app in the system. And if you do anything offline from the user, you won't have access under the new OAuth key to their account. On Dec 23, 7:01 pm, shiplu shiplu@gmail.com wrote: On Thu, Dec 24, 2009 at 3:45 AM, chrisLiveFyre cbecker...@gmail.com wrote: This has been asked before but not answered. How can we move ownership of an app to a different twitter user account? Thanks, Chris I had the same issue. I just removed the app. Then add the same name in other account. Then I updated the tokens. It worked. -- Shiplu Mokaddim My talks,http://talk.cmyweb.net Follow me,http://twitter.com/shiplu SUST Programmers,http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest) -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn
[twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
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 ra...@twitter.com 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 wilh...@twitter.com 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
users type=array
user
!-- ... omitted ... --
/user
/users
or JSON like [{/*user record*/ /*, .../]
whereas
/statuses/friends.xml?cursor=n
/statuses/followers.xml?cursor=n
return data that looks like
users_list
users type=array
user
!-- ... omitted ... --
/user
/users
next_cursor7128872798413429387/next_cursor
previous_cursor0/previous_cursor
/users_list
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
ids
id1/id
id2/id
id3/id
/ids
whereas
/friends/ids.xml?cursor=n
/followers/ids.xml?cursor=n
return data that looks like
id_list
ids
id1/id
id2/id
id3/id
/ids
next_cursor1288724293877798413/next_cursor
previous_cursor-1300794057949944903/previous_cursor
/id_list
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
