Live data from Hacker News

Principles of a Decentralized Web

nicola.io

1–10 of 31 posts

Re: Principles of a Decentralized Web

#2
I don't think control of data, user or otherwise, is an inherent part of decentralisation. If fact it may be the opposite.

So as a principle for a Decentralised Web its a contradiction. Maybe it works as a part of a more broad set of principles (eg. a Healthy Web).

Re: Principles of a Decentralized Web

#5
post #4

An important feature of the decentralized web is that one Harvard/MIT person doesn't get to design it.

I'm not sure what your objection is. Why shouldn't one Harvard/MIT person design it? I mean, somebody has to.

If the web is to be decentralized in the same way that the internet is decentralized, it will be much better if it's never "designed" at all. If your app wants to talk to my host, cool. If it doesn't, that's cool too.

Re: Principles of a Decentralized Web

#7
post #4

Earlier quoted context omitted.

I'm not sure what your objection is. Why shouldn't one Harvard/MIT person design it? I mean, somebody has to.

If the web is to be decentralized in the same way that the internet is decentralized, it will be much better if it's never "designed" at all. If your app wants to talk to my host, cool. If it doesn't, that's cool too.

But you still need a protocol for the app and the host to talk to each other - and that needs designing.

And you need a way for the app to find the host; that needs to be designed too.

Re: Principles of a Decentralized Web

#8
Does the web here mean a network of hyperlinked documents, does it mean HTTP, or does it mean "browser stuff"?

Personally, I think we should retire the idea of The Decentralized Web. It doesn't help clear thinking. BitTorrent is one of the most successful decentralization stories out there right now, but it's 0% part of "The Decentralized Web".

Re: Principles of a Decentralized Web

#10

Am I missing a fundamental part of the article? There is almost no content here. This is less of a complaint about why this was upvoted as it is a question of why.

I agree, the article should probably expand on

- What "control" means specifically / what kinds of control a user should have

- What the difference is, in practice, between interoperability and portability

- What is the scope of the project?

Post reply on HN