Re:Decentralized Web Primer
by hossbeast on Saturday December 09, 2017 @05:20PM
(#15888494)
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.
[ Parent
| on HN ]
The next step after DAGs is CRDTs.
They have a research page on this: https://github.com/ipfs/research-CRDT
One of them is us (https://github.com/amark/gun), David reached out the other week, now we're trying to find time to discuss with Juan how to best integrate.
That's exciting that Gun is looking up adopt CRDT. Is that what you are saying? A real open source competitor to Google Firebase.
Thanks! GUN is already a CRDT (it is a generalizable CRDT on graphs), which is why IPFS is chatting with us. Our CRDT has an emergent property of composability though, which lets other specialized CRDTs be implemented on top in just a few lines of code (take this example, of a counter CRDT: https://github.com/amark/gun/wiki/snippets-(v0.3.x)#counter ).
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
by domainkiller on Saturday December 09, 2017 @05:30PM
(#15888537)
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