Live data from Hacker News

Decentralized Web Primer

gitbook.com

31–40 of 97 posts

Re: Decentralized Web Primer

#31

One thing I've never understood is how IPFS would serve dynamic content. Like imagine building amazon.com on IPFS how would that work? Every single page served would have Different hash, because the content is always changing.

It isn't supposed to do that. It isn't supposed to replace the entire internet nor even the entire web.

This "primer do the decentralized web" title is just bullshit.

Re: Decentralized Web Primer

#32
post #18

"The Decentralized Web" is the WWW system Tim Berners-Lee invented and that we're all using right now. It relies on the DNS and HTTP protocols. This new IPFS-based decentralized web is interesting but it's not even a measurable percentage of web traffic today. Far from being "The". What we need more than anything is to actually realize the beautiful dream TBL had for the WWW. HN is one great example but there should…

No. The web as it works right now is naturally centralised, for a simple reason: the bandwidth costs on a server is proportional to the size of its audience. This is why we need YouTube to begin with, instead of millions of people posting their videos on their personal page. There are other factors of course: firewalls, asymmetric bandwidth, security issues, technical ignorance… But the client-server model does play…

"use a P2P protocol instead".

Actually, just like "the cloud" is just someone else's computer, "P2P" is just someone else's server.

Re: Decentralized Web Primer

#33
post #2

Could be that I'm just really out of touch, but I need at least one paragraph saying "What is this?" (and ideally also, "Who is the target audience?" - or "Why would I be interested in reading this?")

[deleted]

Re: Decentralized Web Primer

#34

Earlier quoted context omitted.

Wouldn't a single-page-app connected to a remote datastore work?

Alright but all of the complexity, and all of the content served, is in the data store, and now what is IPFS even accomplishing?

What if the data store is built on IPFS as well? For instance, https://github.com/orbitdb/orbit-db

Re: Decentralized Web Primer

#36
post #32

Earlier quoted context omitted.

No. The web as it works right now is naturally centralised, for a simple reason: the bandwidth costs on a server is proportional to the size of its audience. This is why we need YouTube to begin with, instead of millions of people posting their videos on their personal page. There are other factors of course: firewalls, asymmetric bandwidth, security issues, technical ignorance… But the client-server model does play…

"use a P2P protocol instead". Actually, just like "the cloud" is just someone else's computer, "P2P" is just someone else's server.

P2P is not like the cloud. It's someone else's computer, but you don't know nor care what the exact machine you are connecting to because they are mostly untrusted.

Re: Decentralized Web Primer

#38

Unless your project needs censorship resistance, you can probably ignore this.

Well, my personal project as a voracious reader and critical thinker does needs censorship resistance on behalf of a diversity of authors who wish to publish their thinking.

Re: Decentralized Web Primer

#39
post #32

Earlier quoted context omitted.

No. The web as it works right now is naturally centralised, for a simple reason: the bandwidth costs on a server is proportional to the size of its audience. This is why we need YouTube to begin with, instead of millions of people posting their videos on their personal page. There are other factors of course: firewalls, asymmetric bandwidth, security issues, technical ignorance… But the client-server model does play…

"use a P2P protocol instead". Actually, just like "the cloud" is just someone else's computer, "P2P" is just someone else's server.

P2P is everyone else's server. Each peer pulls its own weight. This is different from relying on a single entity.

Re: Decentralized Web Primer

#40
post #3

How hard to censor is IPFS? It would be quite disappointing if we managed to switch everyone over to IPFS, and in the end, after all that effort (and the compromises we'd have to make compared to simply using centralized content), governments would remain quite effective at censoring IPFS content. Could ISPs throttle or block IPFS content, for instance? The developers should start assuming some extremely aggressive e…

From what I gathered by reading the whitepaper mass censorship is extremely hard to accomplish. > Could ISPs throttle or block IPFS content, for instance? They wouldn't know what was IPFS and what was regular encrypted TCP, the only way I can tell IPFS traffic apart in wireshark is the port number. Once ISPs start blockings random encrypted connections people will get mad when their games or other applications stop w…

> They wouldn't know what was IPFS and what was regular encrypted TCP

The extreme conclusion of state-sponsored censorship is not a black list or DPI. It is a white list. It is easy to restrict traffic to a small set of addresses that are rigorously monitored for any ability to proxy non-conforming traffic. Everything else would get dropped on the floor.

IPFS and the like sit too high in the OSI layers to combat state sponsored censorship in the long-run.

It makes me wonder what the target market is. If this ever got big, it would just trigger the next step in the arms race it is incapable of sustaining

Post reply on HN