1. 6

For some reason, it goes without questioning that networked applications of significant complexity require a centralized server. Much of the nature of the web and the cloud are basically a result of this. In a number of cases, it’s relatively legitimate. Some things just are significantly easier when fully centralized, operating over consistent state. Programmers understand this from experience.

I suspect we assume this constraint because of incidental, lower level technical constraints.

One is NAT traversal. I’m not going to explain it in depth, but in short it means that two users on their regular old computers connected to the internet can’t get their computers to talk to each other without another pre-designated computer somewhere in the middle. This implies at least minimal centralization for any peer to peer protocols.

The second technical constraint is that the current networking paradigm is conversation centric, rather than content centric. This means that effectively the only means of receiving or conveying information to or from other nodes on the network is a one to one conversation with those computers. (Yes, there are nuances to this, but they don’t fundamentally change the argument, so I won’t get into them.) This means if you want information from a large number of different sources (which is what would happen in a distributed social network), your computer has to start a large number of conversations. This is full of complications and makes the peer to peer social network via conversation centric protocols an untenable project.

So why do these both matter? Well, centralized services can be both cheaper and more expensive to run than decentralized ones, depending on the problem you’re trying to solve. It’s terrible that we have to see ads on all the services we use, but we’re also not willing to pay enough to use them without the ads. But if they ran on our computers, and our friends computers, rather than on BigCo’s servers, then we wouldn’t have to pay, except for our own power, internet, and computers. Again, not all services can be decentralized like this, but some can. I see it as a social problem to put so much control over the ways we can interact into the hands of any single party, no matter how benevolent.

But, because of NAT traversal and a conversation centric approach to networking, the simple fact is we can’t do those sorts of things. IPv6 can help because it gets rid of the necessity of NAT traversal. It doesn’t mean there won’t be any more NAT traversal, but that it won’t have to be there. This means arbitrary computers can just start a conversation with each other. But, it only allows conversations, given the current set of network protocols in wide use. Content Centric Networking can help because it provides a mechanism to request a piece of content directly from the network itself, rather than asking individual computers for it. This means it is theoretically possible to gather information from a large number of sources efficiently, without any central computer needing to be involved.

Unfortunately, IPv6 is taking a LONG time to get into wide use, and CCN isn’t even a fully fleshed out idea yet. I still think they really matter, and even if I haven’t been able to persuade anyone else that they do, I hope this at least starts a conversation about it.

  1.  

  2. 2

    Huge caveat: I’m no network engineer, just an interested programmer who’s poked around at wiki articles and whatnot a bit. It might be that these technologies can’t actually solve these problems, but to the best of my knowledge they can. Happy to be shown where I’m misinformed if I am.

    1. 1

      I think that the security concerns with publicly accessible IPs will make IPv6 communication just as restricted as IPv4. Windows (and Mac OS?) ships with its firewall turned on by default which is going to block any incoming ports, so you’d still have to do the secret handshake stuff to allow inbound communication from a remote host.

      1. 1

        Communicating with a firewall on the local machine would be way easier than the gymnastics required for NAT traversal.

      2. 1

        I agree with you about end goals, and that NAT and current models of interaction are a problem. The situation isn’t an accident though, and these problems have a common cause.

        We started with an Internet in which services were mostly decentralized. Today they are mostly centralized, except for a few things that remain from an earlier era (e.g. email). This trend is unlikely to reverse, because commercial services (which are all centralized, because it’s hard to make money otherwise) have a huge economic advantage over decentralized, community-run services.

        The lack of resources being put into e.g. IPv6 is just one symptom of this situation.

        I don’t know what the solution is, but I do know that we’ve got to up our game if we hope to make a change.

        Dmytri Kleiner gave a great talk about this a few years ago: https://www.youtube.com/watch?v=112d45b03hM