@documentally i see it as an infrastructure company with an API (w/pricing tiers) powering an ecosystem of developers, some making clones of popular services, some making new innovative services, and catering to orgs, companies and consumers, & not free.
@documentally at the core, the company will attempt to be driven by traditional models of paying customers rather than play the game of mass adoption, inflated evaluation and inevitable developer discrimination.
What is an example of a service that isn't a Twitter clone that could be powered by the current app.net framework? I think having a legitimate answer to that question would help answer people's questions.
@documentally An ad-free, paid subscription-based framework for social media interactions, respects 3rd party developers & doesn't treat its users like the product. Noobs see Twitter clone, only b/c that was the first "shipping" app using the framework.
@documentally I prefer 500-750 characters for adequate thought emmissions ;-) But 256 has been a nice bump up from 140. It would be cool to see what users here would do with imposed limit as a setting.
@katcaverly There's also a lot of infrastructure thats yet to be decided and the api is nowhere near final (my understanding). There is Issue #33 that could allow private/semi-private networks. #33 & pricing are what a lot of devs are watching/backing.
@yagankiely i feel that any UI can overcome "ruining" an experience. so in this case, the stream could always display ~256 chars with a simple read more option (permalink and/or expand/collapse toggle) Nothing new but it works. I do like succinctness!
@katcaverly Yes, not a terrible plan for now. Until 33 & pricing, I'm playing/hanging out/learning a bunch. But in the meantime, think of a group (or groups) of people who would pay to talk to each other or to another group. p.s. it's not developers
@sull But if the <256 chars is half a paragraph rather than a comment are summary then this is the same as an RSS feed that says 'click to read more'. I can't skim half a paragraph, I can skim a comment or summary.
@katcaverly But they didn't pay to only talk. Talking to each other here was necessary but not sufficient for why a developer joined. They paid for access to make something better than what's available now.
Funny, the exact thought I had was "What would Dave Winer do (with App.net)?" MP @sull@yagankiely here is an example River of News (using bootstrap) that I put together that sort of expresses what I was saying. […]
@sull@yagankiely@keithcalder Correct me if I'm wrong, but Twitter didn't do anything that RSS or Atom couldn't have been extended to do, except make the publish/subscribe process palatable to mere humans.
@20gnd it was a 50/50 shot that Dave would join early. in ways, it is exactly what he has called for and he likes being a "customer" and dislikes the Twitter business path. but sometimes you gotta sit back and watch to see whats real. i get that.