<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>louisgray.com - Latest Comments in louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://louisgray.disqus.com/</link><description>A Silicon Valley Blog for Early Adopters and Tech Geeks</description><atom:link href="https://louisgray.disqus.com/louisgraycom_twitter_chokes_unauthenticated_api_requests_sites_gasp_for_air/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 29 Oct 2009 06:09:59 -0000</lastBuildDate><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-21253743</link><description>&lt;p&gt;hy this is a great site kung regards &lt;a href="http://www.layer-king.com" rel="nofollow noopener" target="_blank" title="www.layer-king.com"&gt;www.layer-king.com&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Layer-King</dc:creator><pubDate>Thu, 29 Oct 2009 06:09:59 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-963202</link><description>&lt;p&gt;Sounds like a very reasonable business model.  I have a feeling that's what we're going to see from Twitter soon.  Maybe they should have rolled out the payment plan before turning off the tap though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Greg Go</dc:creator><pubDate>Tue, 22 Jul 2008 00:08:58 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-954436</link><description>&lt;p&gt;At FriendBinder I think we have this under control now, as long as people authenticate for Twitter: &lt;a href="http://blog.friendbinder.com/2008/07/changes-to-twitter-support.html" rel="nofollow noopener" target="_blank" title="http://blog.friendbinder.com/2008/07/changes-to-twitter-support.html"&gt;http://blog.friendbinder.co...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Cunningham</dc:creator><pubDate>Mon, 21 Jul 2008 05:32:02 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-935022</link><description>&lt;p&gt;Twitter started pushing their XMPP feed to Gnip this morning. Notifications for everyone! &lt;a href="http://www.techcrunch.com/2008/07/18/twitter-plays-nice-xmpp-firehose-data-feed-to-gnip/" rel="nofollow noopener" target="_blank" title="http://www.techcrunch.com/2008/07/18/twitter-plays-nice-xmpp-firehose-data-feed-to-gnip/"&gt;http://www.techcrunch.com/2...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Marcoullier</dc:creator><pubDate>Fri, 18 Jul 2008 14:19:47 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-934700</link><description>&lt;p&gt;To me this seems to be a good opportunity for Twitter to bring in a little extra cash.  Why not offer up the 100 req/hr for free, and charge for anything beyond that?  Given the choice between "dying a slow death" and paying a reasonable fee for access to a valuable service, I think many developers would prefer the latter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kevin</dc:creator><pubDate>Fri, 18 Jul 2008 13:52:46 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-933259</link><description>&lt;p&gt;Do you think twitter users should share the burden? a la Amazon's Alexa API which charges pennies for every 1,000 requests. I don't necessarily advocate charging the end-users but maybe the services which make more than 5,000 requests per day.&lt;/p&gt;&lt;p&gt;Indus&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Indus Khaitan</dc:creator><pubDate>Fri, 18 Jul 2008 11:49:20 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-932882</link><description>&lt;p&gt;Great analysis!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ekivemark</dc:creator><pubDate>Fri, 18 Jul 2008 11:10:47 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-932465</link><description>&lt;p&gt;So I'd just like to chime in as an API user.  While Socialthing! uses the authenticated API and we're not at all affected by this, we have similar restrictions at other sites.  Up until now, Twitter had really been an anomaly when it comes to how their API is served up (in both authenticated and unauthenticated calls.  First off, almost every single other site out there with a popular API has rate limiting on the IP level.  Yeah, it sucks, but there's really not many other ways of doing it until push comes to pass.  &lt;a href="http://gnipcentral.com" rel="nofollow noopener" target="_blank" title="http://gnipcentral.com"&gt;Gnip&lt;/a&gt; is a solution for sure, but those same API providers need to plug into Gnip for it to happen.&lt;/p&gt;&lt;p&gt;Twitter is just coming to a point where they're realizing that they can't easily sustain their previous models.  Anyone that is currently using unauthenticated calls will soon be able to pull from Gnip to be able to optimize their calls (and likely, be more accurate than they were before).&lt;/p&gt;&lt;p&gt;APIs are a tough game...both on the consumer and the producer level.  Twitter understands that their developers are their lifeblood, that's why they're working hard to improve the service for all.  I think it's safe to say that the reason they're bumping up the auth'ed calls, and down the unauth'ed calls is because more people actually interact with services that are authenticated.  Think Twhirl, Twitterrific, Socialthing!, etc.  Now, the non-authenticated services are probably pulling far more data at a much larger detriment to Twitter, but most of the activity isn't going on with those places.  This move is a very positive thing for the API as a whole, and you can rest assured that they will likely have other solutions for folks that simply can't auth the API going forward.&lt;/p&gt;&lt;p&gt;Great post, Louis&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Galigan</dc:creator><pubDate>Fri, 18 Jul 2008 10:37:03 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-932267</link><description>&lt;p&gt;I don't pay a direct fee for the tap water I use in my building, but I'm pretty sure if I started bottling the stuff as a business, using thousands of gallons a day, the management company would track down which apartment was using all that water and ask me to stop.&lt;/p&gt;&lt;p&gt;Anyone who builds a service depending on more than a request a minute from a single data stream should realize they're treading on very shaky ground.  I have little sympathy.  If you were GM, you wouldn't have one and only one brake supplier...   having one supplier is just not a good business strategy at all, so these Twitter apps are risky propositions from the start.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ceonyc</dc:creator><pubDate>Fri, 18 Jul 2008 10:16:31 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-932130</link><description>&lt;p&gt;Building a business on use of another business's API, and being a drain on that business's resources, and not supporting that business financially. No room for complaint in my eyes. This sounds like a smart move by Twitter. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">LH</dc:creator><pubDate>Fri, 18 Jul 2008 10:02:20 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-931510</link><description>&lt;p&gt;why does anyone care?  forget the technical problems.  the real issue here is that twitter failed to be a free forum for free expression and is censoring any parties that question their ever changing policy.  twitter is dead and it isn't because it doesn't load... it is because their hearts were up their asses&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Noah David Simon</dc:creator><pubDate>Fri, 18 Jul 2008 08:50:19 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-930676</link><description>&lt;p&gt;Hi Louis,&lt;/p&gt;&lt;p&gt;Our side project &lt;a href="http://www.tweetmeme.com" rel="nofollow noopener" target="_blank" title="http://www.tweetmeme.com"&gt;http://www.tweetmeme.com&lt;/a&gt; which was the first twitter URL tracker has now been down for months because we were offered the use of the XMPP feed and by the time we had implemented they pulled it. We will not bring it back up again or put development effort into it unless these kind of restrictions are a thing of the past.&lt;/p&gt;&lt;p&gt;It is a real shame because twitter became strong because of a really simple to use RESTful API that developers flocked to, by restricting access they are cutting off what made it what it is, this can only have a detrimental effect in the long term.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nick Halstead</dc:creator><pubDate>Fri, 18 Jul 2008 06:39:59 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-930668</link><description>&lt;p&gt;Does this help illustrate why we need a open and federated microblogging solution?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pete Prodoehl</dc:creator><pubDate>Fri, 18 Jul 2008 06:38:16 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-930475</link><description>&lt;p&gt;This was bound to happen.&lt;br&gt;I guess you should use twitter search api (summize) get public data instead of regular api.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thejesh GN</dc:creator><pubDate>Fri, 18 Jul 2008 05:43:53 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-930191</link><description>&lt;p&gt;Twitter is surely circling the plug hole. I'm impressed that they have managed to stay alive this long!!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nogg3r5</dc:creator><pubDate>Fri, 18 Jul 2008 04:10:04 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-930063</link><description>&lt;p&gt;so gold is the only option for Twitter? all these silver, bronze parties just don't count? who was it that said; participating is more important than winning? it sure is true; all that twitters is not gold.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A3Munier</dc:creator><pubDate>Fri, 18 Jul 2008 03:32:23 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-929634</link><description>&lt;p&gt;is twitter on the way to evil?  walled garden?  or just trying to breathe?  trying to get control over competitor's?&lt;/p&gt;&lt;p&gt;dunno&lt;/p&gt;&lt;p&gt;but damn good reporting mr. gray&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gregorylent</dc:creator><pubDate>Fri, 18 Jul 2008 01:13:06 -0000</pubDate></item><item><title>Re: louisgray.com: Twitter Chokes Unauthenticated API Requests, Sites Gasp for Air</title><link>http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html#comment-929102</link><description>&lt;p&gt;The ability to curtail traffic selectively is a hallmark of maturing service platforms.&lt;/p&gt;&lt;p&gt;Now, witness the power....&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jay Cuthrell</dc:creator><pubDate>Thu, 17 Jul 2008 23:38:04 -0000</pubDate></item></channel></rss>