Hi Raffi If that is the case then it's very reassuring to hear
On Mar 13, 9:23 pm, Raffi Krikorian <ra...@twitter.com> wrote: > i don't think we've said its a waste of time, especially for something like > dabr. and, again, its not that we're stopping the competition -- we've said > that if you are building a regular timeline client, we're going to be > holding you to a higher bar. in our opinion, its not a good -business- to > be in. i would love to see dabr, and other smaller, niche clients that are > done out of enjoyment of coding, love of programming, etc. to continue! > > > > > > On Sun, Mar 13, 2011 at 11:25 AM, artesea <ryancul...@gmail.com> wrote: > > Except every day I hear people go "I hate new twitter", "I want > > feature y", "I wish it didn't do that". > > I run a port of dabr, I don't do it for the money (no ads on the site) > > I do it for the love of programming. Working out ways to get thumbnail > > images in to the timeline. To have different displays depending on the > > device or choice of the user. Being able to come up with an idea > > whilst at work, and 2 hours at the keyboard when I get home to have it > > working. > > > The number of users on my client is probably five, but I'm finding it > > odd that Twitter insist that I'm wasting my efforts. > > If you are so confident that you have a large enough market of the > > timeline clients why stop competition? > > > Ryan > > ps, I'm guessing that I'm counted in the 90% who "use" a twitter > > client, but it's install on my android device any is only used to sync > > up to my contacts. > > > On Mar 13, 4:38 am, Raffi Krikorian <ra...@twitter.com> wrote: > > > hey adam. > > > > i can't speak officially and definitively, however, we don't think there > > are > > > as many business opportunities in making a piece of software that > > > *simply* renders > > > any of our timeline methods > > (/1/statuses/home_timeline,/1/statuses/mentions, > > > lists, etc.). that's your #1. > > > > you're right, we do think there is a lot to be done with tweet > > > summarization, curation, selection, matching, etc. focus your efforts on > > > that and just follow our lead with tweet rendering and interaction. > > > > does that help? > > > > On Sat, Mar 12, 2011 at 7:45 PM, Adam Green <140...@gmail.com> wrote: > > > > Can we get a definition of "client?" This seems to be where we are > > talking > > > > across each other. > > > > > 1. Twitter HQ sees a client as an app that displays *only* a user's > > home > > > > time line and allows the user to tweet, retweet, follow, etc. > > > > > 2. Developers see a client as an app that displays tweets from any > > source, > > > > including the home timeline *and* those that are curated by editors and > > > > algorithms, and allows the user to tweet, retweet, follow, etc. > > > > > I think to Twitter HQ, these are two very different things. I believe > > that > > > > this is what Ryan was trying to say. I believe that Ryan was trying to > > say, > > > > don't build apps that *only* do 1. You will have more luck with 2. > > > > Developers heard don't build apps that do 2 or you will be instantly > > shut > > > > down. > > > > > If Ryan hadn't combined his message with things that inadvertently also > > > > were perceived as a threat of instant shutdown as a result of an > > innocent > > > > misunderstanding of the rules, his statement would have been taken as > > > > advice, rather than a threat. I believe he meant well. He failed. He > > should > > > > keep trying until everyone understands. That is his job. Or it should > > at > > > > least be someone's job. Collectively the developers are worth the > > effort. > > > > > Hey, why not hold a conference, put everyone together, and talk until > > this > > > > is clear? You can afford it. We all need it. > > > > > Your future IPO investors aren't stupid. Well, at least not all of > > them. It > > > > is not just your revenue numbers they will see. It is lots of either > > happy > > > > or unhappy developers. We will raise your valuation. Keep saying that > > to > > > > Dick and the Board. They need to understand that. > > > > > On Sat, Mar 12, 2011 at 10:26 PM, Raffi Krikorian <ra...@twitter.com > > >wrote: > > > > >> is the "twitter client" what's the most useful thing there? i would > > think > > > >> the algorithms and system to match tweets to that content is the most > > > >> fruitful place for entrepreneurship? > > > > >> On Sat, Mar 12, 2011 at 7:22 PM, Shannon Whitley < > > > >> shannon.whit...@gmail.com> wrote: > > > > >>> Thanks, Raffi, but obviously I'm not the only one reaching these > > > >>> conclusions. If our interpretation is incorrect, then the policy > > > >>> isn't clear. > > > > >>> Television shows, newspaper articles, and band pages are perfect > > > >>> examples of places where a "Twitter client" might be useful. I could > > > >>> build a full-featured Twitter client around a single news site and > > > >>> that might be the perfect solution for that set of users. Under the > > > >>> new guidelines, it sounds like I'd be shutdown. > > > > >>> On Mar 12, 6:39 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > > >>> > in reading your blog post, i think you're misunderstanding what > > > >>> > @*rsarver*wrote. > > > > >>> > the API is open -- i personally love seeing all the innovation > > around > > > >>> > getting content into twitter (/1/status/update). there is a cafe > > in > > > >>> france > > > >>> > who's oven tweets whenever its done baking. that uses the platform > > to > > > >>> get > > > >>> > content in there. there was a NYU project that enabled your plants > > to > > > >>> tweet > > > >>> > when they needed water. that uses the platform to get content into > > > >>> twitter. > > > >>> > then there are people who match tweets to context. seeing > > twitter in > > > >>> > action with a television show, or a newspaper article, or a > > conference, > > > >>> or a > > > >>> > band -- that's how people really understand and get twitter. they > > see > > > >>> it > > > >>> > through the lens of what's happening in the world. > > > > >>> > what @*rsarver* said, effectively, was building a business around > > > >>> > *simply*rendering > > > >>> > /1/statuses/home_timeline was probably-not-the-best-thing-to-do. > > > >>> please go > > > >>> > still innovate. just don't bet money on simply making an API call > > to > > > >>> > grabbing a user's home_timeline and rendering it. that's thinking > > too > > > >>> > small, and @*rsarver* is telling you that. > > > > >>> > On Sat, Mar 12, 2011 at 4:29 PM, Shannon Whitley > > > >>> > <shannon.whit...@gmail.com>wrote: > > > > >>> > > I was hoping that Ryan was just a few weeks early for his April > > > >>> Fools' > > > >>> > > post. > > > > >>> > > "Don't build clients?" It sounds like a bad joke. > > > > >>> > > I wrote a letter to Ryan on my blog in response to this post: > > >http://www.voiceoftech.com/swhitley/index.php/2011/03/a-letter-to-rya... > > > > >>> > > I know you guys can't be serious about this. Stage a mutiny if > > you > > > >>> > > have to, but don't let this boneheaded decision stand. > > > > >>> > -- > > > >>> > Raffi Krikorian > > > >>> > Twitter, Application Serviceshttp://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 > > > > >> -- > > > >> 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 > > > > -- > > > Raffi Krikorian > > > Twitter, Application Serviceshttp://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 > > -- > Raffi Krikorian > Twitter, Application Serviceshttp://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
