Bring On the Decentralized Social Networking
- the end of horror stories about accounts and company pages being shut down arbitrarily by Facebook
- privacy settings that give you fine-grained control, and that are not forcibly changed for you
- an ad-free viewing experience (depending on the policies of the node hosting your profile), and
- the easy implemention of desirable features in the interface, without waiting for a single company like Facebook to adopt them.
(Not to mention an interface that stays relatively stable until you decide you want to change it --
no more waking up to find out you've been "timelined".)
Consider the main things that we use Facebook for today:
- Finding old friends and re-establishing contact with them.
- Receiving a stream of updates from your friends, viewing photos, posting comments, etc.
- Creating events and inviting friends.
- Creating branded pages for your company or product that other people can "like," and receiving updates from pages created around other people's companies or products.
There's no particular reason why any one of those functions could only be carried out on a
centralized system. I can envision a distributed protocol with many different servers, or 'nodes,'
run by different hosting companies, and each 'node' can be used to store many accounts; users pick a hosting company and a node to create their new account, and their account on that node could be used to store their friends list, their photos and status
updates, and any events and groups that they had created.
I'll get to the protocol design in a second, but let me emphasize something more important first: to make the protocol censorship resistant, it would have to be possible to move your entire account from one node to another node at
a completely different company,
without breaking any of the existing links with friends, your events, etc. That way,
the node hosting your profile wouldn't be able to lean on you by saying, "Delete that one photo
you posted, or I'll delete your entire profile and you'll lose all the friend links and
events that you created."
To make a profile "seamlessly portable" in this manner,
my suggestion would be to have the profile associated with a domain name owned by the
user, with a URL like http://yourdomainname.com/profileprotocol/yourusername/.
The domain name could be hosted with any hosting provider, as long as you paid their hosting
fee (or as long as you were willing to display their advertisements to people who viewed your profile). But if your hosting company ever kicked you to the curb, you could simply change the domain name to point to a different hosting provider, and be back up and running after just a few hours of downtime (assuming you had backups of all of your data!).
No one would be able to shut
down your profile permanently, unless they wrested control of your domain name away from you, or convinced every hosting provider in the world not to host you. (A user who didn't want to bother
with their own domain name, could still host a profile under someone else's domain. This would probably be the default option for most casual high-school users, and thus companies
like Facebook could still exist to serve them by helping them create new profile accounts in two minutes. But
then those users would have to accept the risk that the domain name owner could shut their profile down.)
Thus I'm distinguishing here between two levels of censorship-resistance that could be provided by a
distributed model. In the weaker type of censorship-resistance, profile-hosting companies
would compete for your business by providing more permissive hosting policies, which would enable
people to post edgier content than Facebook currently allows --
but once you're hosted with a given company, you couldn't easily switch without breaking
all of the inbound "links" from your friends' accounts, so your hosting company could force you to
self-censor, by threatening you with the loss of your account. In the stronger type of
censorship-resistance that I'm advocating, you could switch seamlessly from one hosting provider
to another, as long as you kept control of your domain name.
Of course this is exactly the type of "censorship resistance" enjoyed by people who run their own websites under their own domain names. The challenge would be to bring the same freedom to an open social networking protocol, but I see no technical reason why it couldn't be done.
Consider a protocol where "Bob" creates a new account on a social networking hosting node (together with a public/private key used to authenticate his actions to other nodes — if you're
not a crypto geek, don't worry about that, it just means that users wouldn't be able to forge
friend requests, "likes," event invites, etc. from other people).
"Bob" could then
find the profiles of his friends, and add them to his own "friends list" (which would be
stored on his node). If Bob adds Alice as a friend, then Bob's node can also download
Alice's current friend list (unless Alice has disabled this feature, or unless Alice
has customized her friend list so that only portions of her friends list are viewable
to other users — something not currently possible with Facebook). That way, when Bob searches
for new names of users to add as friends in the future, the search will first default to
searching the friends-of-friends lists that he's downloaded from his own friends.
When Bob signs in to his account on his node (either through a web interface, or a dedicated
application, or a mobile app), his "news feed" consists of the comments, photos, and
other items that have been published from his friends' accounts. He can post comments on any of his friends' items, which are then transmitted to his friends' accounts and stored on their node along with their content, unless they choose to delete the comments.
And of course he can publish his own photos and status updates just like we all do on Facebook today, which would be downloaded to his friends' news feeds. (I'm hand-waving over whether the notifications would be "pulled" by users' nodes periodically polling the nodes of their friends to check for new content, or by their friends' nodes "pushing" the content to all known subscribers.)
Alice could meanwhile create an "group" of users would would be stored as an object on her node, and invite other users to join the group. Then any messages or content posted to the group would show up in the news feeds of all users who had joined. And Alice could
create "events" which are also stored as an object on her node, and send out invites to her friends or other members of her groups. Pretty much any Facebook feature could be duplicated
in this distributed system, with the benefit that users wouldn't run up against aggravating
limitations imposed by Facebook — like the fact that Facebook used to
block
you from
messaging the guests of your own event after it
reached 5,000 attendees, and then
removed the ability to message
guests of an event entirely.
There's only one Facebook feature that I think could not be implemented on a distributed social networking protocol, and that's the practice of accruing hundreds of thousands of fans for your
company fan page, basically as a form of
"social proof" to show potential new customers that you're
serious. Under Facebook's model, if you see a fan page with hundreds of thousands of fans, your first instinct is to assume that the company must be doing something right in order to be that
popular, since Facebook makes it difficult for a company to create hundreds of thousands of fake users just to be fans of their product. On the other hand, in a distributed model, suppose I run
across a company's fan page which claims to have 1 million fans. It's not just a case of the company lying about having 1 million fans — you could use digital signatures to verify that 1
million "users" really are "fans" of the product — but since anybody can set up a profile hosting node, you have no way of knowing how many of those 1 million "users" are real. "Acme Soda Company" could have just set up a dozen profile hosting nodes and created 100,000 fake users on each one, and have each of them sign up as "fans" of their product. (I just made up that company name, but this is incidentally something the
real Acme Soda Company
is apparently not doing.)
But how useful is it for regular users, after all, to see that a company has hundreds of thousands of fans? I've never assumed that a company makes a quality product just based on the number of Facebook fans that they have. I'd be more interested in checking out a company if a high proportion of my own social networking
friends are fans of the product — and that is something that could still be implemented in a distributed model, since if a company claims that 3 of my 100 friends are fans of their
page, I could use their digitally signed "fan" relationships to verify that this is true.
So I hope that the future of distributed social networking arrives soon. It may or may not be in the form of the Diaspora Project (in true Dr. Evil fashion, their most
recent press release announced that they've already attracted "thousands" of users), but there's no particular reason that a distributed protocol would have to be a grass-roots
effort. My guess is that if it took off, it would have to be started as a side project by an established company that gave it name recognition, and which could possibly provide
free hosting for the first wave of users. Google+ never gave most people a compelling reason to switch, but imagine if it had been released not as a website but as an open protocol, complete
with an open-source implementation that could be installed anywhere. Thus, complete freedom to create pages with whatever content you want, to amass as many fans and subscribers as
you could legitimately earn, without having to worry about it all being controlled by a single
entity who could mine your data or delete your content. I definitely would have given it a closer look.
Joe Sixpack has one question: WTF you are talking about, who is centralized, and why should I care? Seriously, geeks are 1% of Facebook audience, 99% couldn't care less about "decentralization".
839*929
People don't want to run hubs or have to do complex setup just to talk to people. Freetards once again fail.
cool story bro
But binaries ruined it !!
Release a product.
BOOM roasted
just how many users are there on Diaspora?
Hey Bennet your link is about it Diaspora becoming a community project not about opening the source code. Since, you know, it's was already open source and on Github.
But this approach also has disadvantages which are not explored. The exposition above seems to assume that Facebook act randomly in removing photos and in removing features, but that's clearly not the case. There is a reason they remove certain photos and a reason they remove features (e.g. if they are abused). This system would bring all the abuse back, unless designed with those abuses in mind - but all I see here are advantages, no disadvantages or even cautionary notes. Maybe people don't want a Facebook alternative where they are spammed left right and center, and on which people host porn, for instance.
Wake me up when you have some news. Thanks!
Personally I think that so-called "social networking" contributes to the achievement of the opposite of it's intent: It actually keeps people apart rather than bringing them together. It has created another, deceptive definition of the word "friend", whereas now you have "Friends" (with a capital 'F', for your real, actual friends) and "friends" (with a lower-case 'f', for your online 'friends', who very often may as well be 'bots for all the real meaning they have to your life). We have an entire generation of kids growing up who are more sociall awkward than ever before, because "social networking" gives them an excuse to not learn to interact with each other on an in-person level. I'd like to see people outgrow all this so-called "social networking" and get back to actually relating to each other in real life.
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
yo, '95 called and wants it nerd social networking back(and irc).
isn't this the second article about diaspora becoming _UNMAINTAINED_?
world was created 5 seconds before this post as it is.
Anyone so inclined may run a webserver, with various forums or bulletin boards or private guest pages or whatever. As well as mailing lists. All of that is social networking. We've been there for some time - but without a brand name like 'facebook'. The Internet itself is a social network.
The idea of a central company having complete control of my information and social network is just absurdly bad, to me. I don't care what privacy protections they give assurances of, that information alone is so powerful in the hands of those who would seek power, it is literally irresistable. It is a testament to how little people give thought to their everyday actions that so many people use Facebook.
Replace "facebook" with "a 3-letter federal agency" performing the same task, and the outrage would be unquenchable... but somehow people trust Facebook not to betray them. I just don't understand it.
I swear they give me mod points to shut me up.
We need an Internet Bill of Rights to outline our goals around privacy for citizen infrastructure. Then we can move these projects forward. It needs to cover email, chat, social networking, voice, Skype/video... Please read my first draft and provide feedback: http://matthol.blogspot.com/ Also I don't like that Diaspora requires servers. I email, chat, social network, video calls etc should be P2P based on each person having a PGP key. And let's be clear that if we want to have the true democracies that we all deserve around the world, we need secure and private evoting which also depends on this same infrastructure. Let's get this thing done!
You already can run your own web server free of any corporate oversight. Guess how many people do.
You can already run your own mail server free of any corporate monitoring. Guess how many people do.
Diaspora failed because they thought people cared about these things. Guess how many people do.
People use Facebook/G+/Twitter and whatnot because:
1. Everyone else is.
2. They don't have to run it.
"I use a Mac because I'm just better than you are."
1. No farmville
Congratulations, you lost 99% of potential users.
2. No mention of abuse
Sometimes pictures and profiles are removed for good reasons. Without that oversight the decentralized network would be much like the hidden web - overrun by places like silk road and so on. Not to mention all the photos posted without someone's permission. Not that I care much about copyrights, but what about someone posting nude pics of their ex, to shame them? No safeguards.
3. Too complicated.
Congratulations, you lost 99% of potential users.
Really, I could go on and on, I could go into detail, but you're over-thinking it... The average user couldn't care less. If it's complicated, it's not going to get chosen over the easy option. Figure out how to do ALL that you wrote about, with absolutely no technical know-how, and make it work as seamlessly as facebook or similar sites, then we're talking.
Oh, and don't forget the games.
We've had these forever. It's called a BBS. Current implementations include PHPBB and VBulletin
...but if I sign up for Alice's network, and ten of my friends are on Bob's network, and another 35 are on Charlie's network... what do we gain by belonging to 3 separate networks?
If the content is all federated (Alice's network pulls contact info from Bob's network, etc), it acts the exact same as Facebook does for the end user.
This to me sounds like an arbitrary barrier to social networking. My friends don't fit easily into social network "buckets", and nearly none of my friends have time to sort and connect to various federated sources of information. They have 15 seconds to check one spot - facebook - for notifications, messages, and status updates. The really hip ones use Twitter.
So really: Sell myself and my friends on this in one sentence. "It's not facebook" is not that sentence - if Google can't make that work, neither will geeks trying to precisely bucket social communication like we were robots instead of messy, finicky humans.
hookers and grits.
the end of horror stories about accounts and company pages being shut down arbitrarily by Facebook
And the beginning of horror stories about fake accounts, porn pics getting scattered about willy-nilly, and countless "what if the password reset gets hijacked?" claims, problems, attempted (bad) solutions, etc. Yes, the decentralized model is clearly the way to go.
Fat chance. What is needed is a "new" centralized Facebook, but by a company that doesn't have to justify a $100B valuation (perhaps built purely on open source code) with the only stated goal of being "good to users". If Google+ can't gain critical mass (although it might, eventually) then I doubt any other such concoction has a chance. You are more likely to see Facebook "utilitied" by the government after being convicted of having a de facto monopoly. Maybe then, some of those things that Facebook seems to do wrong can get changed for the better (with a heaping helping of things changing for the worse).
amusing how Trend Micro blocks access to this site http://global.sitesafety.trendmicro.com/
You're describing a system that runs on any host, can be transferred easily, and is fully customisable by the user to show whatever text and pictures they want. Frankly, I struggle to see the difference between what you're talking about and "a website". OK, you've got connections to other users, but this isn't anything that can't be handled by an inbuilt XML feed in an agreed format. Define a common socialXML format for all websites with some fairly simple authorisation system (Oauth style) and you've got everything you need to make any website you can think of "social". If we're decentralising why lock everybody into the very small feature set of Facebook or whoever?
Please consider this account deleted, I just can't be bothered with the spam anymore.
I'm increasingly seeing Facebook crack down on pages for reasons which seem silly and arbitrary. I've had a friend whose criticism about a movie was removed by Facebook admin. Yesterday, a business which sells e-cigarette products had their page shut down by Facebook. The explanation: Facebook's policy prohibits marketing tobacco and they include e-cigarettes in that category.
There's nothing wrong with the concept of social networking itself, but it's survival will depend on decentralization.
And as far as Diaspora's use requiring skills and know-how that, currently, most people don't possess...give them time. I remember an era when people complained that setting the clock on their VCRs was too difficult. Nowadays, most high school students know how to work Excel and many high schools even teach college-level Java programming.
I'm an old fart who has gone back to school and, during class recently, I had a brand new TI-84 which did not have a Quadratic Formula program on it. I mentioned it to a classmate young enough to be my daughter. She asked for the calculator and handed it back to me two or three minutes later. She had programmed a Quadratic Formula app it in for me.
People can learn stuff when they feel like there's an incentive to learn it. Don't underestimate the incentive that is people's ability to post cat photos.
timothy has eloquently expressed with good detail what I believe. I have told friends, family, and acquaintances that the pinnacle of social networking will not be another centralized offering, but a distributed model. This is nothing new: the FOAF (friend of a friend) protocol with its cousin, the Semantic Web, was bandied about in the '90s, and in more recent, pre-Facebook days by Tim Berners-Lee.
I cheer loudly for Diaspora but I'm painfully aware of network effects: Facebook already got grandma and grandpa, a herculean tech task in its own right, and I doubt the confusion of an anti-statist social network protocol will get many friends out of the gate. I'm still cheering for it, though.
Finally, I strongly believe that half-hearted, amateur implementations of new social network nodes will damage the "brand" of distributed social networking. There needs to be a monetization tool ready from the start, be it advertising modules, e-commerce and credit card processing (unfortunately), PayPal hooks (frightening!), BTC—whatever. A good start to distributed social networking can't depend on the work of the good graces of some well meaning hobbyists donating server space.
Cloud computing was an utter failure. Decentralized cloud computing is the future of the internet when laws like SOPA/PIPA/ACTA become the norm.
Don't just virtualize/deventralize some crappy "social" network. Social is just a trend, social won't last.
Virtualize the whole fucking web, enforce default strong anonymity, make every node a proxy for the outside, anonimyze uploads of content, fragment the data, encrypt it.
Make it an "app": hipsters, applefags and whatnots will finally be able to make something usefull out of their gazillions shiny toys.
And most of all don't let Kim.com, Pooperberg and alikes eat all of the cake first.
Google actually introduced a number of open protocols to support social networking and federation of independent networks (some alone, some in coordination with other players), including reference implementations of many of them, long before introducing Google+ (Additionally, Google's gotten behind open protocols that were introduced by others.) Examples of protocols Google developed (alone or with others) specifically for or with application in the social space include OpenSocial and PubSubHubbub among others. Third-party open specifications in the space that they have promoted and leveraged in the past (some still currently) include OAuth, FOAF, and others.
So you don't need to imagine what would happen if Google produced and released open protocols instead of Google+, since they did that before Google+. What actually happened was...well, not quite nothing, but hardly an eruption of decentralized social networking systems displacing centralized systems.
It's funny how Bennett thinks that the release of diaspora as open source would be a step forward towards the success of that platform. The sad reason behind that release is that the money is out and the developers don't see a way that diaspora would give them any income, so they couldn't continue working full time on that project and had to move on.
Of course, they're not gonna say it's dead but "release it as open source" (after all, some other guys could continue the work, right?) but there's not gonna be any full time core team behind the project simply because it's not a viable model to pay the rent/mortgage.
IIRC, the initial funding about 2 years ago was about $200000 for 4 devs. That's $25000 per dev per year. It would take a lot of idealism to continue working full time as a dev for that money, and even more so for $0 now that that money is gone and there's no income in sight.
Facebook is a monstrous data bucket that is never full and is never emptied. We've already seen job applicants being asked for their facebook logon info so that potential employers could see what was stored on facebook. People want a way to communicate informally with friends and family without those personal communications being stored, tracked, and logged for 50 years and then distributed to irrelevant future data leaches. The Diaspora distributed approach is the direction that this needs to go.
Decentralizing lets us run our own 'servers', linking these together into a whole constellation of users. Right?
- Is it safe to assume that some servers will not be configured the same as others? If so, then will I see 'friends' out 'there' with different bits of data available to me? Inconsistency is the hobgoblin of restaurants and web services. This is not good. It sure isn't an improvement. If I want more granularity, I will also suffer from others granularizing themselves into irrelevance. Then I get sleepy.
- Am I expected to trust other adminstrators? Sure. Now I get to decide which of thousands (millions?) of admins I am willing to trust. And this is an improvement how?
- Disapora protects my data from other admins snarfing it and giving it to whoever, right?
- You think it's a good idea to host these servers all over the Web? My ISP has a very different view of this, even if it is for a dozen family members who register a few dozen hits a day. Somehow, I betcha we end up with Disapora hosts that consolidate these servers into hosting sites. For a fee. How much do you think it's worth to me to offer my friends and family this social network? Discount that for the abuse I will take when I refuse to delete some unflattering post. Not really very attractive to me yet.
- These hosting aggregators would probably offer free sevice if I let them mine my data, you know. Back to the future. Mission accomplished.
I just don't get it.
deleting the extra space after periods so i can stay relevant, yeah.
StatusNet, Diaspora and Friendica already all support OStatus as a means of standard communication. It's a technology and protocol easily implemented in other software too, as all the technology in use is standardized and well-spread (Webfinger, PoCo, PuSH, Salmon etc.)
The reason most people haven't started using any of those services are of course the network effect. But with recent Twitter Api lockdowns and Facebook getting all kinds of bad press, maybe more users try to find alternatives.
The part you lost me at was here-
"
"There's no particular reason why any one of those functions could only be carried out on a centralized system. I can envision a distributed protocol with many different servers, or 'nodes,' run by different hosting companies, and each 'node' can be used to store many accounts
"
*I* can envision a distributed protocol with many different servers, or 'nodes', run by *the users themselves*, and each 'node' can be used to store many accounts...
Note that I've recently filed an FCC Form 2000F complaint about Google's anti-network-neutrality bahavior as they are entering the fixed broadband ISP market here in Kansas City, Kansas. It's something of a quixotic war about the right for all end users of fixed broadband connections protecting their FCC-10-201(p13) rights to create successful content, applications, services, and devices on the general purpose technology of the (IPv6) internet. You can read the 57 post, 14 author (out of 23 members) thread in the discussion forum of the Kansas Unix and Linux Users Association here-
https://groups.google.com/forum/?fromgroups#!topic/kulua-l/LxsOtdglNM0
I disagree. I think that monetization is what has created the current mess and the pressure on Facebook to be a profitable corporation will piss off users into fleeing at an increasingly faster clip. I also think that the future model of social networking will look more like the Diaspora model where people pay for their own hosting, write their own code or use software which expedites the process, and where people have a greater involvement in their online persona. There won't be a need for monetization in this scenario. There was a time where paying for television seemed absurd; tv should be free! (Free after you buy the rabbit-ear antenna.) Today, people regularly pay triple digits on their cable and satellite bill. So it isn't a stretch to think that people will pay for hosting, or form groups with friends to share hosting costs, to continue social networking.
I made a game, hosted on facebook that earns me a fair income from people spending facebook credits with it. ..... Facebook handle everything to do with credits, etc.... purchasing them, giving refunds, etc.
How can I make money, if Diaspora took over. Would people become too frightened to spend if there isn't a benevolent dictator to step in should they feel they've been duped?... If I cant make money, then I wont make stuff. No stuff, means a boring Social network
The media-hype name for it is "the post-PC era", but the point is that most people, most of the time, don't need a general-purpose computer sitting on their desk. They're happy with an updated version of the TV, a mostly one-way consumption device that restricts their activities to what's safe and easy.
We may look upon the last twenty years as an aberration, a time when the technology advanced to the point of being useful to a mass audience, but hadn't yet been pared back to only what was useful to them. After all, isn't that Apple's whole M.O.? Removing features most people don't need?
...yet somehow, email remains decentralized...
Palm trees and 8
I visualize a bit-torrent like protocol with a number of seeders, that maintain the locations of your distributed profile. A part of John's profile will be stored on Alice's system. Alice herself cannot view Johns profile since it is encrypted, unless Alice happens to be in John's social network. Alice is effectively seeding Johns profile in the background while she runs the client herself. John's complete profile can be recovered through torrent like hosting sites lets call this Bob. Alice and Bob will be remunerated via advertising ( say ) for keeping their servers up and the network healthy and available. Thoughts?
The value of Facebook isn't in the software. The value of Facebook is the user network. Good luck open sourcing that.
The FOAF project began in 2000, not "the '90s".
First you have to convince my family to switch to it, because the only reason I'm on Facebook is because that's how my family members (non-geeks) communicate these days.
But, before that, you'll have to convince everyone who is friends with anyone in my family to switch. And, you'll have to apply this recursively until you've switched everyone in the world.
Oh, and you'll have to add stupid games, because that's why my family and their friends are on Facebook.
But as soon as you do that, count me in!
Good idea, Anon Coward. Using BitTorrent would be a big departure from the client-server web service that we've all become accustomed to. Advertising depends on metrics (views/impressions, sources, clicks). I don't understand how these metrics would work in such a model, but I welcome the idea.
Due to how diaspora was designed, you're still locked in onto a provider.
Supose I have an account an serverA, and want to move to serverB. Sure, I can export my data, and import it into serverB, but there's no way to delete force serverA. to redirect my profile to serverB, or even delete it. My profile's URL is still valid, so people might not know/be sure I moved.
The obvious fix for this is to use my own domain on some free provider (maybe delegating the same way one would delegate e-mail). However, this feature was deemed too complex and won't be implemented.
My only choice is to set up my own pod. Of course, I can't be bothered since it's not at all an easy task (and this comes from someone who runs his own XMPP/email servers).
Whos going to run Chanserv and Nickserv?
... why should I care? ...
Well it could make the privacy situation even worse. There is no reason to believe that a node will not try to mine and monetize your data just like facebook, or try to censor some type of information they are hosting (due to local laws not a personal bias?), ... As a person objects to one node's policy and moves to another they are increasing the number of 3rd parties that have their private info.
Basically there is no free lunch. There is a potential downside to hopping from one node to another.
Diaspora has always been open source.
No disagreement here, NFiorentini: Forming groups to share the costs would work, as well. I merely think that the mechanism for collecting that payment ought to be included in a social network implementation, perhaps an extension to the Diaspora code.
I only mentioned advertising as one of the four monetization examples (among credit card, PayPal, etc.). Personally, I agree that I would like to avoid the advertising model. The person or business who pays money is the customer. The targeted audience is the product that the media sells. (I think "attention economy" is the term I learned from Wikipedia.) E.g. Google gets paid via advertisers (its true customers) and sells the attention of its users (its true product). The point in having a monetization model beyond advertising is that I, as a user, would be come the customer, not the product, and removing the motivation for the social-network node owner from selling my information.
Thanks, CRCulver. I stand corrected.
NNTP + HTML + a web browser + a few search tools. How hard is this, really?
-- Two men say they're Jesus. One of them must be wrong. - Dire Straits
I'm impressed nobody talks about Friendica.
He mentions in TFA that your comments are stored on the server you are posting to. If that is the case then how can I control who sees what I write on someone elses profile? Can I still edit/delete my own comments?
If by awesome you meant, enjoyment derived from looking for missing, presumed lost, parts of bloat-base64 encoded warez, then yes.
It reminds of of the qualities that have lent themselves well to UseNet (distributed servers all serving content).
Diaspora was fail before it even began by being written in Ruby on Rails. The idea that everyone was going to get Ruby hosting to run Diaspora was insane. The Diaspora project was never serious about it's alleged mission because there was simply no chance even the technically inclined among us would ever be able to conviently run it. The developers took a route that made it easy for /them/, and thereby doomed the project.
If you're actually serious about distributed social networking, it needs to be written in PHP or /maybe/ Perl. You know, the things everyone has in their hosting, not Ruby, Python, Erlang, Lua, or the wonderful new language someone invented last week.
...because "it's what everyone is doing", with no need to gather information and/or make choices. No system that depends on rational behavior and requires thought will ever be popular with more than a minority. That's no reason not to do it, though. Just don't expect to displace FaceBook.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Dude:
Everyone (technical or non) has one question: "Are my friends on Diaspora?"
Me:
"No. Diaspora is like Facebook, but for the kids that weren't popular in High School."
Dude:
"Oh, its ona these geek thingies [sic]" followed by:
"...then what's the point?"
Protip: timothy didn't write this.
The Big Question of 2012 is:
Will a babbler on slashdot change the destiny of social networks writing a long pile of bullshit?
Oh, yeah. Bennett Haselton did. I stand corrected.
I've actually started much of the work with public private keys in a decentralized social network. With the exception of having it on a peer to peer network instead of a federation of websites the idea described above is exactly the same as the one I came up with for this project. With a peer to peer network, you don't have to worry about censorship (unless the whole network is censored), and you don't have to worry about the website owner selling your information.
To get around the spam problem, you can simply not accept connections from people who you haven't friended or aren't friends of friends (finding your first friend may be a problem).
Porn won't be an issue since everyone is basically hosting their own content. If you don't want to see something, you don't have to friend that person. My guess is accidentally seeing porn won't be much of a problem since most people will have friends with similar morals.
Everything is open sourced. It's only me working on it so the progress is slow. Here's the github link: https://github.com/macourtney/masques
Strictly speaking, DNS is just a convenience system. All it does is swap a name with a number.
Using an IP directly isn't significantly more complex than using a phone number.
But even so, you have your "hosts" file, and you can use it as a purely local DNS if you like. You don't have to depend on the formal DNS system, we just do because it's easy, it's free, and generally speaking, it doesn't do bad things to us like censor or steal our data.
The solution is like email. You get your account, it lives on a server. Messages are sent to and fro, and some client program decides how you see the messages.
Seriously, this doesn't seem like something that hard. You could even build most of using email if you wanted.
Also look at Frendica
I mean, I will say I have no personal experience with this having not been alive at the time, but it is my understanding that in the early days of personal computers there were many email providers with proprietary systems that were not capable of sending messages between networks.
From http://www.cs.umd.edu/class/spring2002/cmsc434-0101/MUIseum/applications/emailhistory.html :
"In the late-1970's and 1980's the phenomenal growth of personal computers (Apple II 1978 - 1985; IBM PC 1983 and Apple Macintosh 1984) created a whole new genre of email technologies. Some of these systems were proprietary 'dial-up' systems such as MCI Mail, EasyLink, Telecom Gold, One-to-One, CompuServe, AppleLink etc. For two people to exchange messages remotely on these systems they had to both be subscribers. The proprietary systems did not interoperate or transmit messages from one system to another, or for the few systems that did these were notoriously unreliable...."
I guess I have the "advantage" of having been alive way back then :-)
From my limited perspective as a Californian geek who graduated high school in '86...
In the mid 80's there were a lot of BBS's, and many of them were isolated nodes. A fair number of them did pass messages back and forth, however. But the number of users back in the day was ridiculously small compared to today.
At the same time, in the 80's, all the major universities in the States had interconnected email. Again, the number of users was tiny - mostly CompSci majors. People studying others subjects very often did not own a computer.
In the late 80's, many of the small BBS's started to integrate with the internet (lowercase 'i', which used to indicate nodes that would store and forward email and news), and you could send and receive email to many different kinds of BBS from any internet node.
And, of course, in the mid 90's, we all explained to our parents what email is and how it works.
So there was a small window in the mid or late 80's when there were some BBSs and companies with proprietary email systems that did not connect. But at the same time (and for some time before) there was the university system. For the vast majority of people who heard the term 'email', the first time they heard it it was interconnected.
I fail to see how this is a problem. That's kind of the point of social networks -- you only see posts from people you have agreed to see posts from. Unless you're talking about the common 'message' feature on most networks -- in which case there's really no difference between that and email, and the same technology that manages to keep my Gmail completely devoid of spam should work just as well in something like diaspora.
When you look someone up on Facebook, you are searching one server and it has controls.
When you look someone up on diaspora, what's to keep thousands of zombie diaspora nodes from replying with bogus accounts hoping to connect to you?
From the other direction: have you ever received a spam friend request on a social network like Facebook or g+? Imagine what it would be like with the same connectivity as email, but with less context to determine if an invitation is spam?
Like many have echoed in here, nobody that isn't alrady passionate about stuff like this is going to really give a hoot about decentralization. You have to "beat" Facebook at their interface. Then people will like it. Here's my take - K.I.S.S. Facebook's interface is already very simple. We have to almost think of the old-school BBSes (the original decentralized social networks) and see how clean some of those interfaces were. I personally would love to see an ANSi re-implementation in HTML5. People *do* have the capacity to use the keyboard to navigate, and once they learn it, as long as it's efficient, people will start flocking. There's nothing wrong with a menu system - UI simplicity is Facebook's whole goal, after all. It's just that they have so much sh*t going on that it's almost impossible to do. That's everyone's problem with design. Not that I'm a designer, but I did make my own ANSi menus for Renegade back in the day. And they rocked.
It is pitch black. You are likely to be eaten by a grue.
It's actually a lot of fun, and I've met some very interesting people. Diaspora already has most of the features described above, such as federation. I like how you can follow hashtags also, because it allows you to see comments from people you don't already know, and thus make new friends, something which I feel Facebook lacks. There are some strong devs still out there and waiting to jump in the game, I think D* will stay alive and eventually overtake Facebook.
Kharma is like a boomerang. Mine is broken.
Most of what we call "social networking" can be reduced to a few services:
list of friends is - contacts and address book
messaging systems - email or instant messaging chat
newsfeeds
games
What I would really like to see is a greater ability to Work Offline and take back the data, a local fork if you prefer. With a decent data plan most people are happy enough to be always online but a greater ability to work offline makes things more useful to when you do not have a good connection or in the possible case of Facebook being unplugged in future. I lot of this I can do already, I can already download a big copy of my facebook history, it just is not very useful offline. I do have my contacts but it is not as rich an experience as the online face/phone/address book.
I'm cautiously optimistic I will get much of what I already want due to the push to centralize user data and make it portable every time a user loses their smartphone and wants to get all the information on their next phone, but the idea of being able to share less with the cloud and keep what amounts to a live, and private, local copy or fork of my social network could be very useful.
Full "lifetracking" even something as simple as tracking all the food you eat, could be very useful so long as you could keep it private and data mine it for your own health and wellbeing, but I wouldn't want that level of detail anywhere near the cloud.
Don't we already have decentralized networking? Isn't it called email?
Just wondering whether it's possible to have multiple ids pointing to your profile in Diaspora?
Similar way that you can have several secondary email addresses forwarding all your mail to your main email address.
I doubt normal users would be that much interested in acquiring a domain just to use it as an identifier for their profile. Instead having multiple secondary ids from different parties would sound more plausible way to protect your profile from getting locked to any one service provider.
Facebook is a DataVampire that sucks the info-juices out of peoples' interpersonal interactions.
No, email goes through "Servers" and thus can be cut off at a central point. Even though I have my own email server, it still goes through my ISP who still filters it for spam -- that can still be used accidently or on purpose to block arbitrary content.
I believe the point of decentralization is to not make it so easy for someone to filter your conversations and habits. Presumably, node-connections will support encryption, so those who monitor your connection won't know what you are sending without, at least, a little work....and that's about the best security we can have today...