Live data from Hacker News

WikipediaP2P

wikipediap2p.org

21–30 of 117 posts

Re: WikipediaP2P

#21
Why the “Read and change all your data on the websites you visit” permission?

Also, the “Fork me on GitHub” banner on your website is behind the fancy canvas so we can’t actually click it (Chrome 54).

Great idea otherwise!

Re: WikipediaP2P

#22
This seems like a decent project that has the potential to become very popular. I just tested it and it worked well; however, it clogged my CPU and the extension crushed in the end.

Re: WikipediaP2P

#23
post #19
post #7

For the sake of testing it, I have opened nearly every link in the introduction of the Nikolas Tesla [0] page, the one used in the example. It should now be possible to at least obtain all those articles through me, and hopefully also through other people. [0] https://en.wikipedia.org/wiki/Nikola_Tesla

It burns CPU like crazy for me. Would not use it on battery.

> WikipediaP2P uses WebRTC for all Peer to Peer communication.

Is this a sign that WebRTC isn't optimised yet, or is it the extension itself that needs some love?

Re: WikipediaP2P

#25
post #12
post #3

wouldn't cloudflare be more effective?

Could you see any reasons why people want to explore alternative options to Cloudflare?

I can see that not everyone likes Cloudflare, but generally a CDN that allows cheap delivery of the bandwidth heavy parts (e.g. images and scripts) makes probably more sense in reality than P2P.

While the P2P idea is very nice, most residential lines are heavily geared towards download speed. Upload speed is often only 5-10% of the overall speed. Using a P2P network outside of your Lan will probably lead to a slower experience than using a CDN that has PoPs very close to you.

Now I'm pretty sure that Cloudflare would save Wikipedia at least 95% of bandwidth with the free tiers. And I don't think that Cloudflare would complain, the gain of having them as clients would be larger than the costs for bandwidth. Similar for other providers, Wikipedia and their traffic levels would probably get very cheap offers.

But I can also understand that it would somehow question the independence of Wikipedia from corporate interests. That's why they didn't do it.

Re: WikipediaP2P

#26
post #21

Why the “Read and change all your data on the websites you visit” permission? Also, the “Fork me on GitHub” banner on your website is behind the fancy canvas so we can’t actually click it (Chrome 54). Great idea otherwise!

I think changing the links to point to the cache instead of the original server needs that permission.

Re: WikipediaP2P

#27
GDI, I just flipfloped to Firefox... I guess no P2P goodness until Firefox supports Chrome addons or the addon gets ported...

Re: WikipediaP2P

#28
post #10

I'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…

If you want to do IPFS, you need to run IPFS locally to make it work, otherwise you're just redistributing bandwidth to the ipfs.io gateway.

IMO the presented solution is a bit better since it only relies on WebRTC to establish P2P, no extra software required.

Re: WikipediaP2P

#29
post #5

Earlier quoted context omitted.

Cloudflare is not free

Yes, it actually is, I use it for a simple website I use. It actually decreases the load on it. But, you lack a lot of features and you can increase it. It cost like $20 or more per month up into $100 per month it depends I think. But, they probably don't want to go this route. https://www.cloudflare.com/plans/

I'm sure CloudFlare's free plan doesn't target websites with the amount of traffic wikipedia has.

Come to think of it, it is interesting that they server all this traffic using Varnish + HHVM/3.3.0.

Re: WikipediaP2P

#30
Is it just me that gets put off by typos and other errors on a homepage? I feel like putting a little effort in to checking for obvious errors isn't too much to ask, but I may well be being overly snobby about such things, I'm curious.

The two examples here are:

> This color means it's rearching for that article.

I assume that's meant to be 'searching'

And: > This is an unofficial extension and not entitled by Wikipedia in any way

I'm assuming 'entitled' is meant to be 'endorsed'.

Post reply on HN