That is perfectly clear, Ryan. The fact that people are still asking if they have Twitter's permission to build a client and writing blog posts that say they don't, shows that there is still confusion out there. My goal throughout this has been to get simple statements like yours into this list from Twitter HQ that eliminate the confusion. If someone at Twitter could be given the task of saying what you just said every time someone asks "Why can't I build a client?", or "Does this mean I have to stop building my client?", the confusion will eventually be removed. It may take days or weeks to reverse all the negative press.
In the future, please remember that every time you mention the hundreds of apps you turn off each week developers stop reading anything else. It is not a good way to start a conversation. Thanks for your patience. On Tue, Mar 15, 2011 at 9:28 PM, Ryan Sarver <rsar...@twitter.com> wrote: > Adam, I don't know how else to make this any more clear. As long as you stay > within the rules, your app will not get shut off. We would like to see, and > recommend that, developers focus on bigger opportunities with more potential > than writing another consumer client app. > > -- > Ryan Sarver > @rsarver > > > On Mon, Mar 14, 2011 at 9:28 AM, Adam Green <140...@gmail.com> wrote: >> >> But you will allow it, right? Even if it is thinking small, it will not be >> blocked? That is our problem. We can't separate business advice from a >> warning to prepare to be cut off. We can't help watching the hand that holds >> the kill switch. It makes it hard to hear what you say. Have patience, and >> keep explaining please. If something will not cause a ban, then say this >> explicitly to us. Don't just think it was implied. >> >> On Mon, Mar 14, 2011 at 11:20 AM, Raffi Krikorian <ra...@twitter.com> >> wrote: >>> >>> my statement here was not providing "small" on the size of the company, >>> but rather, "small" on the size of the idea. to re-iterate, making a piece >>> of software that simply renders home_timeline is thinking too small. >>> >>> On Sun, Mar 13, 2011 at 6:21 PM, Lil Peck <lilp...@gmail.com> wrote: >>>> >>>> On Sun, Mar 13, 2011 at 7:45 PM, @siculars <sicul...@gmail.com> wrote: >>>> > @raffi @rsarver, I wrote up my two cents earlier, >>>> > http://siculars.posterous.com/twitter-monoculture. I just don't >>>> > appreciate the direction you all are going in. @raffi, I spoke with >>>> > you at the CU recruiting event a few weeks back and I got to tell you >>>> > that if I were asked I would tell those kids to reconsider working at >>>> > twitter and possibly consider a Twitter competitor. you say "building >>>> > clients is ... Thinking too small" I would say your policy change is >>>> > thinking small and alienating your ardent supporters. >>>> > >>>> >>>> To which I would add, what is Twitter to arbitrate that which is and >>>> is not "too small?" Has Twitter subscribed to the fallacious "bigger >>>> is always better" philosophy? >>>> >>>> How small is too small? >>>> >>>> Less than $25 million in startup funds? >>>> >>>> OR >>>> >>>> One creative, fun loving person and their sweat equity? >>>> >>>> -- >>>> 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 >>> >>> >>> >>> -- >>> Raffi Krikorian >>> Twitter, Application Services >>> http://twitter.com/raffi >>> >>> >>> -- >>> 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 >> >> >> >> -- >> Adam Green >> Twitter API Consultant and Trainer >> http://140dev.com >> @140dev >> >> -- >> 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 > > -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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
