Molus

Decentralization Dilemma

Decentralization Dilemma

A big part of the reason that Molus exists today is because of my ponderings regarding decentralization.

I have spent ample time researching software like: ZeroNet, IPFS, Scuttlebutt and other projects associated with federation or P2P

2 things seem to always pop up with these projects:

The relative difficulty of running your own as an absolute beginner

The eventual centralization on top of the most well-run versions (like Matrix)

1. Beginner difficulty

After spending a few years on a Linux machine, I can safely attest to being someone who is aware of apt-get update or pip install or whatever other commandline knowledge is required for installing/managing software on servers.

I am by no means a solid SRE, System Administrator or "DevOps" person, but I can get by.

The average non-tech person does not have (or even feels the need) to possess such skills. To be able to manage a portion of services for some specific software, will always require some technical knowledge. This is evidenced by the ever-simpler torrents scene for pirated content. Once you knew how, torrenting was easy.

Going from: login to Windows > open Chrome browser > land on google.com > search for Facebook > click, redirect and then proceed to login to Facebook

To being able to successfully use torrents was the difficult part and a steep learning curve for most.

The well-meaning intentions of advocates for decentralization will always face this stumbling block.

The 2 important keywords here are:

Learning-curve

Adoption-rates

2. Eventual centralization

Ignoring the gradual decline of IRC and other chat protocols, let us assume that Matrix.org is successful in getting people back to chatting on federated servers. The important observation is the eventual re-centralization on top of the most popular federated servers. IRC could have been a million small communities running their community-based chatrooms. Instead, we have 10-100 popular IRC servers, with Freenode being the most well-known among casual techies.

I suspect Matrix.org will face a similar problem, as the convenience of just joining their network will trump the efforts of managing your own servers for your own community.

You have to ask yourself if history will keep repeating itself as we attempt to decentralize communications, only for convenience of the end-user to cause re-centralization.

Keywords to take from here:

convenience

Postulating a theory

The learning-curve of any decentralization technology is inversely related to its adoption-rate.

Faced with the dilemma of running their own version versus using existing infrastructure, the user will always choose the latter for convenience.

Expanding on the theory:

When referring to adoption-rate of the technology, it is the actual managing of the servers to keep in mind

When referring to choosing existing infrastructure due to convenience, it is end-users we should keep in mind

Each sentence is its own separate theory, but they are related

This theory can be bashed, scrutinized and discussed. It is based on personal observation, which has bias. It is not based on broad empirical data.

It does serve as a means of justifying the existence of Molus and our experimental organizational models.