|
|
|
|
|
by dasil003
4682 days ago
|
|
The fact that you said "clients" instead of "apps" shows that you still don't understand the vision. App.net provides functionality that you can safely build an app on, and which is fundamentally more useful than the sandy foundations of Facebook or Twitter. That functionality is something which is non-trivial and which has potential network effects. You can use that functionality, you can extend it to something private to your own app, or you can mix and match with all the compatibility compromises that would entail. You can do all this safely without worrying that the rug will be pulled out from under you just when you figure out a magic formula that works. In short, App.net is something with the potential to build a business on, whereas anyone trying to build a serious business (as opposed to just doing something cool) on Twitter is an outright fool at this point. |
|
what on earth makes you think they are not?
I understand the vision. But I also understand, as someone who has used app.net, in actual fact, simply porting your social graph into a new app does you no good. You still have to convince all your friends to also get that same app before they can see what you post with it. The vision only works with basic media, like text, and photos, posted in a very straightforward twitter-like way.
I'll give you a specific example: Group chat with photos. Yep, there's an app.net app that does that, and now, you can't see the photos unless you have that app. so what's the point? what's in the vision for this situation?