There is currently nothing in our TOS preventing this type of project from developing. However, we are writing our Terms for the API and at this time I cannot speak of how a service redistributing our data will be classified. So, proceed as you will, but be warned that we may have to have a discussion down the road when the API Terms of Service better defines our relationship with developers. Thanks, Doug --
Doug Williams Twitter Platform Support http://twitter.com/dougw On Mon, Jun 1, 2009 at 8:52 AM, Nick Arnett <[email protected]> wrote: > > > On Sun, May 31, 2009 at 3:57 PM, Stuart <[email protected]> wrote: > >> >> Much as I respect Twitter and the great people who work there, I don't >> buy that this would place too much demand on their servers. They >> already use Memcached extensively, and this would be a pretty simple >> addition to that data store. > > > For that very reason, I'm not sure it makes sense for third parties to > collaborate on a single-purpose distributed store. There are user/account > properties that Twitter won't implement, at least not until there's a lot of > demonstrated value. In other words, the developer community could > collaborate on problems that have marginal value to Twitter in the short > run. > > Nick > >
