Your final conclusion is about right.
Also, keep in mind, a large portion of the growth of Twitter was driven by the technical innovation of 3rd-party developers (ie the first iOS app)
They built their service on the back of cool things developers built, and now seem intent on destroying the very same ecosystem which ensured their popularity now that they are succesful -> http://daltoncaldwell.com/what-twitter-could-have-been
I think this sucks, and I am trying to do something about it, rather than just complain on the Internet.
Re:App.net project update #1
by peterwiese on Tuesday July 17, 2012 @05:39PM
(#4258071)
if it is my final paragraph that is correct, then i don't understand why you are referring to twitter et al when announcing your service. you are obviously not in competition with them at all (with the exception of bot nets as a customer base maybe).
This is a catch-22. I have to refer to the comparable service and API to give some idea of what we are talking about, and where the inspiration came from.
Whether any startup founder likes it or not, their startups and projects will get put into buckets and will get called things like "the X of Y" or "like X a Y put together" or "X for dogs".
the thing is: the reason why developers want access to the twitter api in the first place is because the users are there. you cannot just make a paradise for developers when there are no actual users feeding data into the system. one of the main reasons twitter got to where it is today is because celebrities started using it and their fans followed... you cannot reconstruct this phenomenon in the way you're trying to pull it off.
maybe, what you're trying to do is something completey else. maybe you want a service rather for machines to talk to, as a service purely for developers. than that's something completely else.