2 ms·
I will post another comment. This is the problem with centralization. A service that is centralized in the hands of the person or organization hosting it leave
by EGreg 13y ago
I will post another comment.
This is the problem with centralization. A service that is centralized in the hands of the person or organization hosting it leaves all the power in their hands to change the rules on a whim. We are lucky that pg is reasonable and cares about feedback. Remember what happened with the facebok newsfeed? Also, democracies don't mitigate all the problems of centralization. Facebook even attempted to have a vote on the new privacy features, heavily promoted it, but had a ridiculously low turnout. Most people don't spend their time on sites trying to govern them, but simply use the tool.
Compare this to decentralized systems like git or the web. Any particular publisher's decision is mitigated by the fact that the audience is small. Even if this while site disappeared tomorrow, the web would continue to exist. Can such a principle be implemented for communities in general?
Yes. But it requires open source software to be installed and published by many people, and clients could interact with publicly signed versions of servers (or their plugins). The key question here is who is trying to protect whom and why.
When a small group forms (such as the discussion thread) the participants are the most interested party, and if the host changes something from what they expected they should be able to fork the discussion and easily continue it somewhere else.
On the other hand, a publisher who is interested in trying out a new (version of a) plugin can install it and see people's reactions. If they like it, they may start more discussions hosted by this publisher.
But the key to a "free market" in improvements is the switching cost. People should be able to easily move the entire discussion somewhere else in case the particular installation has been sabotaged.
Ideally such distributed software could be a bitcoin agent.