It's about more than protecting your investment - supporting a REST API over existing resources is one thing, but supporting a free streaming API to the firehose, on the scale of Twitter, is a whole nother matter. I don't know that the dividends by offering a completely free streaming API and expanding the user and developer base (like the REST API does) would be worth the incredible bandwidth costs they would incur by doing so.
-- Eric On Thu, Apr 15, 2010 at 5:58 AM, Andrew Badera <[email protected]> wrote: > Likewise. I even went so far as to say the same to Fred Wilson, > without response. Very disappointing -- I'll repeat myself here -- I > don't know that I can imagine a more bitter hypocrisy than Twitter's > behaviors of late toward the development community. I understand > protecting your investment, but I also understand integrity and > graciousness. > > ∞ Andy Badera > ∞ +1 518-641-1280 Google Voice > ∞ This email is: [ ] bloggable [x] ask first [ ] private > ∞ Google me: http://www.google.com/search?q=andrew%20badera > > > > On Thu, Apr 15, 2010 at 4:19 AM, tyler gillies <[email protected]> wrote: >> as ive said to a friend fairly recently >> >> f*SK twitter ;) >> >> On Thu, Apr 15, 2010 at 1:16 AM, Julien Genestoux >> <[email protected]> wrote: >>> >>> We (superfeedr) have created a hub exactly like this : we susbcribed to >>> the right users with the streaming API (that they've had for months), and >>> rebuild the feeds from it. It's technically fully fonctionnal. >>> I got in touch with Ryan Sarver and John Kalucki who said that this hub >>> would be breaking their TOS (which specifically mentions that we can't >>> redistribute/resyndicate/republish the data) and that if we turn it on, >>> they'd probably shut our access down. I believed this is more or less what >>> happend to GNIP last year. >>> Since I hate building things that are not "durable" and I don't want to >>> piss off people with false expectations, I never turned it on. If Twitter >>> ever changes their TOS or is even willing to discuss this specific matter >>> with us, we're more than happy to turn this hub on. >>> Cheers, >>> >>> >>> On Thu, Apr 15, 2010 at 9:54 AM, tyler gillies <[email protected]> >>> wrote: >>>> >>>> im surprised superfeedr just doesn't get firehose access and create their >>>> own twitter hub >>>> >>>> On Wed, Apr 14, 2010 at 10:01 PM, Kevin Marks <[email protected]> >>>> wrote: >>>>> >>>>> sitting at their hackathon, the stream is the same continuous flow of >>>>> JSON structs as the others are. You could use it to send updates to a PuSH >>>>> hub. >>>>> >>>>> On Wed, Apr 14, 2010 at 9:44 PM, Jeff Lindsay <[email protected]> >>>>> wrote: >>>>>> >>>>>> Which also makes it possible for people to publish as PuSH .... >>>>>> >>>>>> On Wed, Apr 14, 2010 at 9:38 PM, Jud Valeski <[email protected]> wrote: >>>>>>> >>>>>>> just means that they're moving more and more funx over to the >>>>>>> streaming model (not PuSH). >>>>>>> >>>>>>> On Thu, Apr 15, 2010 at 12:31 AM, Didier Durand >>>>>>> <[email protected]> wrote: >>>>>>>> >>>>>>>> Hi guys, >>>>>>>> >>>>>>>> Does anybody know if the announcement of yesterday by Twitter (see >>>>>>>> http://techcrunch.com/2010/04/14/twitter-user-streams-annotations/) >>>>>>>> means that they are coming to Pubsubhubbub ? >>>>>>>> They mention "real-time notifications", no "more polling", etc. >>>>>>>> >>>>>>>> Thanks by advance for your hints >>>>>>>> didier >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> To unsubscribe, reply using "remove me" as the subject. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Jeff Lindsay >>>>>> http://progrium.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Everyone Loves Tea >>>> http://www.everyonelovestea.com >>> >> >> >> >> -- >> Everyone Loves Tea >> http://www.everyonelovestea.com >> >
