Why I’m Supporting App.net

When I first heard about App.net a few weeks back I was intrigued. On the surface it sounded all too similar to the ill fated Diaspora initiative aiming to create an open alternative to Facebook. I didn’t feel that the Diaspora team was able to accomplish their lofty goal. They just didn’t seem to have enough knowledge, experience, as well as a solid plan to execute their mission. App.net is the brainchild of Dalton Caldwell. Unlike the Diaspora team, he appears to have the experience and reputation to execute this project.

Interestingly enough, just as Diaspora was seen as a Facebook alternative, people have latched onto App.net as being a Twitter alternative. Actually App.net has much loftier goals than simply supplanting an existing top tier social network. At a high level the goal of App.net is to create a paradigm shift in thinking. Instead of using social networks that are free because of their ability to gather information about us for advertising and marketing, create a pay to use service without ads where we own our own data. That’s the high level thought gist of it. Sure much of the features and functionality that is planned would be similar to existing social networks but it’s limited thinking to only consider this as a competitor to existing social networks we’re familiar with. With an open and developer driven platform it can essentially become a social network and offer many different features and functionality not possible elsewhere because this paid service needs to please the users, not the advertisers.

But I still wasn’t sold on App.net as I’ve become quite excited following the Locker Project and Singly initiatives. It sounded in some ways to be similar to what App.net was planning to do. Also there are many existing open standards that have been in the works for a few years that should be leveraged and not re-invented. The most relevant one from a social data standpoint would be Activity Streams. The other concern is how truly open will App.net be? Will there be an open source client available that will allow bi-directional communication between it and other services?

Well I went from intrigue and confusion about this project to some excitement today. First I went and read Brennan Novak’s post which besides shedding some more light on this project, also had a wish list of sorts that he felt might get the folks that have been part of the Distributed Social Web or Indie Web on board. Then I followed through to the response posted by Dalton Caldwell where he publicly stated support for the items brought up by Brennan. The list included support for Activity Streams, Pubsubhubbub, Webfinger open standard initiatives as well as a lightweight open source client and some other items.

This was starting to sound promising but I still wondered how Locker Project / Singly factored in to this. I sent out a tweet to Brennan:

It wasn’t too long after that in which Brennan responded along with a cc to Jeremie Miller who is a co-founder at Singly

A few hours later Jeremie responded stating that Singly is definitely supporting App.net
https://twitter.com/jeremie/status/234426292689326080

So now I went from excitement to elation. App.net plans to support many existing open standards, offer open source access and now we’ve confirmed Singly support. There also seems to be quite a few other key players showing support for this project. You know what else is cool? That unlike Diaspora which didn’t have anything to show for months after getting funded, App.net already has an alpha version up and running. Here’s the global feed and here’s Jeremie Miller’s page. Beyond that, developers are already creating apps for it including 2 for mobile and a web app.

So you still might be thinking as many others have…who cares? You think of networks like Facebook and Twitter as throwaway services and you don’t care about the deal you make by using the service for free without much control or ownership of data. Well as long as you’re vigilant about how you organize source data and have ways to back up what you publish to those systems great. But most people don’t do that. I wrote a pretty important post earlier this year on How to Preserve, Prepare, and Produce Your Digital Legacy. It was my belief at the time that a service like Singly or now App.net could provide us with the ability to have much better flexibility and control to both share our digital data as well as preserve it for future generations. Most people aren’t thinking this far ahead as we’re still in the early stages of the web and digital data but I think as time goes on preserving these rich memories in a way to share with future generations will become more evident.

So tonight I backed App.net. Do I think this is the answer to what I and many others seem to be looking for? I don’t know just yet. All I know is that I want help get behind and support this project and all the other great like minded folks that have a similar vision for a different type of social network. One that is based on open source and open standards that serves the users. Sitting back and waiting for it to happen on its own is not an option. Others have provided their reasoning to back it as well. I’m optimistic that even if this project isn’t the be all end all of social network utopia it will definitely push the ball in the right direction. As of this writing App.net has received 450k of their 500k goal to move forward with 49 hours left to fund it. You can join me and the others here.

P.s. I applied to join the alpha but they seem to be backlogged fulfilling requests at the moment so I can’t share my profile yet. It will be here once I get in. See you there!

Update: My profile is now live.

About The Author

7 thoughts on “Why I’m Supporting App.net”

  1. “App.net plans to support many existing open standards” – Where did you see that ? They completely ignore them, explicitly siding things like activitystreams and reinventing the wheel (see https://github.com/appdotnet/api-spec/issues/15). No federation on the radar either.

    For me it remains a commercial, closed silo, without any more guarantee on openes/freedom than twitter. I fail to see how their model is more ‘pure’ that the ad-based model of twitter. All this ‘alignment’ talk is BS. They are a company, they do business, and that’s normal btw.

    True solution is indeed open standard based approach. And the list of services federating around OStatus keeps on growing. That’s where I’ll keep putting my $ and coding time 🙂

    But now that you are an app.net user, I hope you voice your concern for open standards. After all, you are paying for this 🙂 That’s may be where the solution eventually comes from, paying users asking for this (but would open federation be aligned with their goal of making money ?).

  2. Laurent, in my post I linked to Dalton’s post regarding support for Activity Streams, pubsubhubbub and more which is here http://daltoncaldwell.com/a-response-to-brennan-novak . I don’t side with the “purity” issue, although another interesting approach, it wasn’t the reason I backed this project. As you see towards the end of my post I don’t know if this can become the service I’m hoping emerges to provide what I’m looking for, but at least they’re trying something different and seem to be getting some great support off the bat.

    I’ve seen many open standards and initiatives flounder over the years and I see many folks criticizing what app.net is doing and if instead of sitting on the sidelines complaining, if they come up with a service that provides a better solution, I’ll be the first in line to back them as well.

  3. Pingback: There’s a new social network in town (sort of) | Bazaar Daily News

  4. Sorry, didn’t see that one. It is indeed a major commitment, and diverts from what was previously stated, especially in their Github tracker. Great to read that they are listening/answering to the community.

  5. The ‘pay-to-play’ model is a bust.

    For this type of service to be successful, all of your friends must be on it. If even 10% are too cheap/broke/apprehensive/etc. to pull out their credit cards, that’s a problem.

    Solution: Freemium. Ads aren’t evil. If you’re cheap, you get ads. $50/year, no ads. Seems simple, why don’t they do it?

Comments are closed.