I wonder if this concept could be extended to site aggregator such as HN or Reddit? The amount of bandwidth saved could be significant.
I don't think it would work all that well with content that changes so often.
WikipediaP2P
51–60 of 117 posts
Re: WikipediaP2P
#52I feel like I should contribute more than a pun, but this is a missed opportunity for wikip2pedia.org. The domain is available.
thats gold rfrank, gold
Re: WikipediaP2P
#53I've been wondering, would one reach the same principle if one would pin the root folder of wikipedia on their own server using IPFS and then if wikipedia would point their domainname to the ipfs.io gateway with a hash for that folder, would Wikipedia auto update on my server and would IPFS provide the load balancing/p2p part? Or am I understanding IPFS or the ipfs.io gateway wrong? Does everything go through the ipf…
For Wikipedia it would probably be more useful to embed js-ipfs [0] into pages, and fetch additional pages and assets after first one from ipfs. js-ipfs can currently speak WebRTC to peer with other js-ipfs nodes, and websockets to peer with go-ipfs nodes.
Re: WikipediaP2P
#54We'd be better off by putting wikipedia on IPFS and IPFS into p2p cache.
I agree, but sadly IPFS still needs some optimization for that to be feasible. I published the whole Wikidata dataset as separately accessible entities to IPFS and the initial publishing took ~2 weeks. Theoretically updating the dataset with weekly changes should be pretty fast after that, but if there is a change that impacts the JSON structure of every entity you have to start all over (which recently happened). Ri…
Performance of adding to IPFS has improved in the past months, I recently added 3.7 TB of https://cdn.media.ccc.de and it took ~24h, admittedly these files are each pretty big, while Wikidata sounds like tons of tiny files.
One more major improvement is on the way, which is directory sharding using a HAMT data structure: https://github.com/ipfs/go-ipfs/pull/3042
Re: WikipediaP2P
#55I understand that this is an early implementation. Nevertheless, I have a question: how does it make sure the site you receive is actually the a) correct one (someone could distribute incorrect pages e.g. about controversial topics like North Korea or Climate Change; or inject some malicious code that e.g. uses your account to submit changes to wikipedia) b) most recent one (or at least a reasonably new one). I imagi…
> controversial topics like [..] Climate Change
You're making me sad on a Friday afternoon.
Re: WikipediaP2P
#56I understand that this is an early implementation. Nevertheless, I have a question: how does it make sure the site you receive is actually the a) correct one (someone could distribute incorrect pages e.g. about controversial topics like North Korea or Climate Change; or inject some malicious code that e.g. uses your account to submit changes to wikipedia) b) most recent one (or at least a reasonably new one). I imagi…
> controversial topics like [..] Climate Change You're making me sad on a Friday afternoon.
Let's reformulate it then: topics where some actors have a strong incentive (monetary or emotional) to manipulate other peoples opinion.
Re: WikipediaP2P
#57I understand that this is an early implementation. Nevertheless, I have a question: how does it make sure the site you receive is actually the a) correct one (someone could distribute incorrect pages e.g. about controversial topics like North Korea or Climate Change; or inject some malicious code that e.g. uses your account to submit changes to wikipedia) b) most recent one (or at least a reasonably new one). I imagi…
> controversial topics like [..] Climate Change You're making me sad on a Friday afternoon.
I guess he phrased it wrongly. Climate issues is not a matter of controversy but rather there are organizations trying to spread false knowledge and being able to spread that using wikipediaP2P is what OP is concerned about.
Re: WikipediaP2P
#58Re: WikipediaP2P
#59I remember thinking about a similar concept a few years back. It would be good to have a p2p archive of human knowledge for end of the world scenarios. The problem is Bittorrent isn't the protocol for it, it doesn't allow incremental changes. You also don't want the complete history like git, you want something that passes a diff around. It would be great to have a p2p network with Wikipedia, a load of academic paper…
There's a BEP (46 iirc) proposed for that :)