I think you're confusing open source licensing with a Terms of Service. I agree that we need a ToS specifically for the API, and that project has been delegated internally. But in the meantime, our standard ToS applies, and that's been adequate for commercial, non-profit, and educational uses of the Twitter API.
We prefer that product names not contain "Twitter" in full, but it's just a suggestion, not a legal requirement. On Thu, Jan 22, 2009 at 13:04, AG <ankushg...@gmail.com> wrote: > > Okay so the API is open source....anyone know where supporting > documentation exists? Is it ascribed to the GNU general or lesser > general public license? NO? Then how can we create commercial apps > without worrying about twitter suing us ;-> > > There needs to be some documentation about how the API is open source > and can be used for commercial development. And no, the API wiki > pages and generic terms of service don't reflect anything beyond the > fact that it is open source. > > Can anyone help? > > Also on the naming convention side of things, what stops us from > calling our app "ABC Twitter". Twitter doesn't seem to care about > "Twitterific" or "Twitterilicious" etc. Are there any restrictions on > the name for your 3rd party app? > > Thanks > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
