[twitter-dev] Re: Search with multiple terms
I did not see the solution for multiple words. It is clear that for single words it is: this OR that becomes ors=this+that I did not see the solution for this sentence OR these words On May 11, 8:13 pm, Matt Harris wrote: > Hi Adrian, > > Check out our guide on how to use the Search API: > http://dev.twitter.com/pages/using_search > > It includes information about how to do this and other types of queries. > > Best, > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > On Wed, May 11, 2011 at 8:50 AM, Adrian wrote: > > Is it possible to do a search for multiple words that belong together > > combined with the OR operator? > > > For example if I want to capture all tweets for "The Bachelor" > > including people who use hashtags, I would like the query to look > > something like: > > > the bachelor or thebachelor > > > on Twitter search this is translated as: > > > ors=the+bachelor+thebachelor > > > which is clearly wrong. > > > I have tried it many ways now but seem to fail constantly. Any > > suggestions? > > > -- > > Twitter developer documentation and resources:https://dev.twitter.com/doc > > API updates via Twitter:https://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >https://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >https://groups.google.com/forum/#!forum/twitter-development-talk- Hide > >quoted text - > > - Show quoted text - -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Search with multiple terms
Is it possible to do a search for multiple words that belong together combined with the OR operator? For example if I want to capture all tweets for "The Bachelor" including people who use hashtags, I would like the query to look something like: the bachelor or thebachelor on Twitter search this is translated as: ors=the+bachelor+thebachelor which is clearly wrong. I have tried it many ways now but seem to fail constantly. Any suggestions? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: users/lookup returns duplicates, missing records for valid users
Hey guys, I'm glad to report that, as of 7:00 PM (UTC), the problem seems to have disappeared :) No more duplicates, I'm consistently getting back exactly 100 unique users for every 100 that I request. Thanks for finally getting to this! Cheers, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
I can confirm that this happens whether the lookup is by screen_name or id. Incidentally, any progress on Twitter's side? Way over a month now, and it only seems to be getting worse. Cheers, Adrian On Tue, Mar 22, 2011 at 1:18 AM, Nischal Shetty wrote: > Anything on this? It's been quite some time and user lookup I believe would > be used by a lot of apps. > > -N > > > On 16 March 2011 05:46, Taylor Singletary wrote: > >> Still working on it, unfortunately. No ETA for a fix yet. I know it's an >> aggravating bug for anyone who runs into it. Thanks for being patient. >> >> Taylor >> >> >> On Mar 15, 2011, at 5:09 PM, Adrian Petrescu wrote: >> >> Hi Taylor, >> >> Not trying to be pushy or anything, but have you guys uncovered anything >> related to this issue? It's still happening quite regularly for a couple of >> weeks now. >> >> Thanks, >> Adrian >> >> -- >> Twitter developer documentation and resources: >> <http://dev.twitter.com/doc>http://dev.twitter.com/doc >> API updates via Twitter: <http://twitter.com/twitterapi> >> http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> <http://code.google.com/p/twitter-api/issues/list> >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> <http://groups.google.com/group/twitter-development-talk> >> http://groups.google.com/group/twitter-development-talk >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > > > -- > -Nischal > twitter: NischalShetty <http://twitter.com/nischalshetty> > facebook: Nischal <http://facebook.com/nischal> > > > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
Hi Taylor, Not trying to be pushy or anything, but have you guys uncovered anything related to this issue? It's still happening quite regularly for a couple of weeks now. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: users/lookup returns duplicates, missing records for valid users
Thanks for investigating :) Just thought I'd add that I'm also affected by this, and when I investigated I discovered that the exact selection of users which are omitted and duplicated is relatively stable; that is, if I run the same set of lookups on the same chunks of 100 users, it will almost always be the same users who are missing and duplicated. This can vary slightly over a course of days, but consecutive requests fail in the same way. I hope this assists the Twitter team in debugging the issue. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: countdown to OAuth / basic auth removal / OAuthcalypse
At this point, all I'm looking for is a way to upgrade this piece of
PHP code to take into account the new authentication model:
$ch = curl_init('http://twitter.com/statuses/update.xml');
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 10);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS,
'status='.urlencode(trim($message)));
curl_setopt($ch, CURLOPT_USERPWD, $settings['twitter-username'].':'.
$settings['twitter-password']);
$response = curl_exec($ch);
$resp = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Apr 24, 6:40 pm, Raffi Krikorian wrote:
> hi all.
>
> you're going to be hearing a lot from me over the next 9 weeks. our plan is
> to turn off basic authorization on the API by june 30, 2010 -- developers
> will have to switch over to OAuth by that time. between now and then, there
> will be a *lot* of information coming along with tips on how to use OAuth
> Echo, xAuth, etc. we really want to make this transition as easy as we can
> for everybody.
>
> as always, please feel free to reach out to this group, or to @twitterapi
> directly. if you need help remembering the date -http://bit.ly/twcountdown
> .
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi
>
> --
> Subscription
> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] would like to see number of lists in USER/SHOW
For the user/show method, I'd like to see the number of lists a user is in and follows, just like on the main site: eg: http://twitter.com/users/show.json?screen_name=dougw http://twitter.com/dougw/lists/memberships Lists following dougw (126) Lists dougw follows (10) add to user/show 126 10
[twitter-dev] source name has switch to web
Hi, all preexisting and newly added tweets with source Twitya have changed to Web. Tweets are added using 'source=twitya' in the post querystring as per usual.
[twitter-dev] Re: problem with http://twitter.com/statuses/update.xml
PHP code used:
Hence the error message given is "could not authenticate" -$response
while( $message = array_pop($messages) ){
$ch = curl_init('http://twitter.com/statuses/update.xml');
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 10);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, 'status='.urlencode($message));
curl_setopt($ch, CURLOPT_USERPWD, $settings['twitter-username'].':'.
$settings['twitter-password']);
$response = curl_exec($ch);
$resp = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
echo 'posted '.urlencode($message).'';
if ( $resp != '200' )
die('Problem with twitter. We should try later. Twitter
reported: '.
$response);
else
sleep(5);//Sleep 5 seconds before the next update
}
On Apr 20, 11:48 am, Abraham Williams <4bra...@gmail.com> wrote:
> It would be helpful if you provided code and more details.
>
>
>
> On Mon, Apr 20, 2009 at 02:14, Adrian wrote:
>
> > Also, for the account that works, if I changes its screen name to the
> > account that doesn't work well, that working account stops working
> > properly.
>
> > On Apr 20, 10:12 am, Adrian wrote:
> > > I have a php script that posts updates tohttp://
> > twitter.com/statuses/update.xml
>
> > > It works reliably when posting to one account of mine, but when
> > > switching to another, it constantly says "Problem with Twitter. Could
> > > not authenticate you. Try again later."
>
> > > I try again later, multiple times, and only sometimes it will actually
> > > work. With the other account it always works, so there's something up
> > > with Twitter and some accounts for such updating.
>
> --
> Abraham Williams |http://the.hackerconundrum.com
> Hacker |http://abrah.am|http://twitter.com/abraham
> Web608 | Community Evangelist |http://web608.org
> This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: problem with http://twitter.com/statuses/update.xml
Also, for the account that works, if I changes its screen name to the account that doesn't work well, that working account stops working properly. On Apr 20, 10:12 am, Adrian wrote: > I have a php script that posts updates > tohttp://twitter.com/statuses/update.xml > > It works reliably when posting to one account of mine, but when > switching to another, it constantly says "Problem with Twitter. Could > not authenticate you. Try again later." > > I try again later, multiple times, and only sometimes it will actually > work. With the other account it always works, so there's something up > with Twitter and some accounts for such updating.
[twitter-dev] problem with http://twitter.com/statuses/update.xml
I have a php script that posts updates to http://twitter.com/statuses/update.xml It works reliably when posting to one account of mine, but when switching to another, it constantly says "Problem with Twitter. Could not authenticate you. Try again later." I try again later, multiple times, and only sometimes it will actually work. With the other account it always works, so there's something up with Twitter and some accounts for such updating.
[twitter-dev] Re: Request for documentation review
Would love to see something about OAuth, to help in the migration process. On Apr 14, 2:11 am, Doug Williams wrote: > Coderz, > I am refactoring the API documentation [1] to make it friendlier on the eyes > and easier on new developers. Please give it a once over and reply with any > of errors, addition requests, or suggestions. We will be using these new > docs officially in a few days (linked from the apiwiki.twitter.com) once any > glaring omissions and/or errors are addressed. > > My goal is to make the documentation more robust and example laden to help > new developers get going without needing help. Suggestions and critism along > those lines is welcome. > > A final plea for help: > If you have some spare time and examples to borrow from, please send > a...@twitter.com any code/instructions that I can then paste into method body > to help new devs get started. Basic Hello World! style usage examples for > each method would go a long way to curbing new developer problems. Be sure > to include a link to any libraries your example is using. Working full > length example code hosted on github would be preferred. > > 1.http://apiwiki.twitter.com/Twitter-API-Documentation > > Thanks, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] What's the status of OAuth to non-beta users?
Please let me know when it's possible for average API users to access OAuth authentication for their apps? This page seems to be open to all: http://twitter.com/oauth_clients/new
[twitter-dev] data inconsistencies between json and xml
Wondering why friends count here is 791: http://twitter.com/users/show/rssfriends.json but here it is the correct 896: http://twitter.com/users/show/rssfriends.xml
[twitter-dev] Re: Double Basic Authentication When Post Follows Get
OK, done. thx :) On Apr 12, 5:58 am, Abraham Williams <4bra...@gmail.com> wrote: > Well the API is what it is. I don't know of any open issues about supporting > sessions. I suppose you could open one. > > > > On Sat, Apr 11, 2009 at 19:19, Adrian wrote: > > > It adds more complexity to my side. Sessions would be better atm. > > > On Apr 12, 3:10 am, Cameron Kaiser wrote: > > > > ..I can't and dont' want to access user credentials. > > > > > I'd love session support. > > > > Then you will love OAuth. > > > > -- > > > personal: > >http://www.cameronkaiser.com/-- > > > Cameron Kaiser * Floodgap Systems *www.floodgap.com* > > ckai...@floodgap.com > > > -- I'm a dyslexic amateur orthinologist. I just love word-botching. > > --- > > -- > Abraham Williams |http://the.hackerconundrum.com > Hacker |http://abrah.am|http://twitter.com/abraham > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Double Basic Authentication When Post Follows Get
It adds more complexity to my side. Sessions would be better atm. On Apr 12, 3:10 am, Cameron Kaiser wrote: > > ..I can't and dont' want to access user credentials. > > > I'd love session support. > > Then you will love OAuth. > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- I'm a dyslexic amateur orthinologist. I just love word-botching. > ---
[twitter-dev] Re: Double Basic Authentication When Post Follows Get
do you mean just call: username:passo...@https://twitter.com/statuses/update.xml ..I can't and dont' want to access user credentials. I'd love session support. On Apr 12, 3:04 am, Abraham Williams <4bra...@gmail.com> wrote: > Sessions are not officially supported. You might as well just to include > credentials with all calls. > > > > On Sat, Apr 11, 2009 at 18:57, Adrian wrote: > > > Hi, on my client, if I run GET request, I'll have to authenticate but > > after that all other GETs don't require authentication. Then, as soon > > as there is a POST, I will have to re-authenticate. I'd prefer the > > server just accepted the POST request as part of the session from the > > already authenticated user and didn't reask for credentials. See > > headers below: GET Request > Authenticate > POST Request > Fail > > >http://twitter.com/account/verify_credentials.json?callback=jsonp1239... > > > GET /account/verify_credentials.json? > > callback=jsonp1239486621989&_=1239493435268 HTTP/1.1 > > Host: twitter.com > > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: > > 1.9.0.8) Gecko/2009032609 Firefox/3.0.8 > > Accept: */* > > Accept-Language: en-us,en;q=0.5 > > Accept-Encoding: gzip,deflate > > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > > Keep-Alive: 300 > > Connection: keep-alive > > Authorization: Basic ZGVzbWlkaXNvOmd3dHdnd3R3 > > > HTTP/1.x 200 OK > > Date: Sat, 11 Apr 2009 23:44:15 GMT > > Server: hi > > Last-Modified: Sat, 11 Apr 2009 23:44:15 GMT > > Status: 200 OK > > Etag: "a69811ab820044f3fcad85ed061bb512"-gzip > > Pragma: no-cache > > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- > > check=0 > > Content-Type: application/json; charset=utf-8 > > Expires: Tue, 31 Mar 1981 05:00:00 GMT > > X-Revision: 0d279c956b77447dc8b68179a828f0d93a6e93e3 > > X-Transaction: 1239493455-52742-21090 > > Set-Cookie: lang=; path=/ > > Set-Cookie: > > _twitter_sess=BAh7CToJdXNlcmkEKCLNAToTcGFzc3dvcmRfdG9rZW4iLWFkNmEzZGQzMzli > > > %250AOGRiZTE5YmViNTFlYzAwODZhYjRhZjE3NGY1OTE6B2lkIiU4MjAwYTFmYTA5%250AM2I4Z > > WUxYTEzNmJlOTQ4NmZlNzgzOCIKZmxhc2hJQzonQWN0aW9uQ29udHJv > > %250AbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D-- > > b68d85bbacedd2a15c46152c514ac78fc30c1873; domain=.twitter.com; path=/ > > Vary: Accept-Encoding > > Content-Encoding: gzip > > Content-Length: 491 > > Connection: close > > > > >https://twitter.com/statuses/update.xml > > > POST /statuses/update.xml HTTP/1.1 > > Host: twitter.com > > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: > > 1.9.0.8) Gecko/2009032609 Firefox/3.0.8 > > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/ > > *;q=0.8 > > Accept-Language: en-us,en;q=0.5 > > Accept-Encoding: gzip,deflate > > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > > Keep-Alive: 300 > > Connection: keep-alive > > Content-Type: application/x-www-form-urlencoded > > Content-Length: 53 > > source=Twitya&in_reply_to_status_id=&status=Hello+God > > HTTP/1.x 401 Unauthorized > > Date: Sat, 11 Apr 2009 23:47:38 GMT > > Server: hi > > Status: 401 Unauthorized > > WWW-Authenticate: Basic realm="Twitter API" > > Cache-Control: no-cache, max-age=1800 > > Content-Type: application/xml; charset=utf-8 > > Set-Cookie: > > _twitter_sess=BAh7BzoHaWQiJTc2OGQzNGEzNzlhNWYyNjliNTI1NDIzZTYxYmU4ZjkyIgpm > > %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG > > %250AOgpAdXNlZHsA--546494cea99c2f48565af4f437ae265f04ed6bc6; > > domain=.twitter.com; path=/ > > Expires: Sun, 12 Apr 2009 00:17:38 GMT > > Vary: Accept-Encoding > > Content-Encoding: gzip > > Content-Length: 135 > > Connection: close > > -- > Abraham Williams |http://the.hackerconundrum.com > Hacker |http://abrah.am|http://twitter.com/abraham > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, Wisconsin, United States
[twitter-dev] Double Basic Authentication When Post Follows Get
Hi, on my client, if I run GET request, I'll have to authenticate but after that all other GETs don't require authentication. Then, as soon as there is a POST, I will have to re-authenticate. I'd prefer the server just accepted the POST request as part of the session from the already authenticated user and didn't reask for credentials. See headers below: GET Request > Authenticate > POST Request > Fail http://twitter.com/account/verify_credentials.json?callback=jsonp1239486621989&_=1239493435268 GET /account/verify_credentials.json? callback=jsonp1239486621989&_=1239493435268 HTTP/1.1 Host: twitter.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: 1.9.0.8) Gecko/2009032609 Firefox/3.0.8 Accept: */* Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Authorization: Basic ZGVzbWlkaXNvOmd3dHdnd3R3 HTTP/1.x 200 OK Date: Sat, 11 Apr 2009 23:44:15 GMT Server: hi Last-Modified: Sat, 11 Apr 2009 23:44:15 GMT Status: 200 OK Etag: "a69811ab820044f3fcad85ed061bb512"-gzip Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/json; charset=utf-8 Expires: Tue, 31 Mar 1981 05:00:00 GMT X-Revision: 0d279c956b77447dc8b68179a828f0d93a6e93e3 X-Transaction: 1239493455-52742-21090 Set-Cookie: lang=; path=/ Set-Cookie: _twitter_sess=BAh7CToJdXNlcmkEKCLNAToTcGFzc3dvcmRfdG9rZW4iLWFkNmEzZGQzMzli %250AOGRiZTE5YmViNTFlYzAwODZhYjRhZjE3NGY1OTE6B2lkIiU4MjAwYTFmYTA5%250AM2I4ZWUxYTEzNmJlOTQ4NmZlNzgzOCIKZmxhc2hJQzonQWN0aW9uQ29udHJv %250AbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D-- b68d85bbacedd2a15c46152c514ac78fc30c1873; domain=.twitter.com; path=/ Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 491 Connection: close https://twitter.com/statuses/update.xml POST /statuses/update.xml HTTP/1.1 Host: twitter.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: 1.9.0.8) Gecko/2009032609 Firefox/3.0.8 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/ *;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Content-Type: application/x-www-form-urlencoded Content-Length: 53 source=Twitya&in_reply_to_status_id=&status=Hello+God HTTP/1.x 401 Unauthorized Date: Sat, 11 Apr 2009 23:47:38 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm="Twitter API" Cache-Control: no-cache, max-age=1800 Content-Type: application/xml; charset=utf-8 Set-Cookie: _twitter_sess=BAh7BzoHaWQiJTc2OGQzNGEzNzlhNWYyNjliNTI1NDIzZTYxYmU4ZjkyIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--546494cea99c2f48565af4f437ae265f04ed6bc6; domain=.twitter.com; path=/ Expires: Sun, 12 Apr 2009 00:17:38 GMT Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 135 Connection: close
[twitter-dev] Quota incorrectly displayed in Chrome and Opera - fine in IE and FF
Hi, I'm been developing a client-side app that uses basic HTTP Authentication into twitter.com. The problem is that when logging-in with a whitelisted account, the 20,000 quota is correctly reflected in the remaining hits as displayed on-site whilst using IE and FF, but in Chrome and Opera, the quota is back to 100 when logging in with the same account. You can see here: http://tr.im/iqLY Enter your username and password - immediately at top-right there will be a number - the remaining hits. It seems this quota is dependent on twitter detecting a whitelisted account, which is determined by the browser. Furthermore, http://twitter.com/account/rate_limit_status.json http://twitter.com/account/rate_limit_status.xml in the same browser, eg IE will display different results. Former ~2, latter 100 and across browser, sometimes the results for each are identical, ~100.
[twitter-dev] Following/ Friend count inconsistencies
online-- follows 554 people http://twitter.com/rssfriends/friends (and growing) XML-- has 508 friends: http://twitter.com/users/show/rssfriends.xml JSON-- 501 friends: http://twitter.com/users/show/rssfriends.json
[twitter-dev] more information behind /friendships/add
Hi there, regarding the March 26 addition of having hyperlinks: twitter.com/friendships/add/username lead to a minimal page allowing the user to follow any Twitter user upon pressing the button on that page, I was wondering if that same page could provide the option to unfollow the specified twitter user if the already following. Perhaps a even new page could added with both options: twitter.com/ friendships/respond/username
[twitter-dev] Re: API Changes for April 1, 2009
As of right right now: http://twitter.com/users/show/bob.xml has about twice the amount of information as say: http://twitter.com/users/show/WeezerOfficial.xml On Apr 2, 3:34 am, Alex Payne wrote: > (Not an April Fool, we promise. We don't enjoy "humor".) > > * Feature (REST API): We now return the same representation of User > objects throughout the API. This representation contains all of the > attributes we make available via the API. > > A bit more about this change: > > Previously, these "full" User objects were only available via the > /users/show and /account/verify_credentials methods. If your > application has been making requests to these methods just to get > extra User attributes, you no longer need to do so. We've had many, > many requests for these extra attributes to be available everywhere, > so we hope to see you all making use of them! > > Please note that this new extended view of User objects may not appear > for all users immediately. As cache expiry occurs for users in our > system, the extra attributes will show up. Don't be surprised if this > takes multiple days for inactive users. > > Please also note that if your application is operating in a highly > bandwidth-constrained environment, you may want to proxy requests to > strip out attributes that aren't relevant to your client. The > additional bytes over the wire should not impact the vast majority of > platforms, in our estimates. > > As always, you can keep up with these changes athttp://bit.ly/api_changelog. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Nice problem - tweets over 140 chars still being logged
I just logged a Tweet 181 characters long using the Twitlet bookmarklet. http://twitter.com/twitya/status/137357
[twitter-dev] incorrect userIDs in search feed
I've found that the user IDs in search feeds for any given user mismatch with those in the normal twitter feeds. Take for example @arikfr: ID: 12069702 http://twitter.com/users/show/arikfr.xml Now goto a search lookup: http://search.twitter.com/search.json...@arikfr or http://search.twitter.com/search.json?q=to:arikfr and the same user's ID is 3341
[twitter-dev] friends ids / followers ids .. any arguments?
I was wondering if it's possible for arguments to be passed to: http://twitter.com/followers/ids/USER.json and http://twitter.com/friends/ids/USER.json in order to limit the response and reverse the order, ie http://twitter.com/friends/ids/USER.xml?count=160&order=newest thx.
[twitter-dev] Re: Pushing Twitter data into the clients
Awesome. Right now, the onus is on the Tweet receiver to sort their friends into groups, and pick and choose those groups they wish read and check at any one time, like with Friendfeed. Would be great to have Sending groups too, where the sender of Tweet chooses who shall receive it. On Mar 15, 11:13 am, ledil wrote: > Hello, > > if you wait another two months, you can use XMPP within blummi.com. > Very are building a > location-based micro-blogging service based on XMPP with realtime > delivering of location > based information. > > greets, > > On Mar 14, 4:26 pm, Andrew Badera wrote: > > > Has Jaiku gone XMPP yet? We're having a discussion about jaiku on the > > GAE list now. I believe XMPP is almost-but-not-quite-ready? They're > > involved in a pubsubhub project on GAE to make it happen, if I paid > > enough attention to that convo. > > > On Sat, Mar 14, 2009 at 5:59 AM, Adrian wrote: > > > > Well, as much as I love Twitter, it's not on Google's infrastructure. > > > Speaking of which, Jaiku has gone open source and supports XMPP: > > > >http://code.google.com/p/jaikuengine/ > > >http://code.google.com/p/jaikuengine/source/browse/trunk/doc/design_f... > > > > Twitter Team: maybe there's something to learn here. > > > > On Mar 13, 6:07 pm, Joshua Perry wrote: > > >> Hey, thats an interesting read, as is Robey's commentary on the Kestrel > > >> message queuing system, but it brings up more questions for me. > > > >> Using a message queuing system is great for decoupling producers from > > >> consumers, but frankly I'm surprised that they're using a polling queue > > >> as recently as January -- however long the polling may be (250msec). > > >> When is the last time your network card polled the switch it is > > >> connected for the next packet in its queue? When was the last time your > > >> application polled the TCP stack for the next byte available in its > > >> buffer? Computers at their lowest level have been event driven since > > >> the early 60's. Any architecture with hopes of scaling should not be > > >> based on polling. Removing polling is usually one of the first > > >> optimizations in a system that finds itself needing to grow beyond its > > >> current capabilities. > > > >> Also, queuing systems don't lend themselves terribly well to the concept > > >> of a pub-sub model. In a multicast model the a message is placed on a > > >> queue and any interested parties can listen to that queue and work on > > >> messages from it; this is not much better than the firehose method, as > > >> the data is actually duplicated and blasted to the endpoints at the > > >> network layer. So while a multicast model is somewhat well-suited to > > >> the Twitter backbone I don't see it being useful outside of that > > >> backbone. In a unicast model a queue is not much more than a decoupling > > >> abstraction between the producer and the consumer. > > > >> I don't know what size their internal message data structure looks like, > > >> but assuming a message of around 1KB -- should be easy to get to this > > >> size passing around unicode -- their queue would exhaust its128MB of > > >> memory cache after only 128000 messages. I don't know if their servers > > >> are memory constrained, they have a large number of queues, this comes > > >> from throughput testing, or they are just optimizing early; with a > > >> "small" server these days able to be configured with upwards of 24GB of > > >> RAM, this number seems low. > > > >> Its easy to stand outside of their design -- and what I'm sure have been > > >> hundreds of hours of discussions and meetings -- and criticize their > > >> system but I hope that there is some constructive criticism in this > > >> discussion. With the reliance that Twitter puts on open-source software > > >> I believe they also value open discussion. > > > >> Josh > > > >> Andrew Badera wrote: > > >> > Last I'd checked, the whole "Twitter needs to rebuild as a messaging > > >> > architecture" conversation is many months old, and probably well on > > >> > its way to being implemented. > > > >> >http://blog.twitter.com/2009/01/building-on-open-source.html > > > >> > On Thu, Mar 12, 2009 at 9:19 PM, Joshua Per
[twitter-dev] Re: Pushing Twitter data into the clients
Praise the lord, of course; but you can't say YouTube has not sped up upon integration into Google's tech stack? (Big Table, Google FS) http://www.techcrunchit.com/2008/07/16/google-where-companies-go-to-die/ I do think my comment may not have been wholly appropriate given Twitter's much, much better now. On Mar 14, 5:06 pm, Cameron Kaiser wrote: > > Well, as much as I love Twitter, it's not on Google's infrastructure. > > *cough*praisethelord*cough* > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- Please dispose of this message in the usual manner. -- Mission: Impossible > -
[twitter-dev] Re: Pushing Twitter data into the clients
ing currently is. Really, this > >> problem > >> has been solved in software and in hardware by many companies since before > >> Ethernet. Tell me why distributing a tweet is much different than a > >> multicast TCP/IP message? The database is an endpoint connected to the > >> tweet-router and just persists messages and still serves a pull REST api > >> for > >> the initial client cache-charge or web page display. An incoming message's > >> from-user-id could be used as a multicast address and be routed quite > >> efficiently to any connected client endpoint "listening" to that address. > > >> If the firehose is a hub with a giant broadcast domain, then tweet-router > >> is > >> a router behind a switch. > > >> Maybe thats silly but its what I've been thinking about. > > >> Josh > > >> Alex Payne wrote: > > >> We're going to be offering exactly that (a long-polling firehose) to > >> select partners to build on. Please see our FAQ for more information. > > >> Providing a realtime solution for the rest of the API is a lot more > >> challenging than just hooking up XMPP. If the technology was there, > >> we'd do it. But we've investigated and benchmarked, and it isn't. We > >> also want to provide something with a lower barrier to entry when > >> we're ready to go down that road. > > >> We understand that power users are very excited about "realtime", but > >> the majority of users and developers are still getting up to speed > >> with Twitter's basic offerings. Accordingly, that's where our energies > >> are at right now. > > >> On Thu, Mar 12, 2009 at 16:08, Sam Sethi wrote: > > >> Please can we get a Twitter xmpp feed. If Twitter are not going to offer > >> this can they allow GNIP to go live. GNIP say Twitter are not allowing them > >> to offer the firehose via xmpp to developers. Why? Pull based polling is > >> last year. Maybe at the least Twitter could offer a Long polling option > >> like > >> friendfeed to give a psuedo realtime feed > > >> Thanks in advance > > >> Sam > > >> W:www.twitblogs.com > > >> Sent from my iPhone > > >> On 12 Mar 2009, at 21:21, Alex Payne wrote: > > >> POST requests are unlimited. > > >> We used to support XMPP as an experimental feature, but we don't > >> currently. > > >> Delivering push features at our scale is a challenge. We're currently > >> making our traditional REST request/response APIs the best they can > >> be. In the future, maybe we'll tackle push as well. In the medium > >> term, select partners will be able to have tweets pushed to them over > >> HTTP via our "firehose" mechanism. > > >> As Andrew suggested, there's been quite a lot of discussion on these > >> topics in this group and elsewhere on the web. > > >> On Thu, Mar 12, 2009 at 13:55, Adrian wrote: > > >> Hi there, I was wondering if it's possible to push data, rather than > >> have the content pulled with JSON or XML fetches. You can poll after > >> set amounts of time, but that only present the illusion of Push, and > >> uses up bandwith. > > >> Also, is the API limit applied to POST requests? > > >> Lastly, has Twitter thought about implementing XMPP. > > >> -- > >> Alex Payne - API Lead, Twitter, Inc. > >>http://twitter.com/al3x
[twitter-dev] Re: Pushing Twitter data into the clients
Well, here are some good links behind XMPP: http://xmpp.org/ http://metajack.im/ (key XMPP advocate and founder of http://www.chesspark.com/ ) On Mar 12, 11:05 pm, Andrew Badera wrote: > What is this "XMPP" of which you speak? Tell us more! > > PS: Read the docs? FAQs? This list's archive? Used Google? Ever? > > On Thu, Mar 12, 2009 at 3:55 PM, Adrian wrote: > > > Hi there, I was wondering if it's possible to push data, rather than > > have the content pulled with JSON or XML fetches. You can poll after > > set amounts of time, but that only present the illusion of Push, and > > uses up bandwith. > > > Also, is the API limit applied to POST requests? > > > Lastly, has Twitter thought about implementing XMPP.
[twitter-dev] Re: Pushing Twitter data into the clients
Great, well that's a start, and obviously the goal is to have IM like performance in Twitter. Maybe there's an engineer out there that can help with the problem. On Mar 12, 11:21 pm, Alex Payne wrote: > POST requests are unlimited. > > We used to support XMPP as an experimental feature, but we don't currently. > > Delivering push features at our scale is a challenge. We're currently > making our traditional REST request/response APIs the best they can > be. In the future, maybe we'll tackle push as well. In the medium > term, select partners will be able to have tweets pushed to them over > HTTP via our "firehose" mechanism. > > As Andrew suggested, there's been quite a lot of discussion on these > topics in this group and elsewhere on the web. > > On Thu, Mar 12, 2009 at 13:55, Adrian wrote: > > > Hi there, I was wondering if it's possible to push data, rather than > > have the content pulled with JSON or XML fetches. You can poll after > > set amounts of time, but that only present the illusion of Push, and > > uses up bandwith. > > > Also, is the API limit applied to POST requests? > > > Lastly, has Twitter thought about implementing XMPP. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Pushing Twitter data into the clients
Hi there, I was wondering if it's possible to push data, rather than have the content pulled with JSON or XML fetches. You can poll after set amounts of time, but that only present the illusion of Push, and uses up bandwith. Also, is the API limit applied to POST requests? Lastly, has Twitter thought about implementing XMPP.
[twitter-dev] missing comma in status creation time not parsing with Date in IE
In IE, this date won't Date.parse Sun Mar 08 09:47:49 + 2009 this will Sun, 08 Mar 2009 09:58:01 + the problem is with the missing comma in the former. The former are status creation times coming from the twitter.com API, the latter are coming from the search.twitter.com API. Could the comma be inserted.
[twitter-dev] additionally
continuing from my last ticket, the year should be moved back to just after the month: SO: Sun, Mar 08 2009 09:47:49 + not Sun Mar 08 09:47:49 + 2009 thanks.
[twitter-dev] Bug: in_reply_to_screen_name
field: in_reply_to_screen_name exists for statuses /statuses/friends/USERNAME.xml but in /statuses/friends/USERNAME.json it does not. thank you.
[twitter-dev] Re: Freelance Twitter API Dev directory?
Hi Alex, Would love to be mentioned too! username: @adrianwinter Company: Interactive Pixels (www.interactivepixels.nl) Email: i...@interactivepixels.nl Focus:PHP, MySQL, OAuth, XML, Ajax, xHTML, CSS, the whole lot really ;) Location: Amsterdam, The Netherlands, Europe Creator of: TwtrFrnd.com Thanks for the inclusion, Regards, Adrian On 23 feb, 19:33, Alex Payne wrote: > There isn't one that I'm aware of, but if people would like to post > their contact info in this thread (Twitter username, URL, email, > whatever) I'm happy to collect them on the API Wiki. > > On Sat, Feb 21, 2009 at 18:00, Chad Etzel wrote: > > > Hi All, > > > I have been getting a few requests here and there for twitter API > > development work. I cannot take on any such projects at the moment, > > but I always feel bad for leaving them in the lurch. Is there a list > > or directory anywhere of Twitter API developers that work freelance > > that I can send to them when this happens? I'm happy to forward on > > such requests. > > > -Chad > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: AIR query
I too have been having some issues with connecting to anything protected by
HTTP Basic Authentication in twitter. What I have found is kind of a
bummer:
1 - The 'Authorized' http header was removed from a version of Flash Player
(I believe 9.0105 ?), but then it was added back.
2 - Now the Authorization header is now blocked when a crossdomain.xml file
blocks this request. The below line is in the twitter corssdomain policy
file:
What this means is that HTTP request using the Flash Player cannot pass
header info to twitter unless it is an allowed domain: example:
bubba.twitter.com would work, mywebsite.com will not work, based on the
permissions in their crossdomain file.
3 - A work around is to build a proxy with a server side
scripting/programming language so that the request from the flash player
goes to that script which in turn calls the twitter api. Or you could try
an AJAX approach using the Flex Ajax Bridge.
All in all this is a real bummer, however I have heard a bit about getting
different results from an AIR app but I have not succesfully implemented a
solution.
Can twitter please open up the crossdomain policy file? There are so many
cool Flex based apps coming out and twitter would be such a great mashup.
On Mon, Oct 13, 2008 at 9:24 AM, Ed Finkler <[EMAIL PROTECTED]> wrote:
>
> You need to send a request that uses HTTP Basic authentication. I'm
> sure you can find examples of doing so in many Flex references.
>
> --
> Ed Finkler
> http://funkatron.com
> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
>
> On Mon, Oct 13, 2008 at 2:24 AM, abhishek <[EMAIL PROTECTED]>
> wrote:
> >
> > i want to connect my AIR application with twitter API,
> > i never used any API before,
> > i used
> > > url="http://twitter.com/direct_messages/new.format";
> > result="
> > resultHandlerSendMessage(event);"
> > fault="faultHandlerSendMessage(event);"
> > method="POST"
> > resultFormat="e4x" >
> >
> > {userName}
> > {message}
> >
> >
> >
> > but it give an error
> > [RPC Fault faultString="HTTP request error"
> > faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent
> > type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error
> > #2032: Stream Error. URL: http://twitter.com/direct_messages/new.format";
> > errorID=2032]. URL: http://twitter.com/direct_messages/new.format";]
> >
> > is authentication mtd is req ?
> > how to use authentication mthod
> > http://twitter.com/account/verify_credentials.format , and wat to send
> > in it ?
> >
>
--
Adrian Pomilio
Trademark pending and in use. All exclusive trademark rights reserved.
Re: Is public_timeline unavailable
I kind of figured that, as well as looking at your crossdomain policy file. No biggie, thanks for your help and I am looking forward to working with the services. A On Tue, Oct 7, 2008 at 8:58 PM, Alex Payne <[EMAIL PROTECTED]> wrote: > > We hold posts from new members to prevent spam. > > You can search the group for information about the AS3 API, but > Twitter doesn't provide official support for them. > > On Tue, Oct 7, 2008 at 5:41 PM, Adrian Pomilio <[EMAIL PROTECTED]> > wrote: > > I saw your previous post, thank you for your efforts. Much appreciated. > > BTW - I joined the group and made a post but it did not show up. Are we > > only able to post to the admin? No problem if so. Any ideas where I can > > get documentation on the Twitter AS3 API for flex? > > > > On Tue, Oct 7, 2008 at 7:42 PM, Alex Payne <[EMAIL PROTECTED]> wrote: > >> > >> It was temporarily unavailable while we resolved a bug. > >> > >> On Tue, Oct 7, 2008 at 12:33 PM, Adrian <[EMAIL PROTECTED]> > wrote: > >> > > >> > Just wanted to know if public_timeline was unavailable or is it being > >> > removed? I use it for Flex examples when helping other developers > >> > learn how to connect to a feed. > >> > > >> > >> > >> > >> -- > >> Alex Payne - API Lead, Twitter, Inc. > >> http://twitter.com/al3x > > > > > > > > -- > > Adrian Pomilio > > > > > > Trademark pending and in use. All exclusive trademark rights reserved. > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x > -- Adrian Pomilio Trademark pending and in use. All exclusive trademark rights reserved.
Re: Is public_timeline unavailable
I saw your previous post, thank you for your efforts. Much appreciated. BTW - I joined the group and made a post but it did not show up. Are we only able to post to the admin? No problem if so. Any ideas where I can get documentation on the Twitter AS3 API for flex? On Tue, Oct 7, 2008 at 7:42 PM, Alex Payne <[EMAIL PROTECTED]> wrote: > > It was temporarily unavailable while we resolved a bug. > > On Tue, Oct 7, 2008 at 12:33 PM, Adrian <[EMAIL PROTECTED]> wrote: > > > > Just wanted to know if public_timeline was unavailable or is it being > > removed? I use it for Flex examples when helping other developers > > learn how to connect to a feed. > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x > -- Adrian Pomilio Trademark pending and in use. All exclusive trademark rights reserved.
Is public_timeline unavailable
Just wanted to know if public_timeline was unavailable or is it being removed? I use it for Flex examples when helping other developers learn how to connect to a feed.
Documentation for TwitterScript
Is there any documentation available for the Actionscript 3 API, TwitterScript, that went opensource on google code? I am interested in that particular API but was hoping that there might be some docs floating around instead of having to dig through all the source. Yes, kick me I am a bit lazy. :-)
