Doesn't Facebook-connect (and FB apps in general) effectively give you the ability to buy/rent their network effect already? Thus eliminating the "no friends and no files" notion?
That's the idea, at least.
Unless you're going to provide free infrastructure for every component (not just the social graph) there will be an element of lock-in to virtually any social product.
This isn't a morality tale, I'm just pointing out what kind of decisions would be made around App.net and that the Vine/Instagram example doesn't really make sense.
This type of interoperability combined with sections of their API that are public (tokenless) provide a way to consume App.net content without needing an account unless you want to participate.
Then there are 3rd party apps and additions that bring even more open interoperability.
For development, there is Dev-Lite, so if you want to play around with the API, you don't need to spend $100/year until you're ready to join their Developer Incentive Program. And most Developers that have built anything for app.net have made their $100/year investment.
And App.net's annotation are another great example of creating new open standard of interoperability. These attachments can be added to any App.net API primitive to provide additional structured data to enhance interoperability between developer applications. Here's a link to their document repository for this: https://github.com/appdotnet/object-metadata
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?
My basic point is, the app.net vision is fundamentally flawed. It's not just a matter of positioning/marketing. It's the same fundamental flaw that google wave had. The vision is that app.net is a protocol, but you can't market protocols to people. you can only market apps. or more specifically, you can only market specific solutions to specific problems, or some fundamentally human vision (rather than a technological one)
With the app.net vision, any app you get that happens to use app.net as a back end will be subtly and frustratingly broken in some way because there's this feature, or that feature that your friend used that you can't see, because you have the wrong app. There's no commonality, there's no ultimate app that does all the things. With twitter, at least you get a link, something everyone understands, to a webpage, read in the ultimate universal client-a web browser. On app.net you just get mysterious silence. and "oh, that didn't work for you? huh..."
app.net is the linux of social media. Nerds love it but mortals will never get on board.
(Note: app.net might pull those dirty tricks in the future, but at least they've got a business model that doesn't _require_ them too)
> Imagine this. You sign up for Vine, and build up a robust friend network and library of videos. But then you try out Instagram’s new video sharing, and decide you like its editing features a lot better.
> Normally, this would mean starting over, with no friends and no files. But let’s say that both of them were just applications that ran on top of App.net. Instead of starting over, when you fired up Instagram for the first time, your friends and videos would be there waiting for you. That’s App.net. Or at least that’s what it wants to be.
Up until I read those two paragraphs, I couldn't shake the notion that it was really a Twitter clone that didn't want to be pigeonholed. Now I get it.