[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 thematthar...@twitter.com 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 arco.wagemak...@gmail.com 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] 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 nischalshett...@gmail.comwrote: 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 taylorsinglet...@twitter.comwrote: 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 apetr...@gmail.com 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/dochttp://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 ra...@twitter.com 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 listflrs126listflrs listfrds10listfrds
[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] 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: 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 spiritpo...@gmail.com 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] 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 'brposted '.urlencode($message).'br';
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 spiritpo...@gmail.com 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 spiritpo...@gmail.com 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] 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] 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 spiritpo...@gmail.com wrote:
It adds more complexity to my side. Sessions would be better atm.
On Apr 12, 3:10 am, Cameron Kaiser spec...@floodgap.com 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] 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=Twityain_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] 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 spiritpo...@gmail.com 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=Twityain_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] 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 spec...@floodgap.com 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] 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] 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 a...@twitter.com 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] Re: Pushing Twitter data into the clients
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 samkse...@googlemail.com 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 a...@twitter.com 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 spiritpo...@gmail.com 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] 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 and...@badera.us 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 spiritpo...@gmail.com 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] 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] 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 a...@twitter.com 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 jazzyc...@gmail.com 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
