WikipediaP2P(wikipediap2p.org)
wikipediap2p.org
WikipediaP2P
https://www.wikipediap2p.org/
27 comments
This doesn't answer your question, but it says it's based on CacheP2P, which itself says (http://www.cachep2p.com/api.html) it's 99.99% WebTorrent (https://webtorrent.io/).
It doesn't look like WebTorrent is meant to deal with content that is continually changing, and I wasn't able to determine (after about 30 seconds of looking) how either of the two layers on top address that
It doesn't look like WebTorrent is meant to deal with content that is continually changing, and I wasn't able to determine (after about 30 seconds of looking) how either of the two layers on top address that
Thanks for actually looking into the mentioned problems instead of going on a tangent about climate change ;)
CacheP2P seems to solve the problem by including a list of sha1 hashes for all files that are distributed through P2P.
Speculation time:
I guess distributing the sha1 hashes for every wikipedia page is a bit too much (especially considering they are always changing). So with every page, you would only distribute the hash for those sites that are directly linked from it.
If you provide the correct sha1 hash for every linked website (which in turn includes the hashes of all linked websites from it...), you would form some kind of merkle-tree of wikipedia pages. Except that the graph of wikipedia pages is certainly highly cyclic (thus no tree), so this isn't feasible. And all the pages change all the time. So this naive approach has already two strikes against it and does certainly not work.
I will try to have a look at the source code at some later point, I guess.
CacheP2P seems to solve the problem by including a list of sha1 hashes for all files that are distributed through P2P.
Speculation time:
I guess distributing the sha1 hashes for every wikipedia page is a bit too much (especially considering they are always changing). So with every page, you would only distribute the hash for those sites that are directly linked from it.
If you provide the correct sha1 hash for every linked website (which in turn includes the hashes of all linked websites from it...), you would form some kind of merkle-tree of wikipedia pages. Except that the graph of wikipedia pages is certainly highly cyclic (thus no tree), so this isn't feasible. And all the pages change all the time. So this naive approach has already two strikes against it and does certainly not work.
I will try to have a look at the source code at some later point, I guess.
Edit: 2.5 Mb was wrong, shame on me -_-
5 Million articles, 512b per Hash, if that's enough, gives 2.5 Gb. Updates can be much smaller. Multiply that by 10 for hashes of the nearest users, who have a copy, and that's still manageable. Just of the top of my head.
edit: inb4 a blockchained approach.
5 Million articles, 512b per Hash, if that's enough, gives 2.5 Gb. Updates can be much smaller. Multiply that by 10 for hashes of the nearest users, who have a copy, and that's still manageable. Just of the top of my head.
edit: inb4 a blockchained approach.
It's 320 MB.
5 million articles times 64 bytes per hash (512 bits) divided by 1e6 bytes per MB is 320.
5 million articles times 64 bytes per hash (512 bits) divided by 1e6 bytes per MB is 320.
Ok, that's not too unreasonable (especially if you need to download an extension anyways). If you make delta updates available for changed pages, this should actually be reasonably small once you have done the initial download.
> controversial topics like [..] Climate Change
You're making me sad on a Friday afternoon.
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.
I guess that's better :)
To expand a bit on my previous comment, the sad part is that even though we know that the topic is not really controversial scientifically, we somehow, subconsciously, refer to it as one.
Elections and all that.
To expand a bit on my previous comment, the sad part is that even though we know that the topic is not really controversial scientifically, we somehow, subconsciously, refer to it as one.
Elections and all that.
Even accepting the science, there is plenty of room for controversy over what actions should be taken as a result.
Yea the true controversy isn't weather the climate is changing but rather the rate at which it is occurring and the degree to which humans should intervene to take corrective action.
And amongst the options of ways to intervene which ones to choose? Some of which are probably mutually exclusive.
All something needs to be controversial is for there to be a great deal of public disagreement about it. Climate change definitely qualifies. Unfortunately, this has just about nothing to do with factual basis, evidence, etc.
> Let's reformulate it then: topics where some actors have a strong incentive (monetary or emotional) to manipulate other peoples opinion.
So North Korea doesn't exist right? :D
So North Korea doesn't exist right? :D
You know how I know you're in Europe? Because the idea that it's controversial in the US hasn't already numbed you.
And that it's still morning here on the east coast :)
And that it's still morning here on the east coast :)
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.
For every person who thinks global warming isn't real (for some reason), there's someone who thinks we're all going to get killed by a giant global warming-induced tsunami like in that awful movie. Climate change is controversial, because people are making many claims without sufficient evidence (e.g. completely trusting some set of our current predictive models) or using it as a justification for political ends (like subsidizing electric cars).
"people are making many claims without sufficient evidence (e.g. completely trusting some set of our current predictive models)"
Do you believe climate change is a problem and should be addressed but see others making claims beyond what the evidence supports? Or do you think climate change isn't an issue? If the former, what in particular are you thinking of? If the latter, what would it take to convince you that it's an issue?
Do you believe climate change is a problem and should be addressed but see others making claims beyond what the evidence supports? Or do you think climate change isn't an issue? If the former, what in particular are you thinking of? If the latter, what would it take to convince you that it's an issue?
[deleted]
This is an honest question. If you think the questions are unfair, or off base, or phrased poorly, I'd appreciate a comment.
Absolutely correct!! You can't call 'Climate Change' a controversy now that we all are facing the consequences already!!
My coworker doesn't "believe" in global warming, but i have some sympathy on the lack of belief.
I know that for most topics i make uninformed decisions based on the information created/curated by intelligent people. Eg, global warming, vaccinations, etcetc. Sure, some of it may seem obvious, but lets be honest - i have no clue about what a vaccination does in the body, nor how climate change works. They're not school-yard topics, i'm a moron when it comes to them.
So, i play the numbers and base my understanding on a large consensus of educated people. As with the case of climate change. My coworker believes roughly the same, but unfortunately he chooses to believe "scientists who revoke climate change". He has some weird things to say, but ultimately he is doing the same thing as me.
The only thing that bothers me on this subject, is we both believe in green energy, reducing pollution, and etcetc. We have basically the same opinions on what we should be doing for the environment (reducing pollution/etc) and how important it is. Yet, he still believes it is a hoax. That part i don't understand.
Why would climate change be a hoax? Who is making money off of a "climate change hoax"? I don't get that part.. hell, part of the problem with green energy was that it didn't exist because no one was making money off it.
Anyway, /rant. All i mean to say is that people on other sides of the fence likely aren't all that different than you.. well, unless you're a researcher in the field of climate change, of course.
I know that for most topics i make uninformed decisions based on the information created/curated by intelligent people. Eg, global warming, vaccinations, etcetc. Sure, some of it may seem obvious, but lets be honest - i have no clue about what a vaccination does in the body, nor how climate change works. They're not school-yard topics, i'm a moron when it comes to them.
So, i play the numbers and base my understanding on a large consensus of educated people. As with the case of climate change. My coworker believes roughly the same, but unfortunately he chooses to believe "scientists who revoke climate change". He has some weird things to say, but ultimately he is doing the same thing as me.
The only thing that bothers me on this subject, is we both believe in green energy, reducing pollution, and etcetc. We have basically the same opinions on what we should be doing for the environment (reducing pollution/etc) and how important it is. Yet, he still believes it is a hoax. That part i don't understand.
Why would climate change be a hoax? Who is making money off of a "climate change hoax"? I don't get that part.. hell, part of the problem with green energy was that it didn't exist because no one was making money off it.
Anyway, /rant. All i mean to say is that people on other sides of the fence likely aren't all that different than you.. well, unless you're a researcher in the field of climate change, of course.
It's often easier to convince someone that something's not a big deal than to convince them that people will solve it without government intervention.
> Why would climate change be a hoax? Who is making money off of a "climate change hoax"?
The entire "Cap and Trade" market?
The entire "Cap and Trade" market?
Views don't have to be binary like "it's a hoax" or "the end is near". In between those 2 you have stuff like:
- World may be warming but I don't believe we should act yet
- World may be warming but I don't believe the actions we are taking make a difference
- World is warming but I don't believe we know whether the result will be necessary a "bad thing"
- World is warming but I don't believe we know the main cause
- World is warming but I don't care what happens in 100 years
- World is warming but I feel we should wait longer to see if models are correct before spending money on it
- I feel humans overestimate their ability to model the future
- I feel there are bigger problems we should be tackling..
Problem is while those reasons may help people sleep at night, none resemble a logical chain of reasoning. Seems more like a list justifications for apathy in spite of opposing evidence bc trying is politically untenable and denying science is easier.
A complete logic must take into account individual preferences, not merely species survival.
The opportunity costs towards an individual to willingly shift and adapt to climate change is fairly high -- until Pigovian taxes or some such are implemented the adoption rate will be small for prevention. We're likely in the stage now where policies around adaption need to be crafted and planned.
The opportunity costs towards an individual to willingly shift and adapt to climate change is fairly high -- until Pigovian taxes or some such are implemented the adoption rate will be small for prevention. We're likely in the stage now where policies around adaption need to be crafted and planned.
Still though, in order to get people to willingly go along with restrictive environmental regulation you have to address those arguments. From a business owners perspective, the only thing they hear when discussing environmental regulation is increased production costs. You have to combat their skepticism with undeniable proof which I think has yet to be presented.
>> part of the problem with green energy was that it didn't exist because no one was making money off it
Government subsidies and mandates can help that. If global warming is a problem and we circumvent the market to funnel money to green energy, a hoax could also circumvent the market to funnel money to green energy.
Government subsidies and mandates can help that. If global warming is a problem and we circumvent the market to funnel money to green energy, a hoax could also circumvent the market to funnel money to green energy.
A strong incentive to believe it to be a hoax, probably kicking in all kinds of biases, is simply how scary it would be to believe it is true.
> Why would climate change be a hoax? Who is making money off of a "climate change hoax"?
This is one thing I really don't understand as well. Ok, there's X amount of proof in favor of AGW. Where's the evidence for your claims it's all an elaborate, international hoax? Where's the money?
I've never gotten a good answer. Usually just deflections to how "the Earth always fluctuates" and other dismissive claims that have already been answered a thousand times had they bothered to actually research it.
It's witnessing confirmation bias.
This is one thing I really don't understand as well. Ok, there's X amount of proof in favor of AGW. Where's the evidence for your claims it's all an elaborate, international hoax? Where's the money?
I've never gotten a good answer. Usually just deflections to how "the Earth always fluctuates" and other dismissive claims that have already been answered a thousand times had they bothered to actually research it.
It's witnessing confirmation bias.
I do not believe it's a hoax, but a lot of disciplines develop unintentional publication biases, so that sensational or apocalyptic findings are probably easier to publish.
Again, I don't think that's what's going on, but I know a lot of people who question or dismiss the median conclusions in other scientific disciplines, like economics, because of some perception of systemic bias.
Myself, I might discount health studies, but maybe I'm biased by the ones that the media chooses to report, which seem to be mostly contradictory nonsense about how chocolate and wine will make you live forever.
This is just a conjecture. If I'm right, I'm not sure if that's supposed to make you feel better (because your opponents are more rational than you thought) or worse (because complex epistemology is not likely a topic you can discuss with 60% of people).
Again, I don't think that's what's going on, but I know a lot of people who question or dismiss the median conclusions in other scientific disciplines, like economics, because of some perception of systemic bias.
Myself, I might discount health studies, but maybe I'm biased by the ones that the media chooses to report, which seem to be mostly contradictory nonsense about how chocolate and wine will make you live forever.
This is just a conjecture. If I'm right, I'm not sure if that's supposed to make you feel better (because your opponents are more rational than you thought) or worse (because complex epistemology is not likely a topic you can discuss with 60% of people).
Me too!
- Github link fixed.
- Ideally Wikipedia could add just a signature in the page metadata and the extension could check it against it's public key.
- CacheP2P has one solution implemented (checksums of links contents defined in the metadata of each page), but would require Wikipedia to enable it.
Hi, thanks for replying. I think the idea of a distributedly mirrored wikipedia is great, so thanks for this project (even if some users seem to encounter high cpu load using it).
So, do I understand correctly that each page (that has been distributed through WP2P) includes the hashes for all the linked pages? But I assume these hashes are only for the content, not the metadata of the linked pages. So a malicious actor could still inject a bad page (that includes bad hashes for linked pages) if he wanted.
It is true that signed wikipedia pages would be a really neat idea, since it would enable this as well as other distributed projects to make sure they are displaying the "real" version of the site.
So, do I understand correctly that each page (that has been distributed through WP2P) includes the hashes for all the linked pages? But I assume these hashes are only for the content, not the metadata of the linked pages. So a malicious actor could still inject a bad page (that includes bad hashes for linked pages) if he wanted.
It is true that signed wikipedia pages would be a really neat idea, since it would enable this as well as other distributed projects to make sure they are displaying the "real" version of the site.
A better way to support Wikipedia would be to donate. $10 probably covers more than the strain you put on Wikipedia for a year.
https://donate.wikimedia.org/
https://donate.wikimedia.org/
I encourage a repeating donation. If you work a tech job you can very likely afford 5/month. The site has changed my life for the better and I constantly find myself on there satisfying whatever is piquing my curiosity at the moment. To be clear, I'm not affiliated in any way just a huge supporter.
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
[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?
Is this a sign that WebRTC isn't optimised yet, or is it the extension itself that needs some love?
Yup, nice concept but pushing my high end I5 to 100% usage on a first page load and getting chrome to freeze is not a viable extension for me.
We'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).
Right now Wikipedia/Wikidata is only really useful as a stress test for IPFS, but I'm optimistic for the future.
For anyone interested in this there is some (slow) progress on this at https://github.com/ipfs-wikidata , though it's admittedly a low priority for me right now, as I wait for the technical state of IPFS to improve.
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).
Right now Wikipedia/Wikidata is only really useful as a stress test for IPFS, but I'm optimistic for the future.
For anyone interested in this there is some (slow) progress on this at https://github.com/ipfs-wikidata , though it's admittedly a low priority for me right now, as I wait for the technical state of IPFS to improve.
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
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
Yeah, it was most certainly the millions of tiny files that were killing the performance, since every publish with IPFS has quite some overhead.
I'm quite excited for directory sharding since it would make the project simpler, but the local filesystem on my server doesn't even seem to be able to handle all the files in a single directory.
I'm quite excited for directory sharding since it would make the project simpler, but the local filesystem on my server doesn't even seem to be able to handle all the files in a single directory.
If it's execution is similar to this project where hosting a page on your system is effortless (or at most a one-click affair), then it's definitely something I can get behind.
You'll get the benefit of insuring off-line availability as well as only hosting pages you care about. Win-win.
You'll get the benefit of insuring off-line availability as well as only hosting pages you care about. Win-win.
This could be a useful application to run on IPFS, which IMO needs a killer app to become widespread.
The problem is that it requires installing third-party software to function (the IPFS client) or putting load on some IPFS gateway.
Not necessary. Either Wikipedia can help out with hosting their own gateways in addition to the ones running on ipfs.io, OR they can include a js-ipfs node in the browser.
>Wikipedia can help out with hosting their own gateways
Which kinda defeats the point of saving bandwidth on their side.
>js-ipfs node
That could work, though I was under the impressino that the js-ipfs implementation was WIP/Experimental (last I checked)
Which kinda defeats the point of saving bandwidth on their side.
>js-ipfs node
That could work, though I was under the impressino that the js-ipfs implementation was WIP/Experimental (last I checked)
> Which kinda defeats the point of saving bandwidth on their side.
Traffic doesn't only need to be served by Wikipedia but could also include other volunteers (think archive.org and others) and the setup for helping out would be easy.
> That could work, though I was under the impressino that the js-ipfs implementation was WIP/Experimental (last I checked)
That is absolutely true, which WikipediaP2P is as well, and IPFS for that matter. I was simply pointing out some ways you can make the whole "Wikipedia on IPFS" thing to work in the future.
Traffic doesn't only need to be served by Wikipedia but could also include other volunteers (think archive.org and others) and the setup for helping out would be easy.
> That could work, though I was under the impressino that the js-ipfs implementation was WIP/Experimental (last I checked)
That is absolutely true, which WikipediaP2P is as well, and IPFS for that matter. I was simply pointing out some ways you can make the whole "Wikipedia on IPFS" thing to work in the future.
The original idea requires a 3rd party addon and Chrome. How is this different?
Wikipedia on IPFS as an addon would also require operating a node to fulfill the goal of the original project, namely to save bandwidth for Wikipedia.
Simply pointing it at gateway.ipfs.io would achieve nothing but shift the problem around.
Simply pointing it at gateway.ipfs.io would achieve nothing but shift the problem around.
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 ipfs.io server in that case? Or is it still distributed/torrent-like?
Or am I understanding IPFS or the ipfs.io gateway wrong? Does everything go through the ipfs.io server in that case? Or is it still distributed/torrent-like?
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.
https://github.com/ipfs/js-ipfs
https://github.com/ipfs/js-ipfs
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.
IMO the presented solution is a bit better since it only relies on WebRTC to establish P2P, no extra software required.
Here's the cacheP2P discussion :
https://news.ycombinator.com/item?id=12752168
https://news.ycombinator.com/item?id=12752168
I 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 papers, maps and recipes, which anybody with a computer could contribute drive space to storing.
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 papers, maps and recipes, which anybody with a computer could contribute drive space to storing.
I agree with your last statement, and think this is a great proof-of-concept for distributed networking.
I worry, though, that this space is fracturing in a way that's hampering adoption. Between Freenet, Zeronet, IFPS, I2P, not to mention things like Retroshare, Matrix, and so forth, there's a lot of redundancy but with important differences between any given two solutions. I'm not sure what can be done about it, but it seems like something in this area needs a network effect to accelerate adoption, but to do that, it needs to be comprehensive in what it offers while also being sufficiently differentiable from other projects. It's great to see so much going on in this area, but it's getting difficult to know what does what, and where one might put some resources.
I worry, though, that this space is fracturing in a way that's hampering adoption. Between Freenet, Zeronet, IFPS, I2P, not to mention things like Retroshare, Matrix, and so forth, there's a lot of redundancy but with important differences between any given two solutions. I'm not sure what can be done about it, but it seems like something in this area needs a network effect to accelerate adoption, but to do that, it needs to be comprehensive in what it offers while also being sufficiently differentiable from other projects. It's great to see so much going on in this area, but it's getting difficult to know what does what, and where one might put some resources.
The database dumps are surprisingly small - can store the whole thing on 2 TB hard drive incl media - or 64GB SD card if you just want the SQL database with text and metadata
If you factor in the overhead of p2p, it is probably cheaper, if operating systems come with a few hundred MB of the more popular Wikipedia pages.
There's a BEP (46 iirc) proposed for that :)
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!
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!
Also, a separate domain, wikipediap2p.org, not (obviously) affiliated with wikipedia.org. If it were p2p.wikipedia.org, it would be fine for me.
It says on the page: "This is an unofficial extension and not endorsed by Wikipedia in any way, it's just an implementation of latest web-technologies towards sharing of knowelege."
I think changing the links to point to the cache instead of the original server needs that permission.
There is no way I'm installing this with those permissions requests. All data on all websites I visit? No way.
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.
how does it handle cache invalidation, eg when a page gets updated?
Hmmm, maybe thats the option for saving twitter?
Check out mastodon.social :)
Look nice, but problem with social network services is usually all about number of users :)
Remember diaspora?
Remember diaspora?
GDI, I just flipfloped to Firefox... I guess no P2P goodness until Firefox supports Chrome addons or the addon gets ported...
Try https://addons.mozilla.org/fr/firefox/addon/chrome-store-fox... (not guaranteed to work, I didn't test it)
Thanks!
Firefox supports Webextension addons in all current channels.
How can I download it then? The button just throws a javascript error, and with javascript disabled it's a dead thing. Going to the chrome web thingy store it only tries to get me to download google chrome.
I tested it in Chromium really quick. I have one small remark: when opening an article obtained by a peer (a green link) in a new tab, it just opens it in the same tab.
So if I wanted to donate my computing resources and bandwidth to hosting this, should I just install the plugin and leave chrome running on my "server"?
This seems to be introducing synchronisation issues or something. I've just made an edit on an article, when I go back to it I see the edited version only if I manually refresh the page.
Slightly related, there's Wikiwand: https://www.wikiwand.com/
fixing a typo on the main page would help improve its apparent legitimacy.
>""This is an unofficial extension and not endorsed by Wikipedia in any way, it's just an implementation of latest web-technologies towards sharing of knowelege."" <---knowledge
>""This is an unofficial extension and not endorsed by Wikipedia in any way, it's just an implementation of latest web-technologies towards sharing of knowelege."" <---knowledge
The guild of censors disapproves..
No Firefox support?
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'.
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'.
I'm assuming non-native writer rather than sloppiness per se.
I'd considered that. That would explain the second, but the first has to be sloppiness. If nothing else, if you want to produce english content, set your spellchecker to english.
I think the first one is meant to be "reaching"?
Both fixed, was my bad, if you see any other please tell me. Indeed non-native over here.
I agree. By the way, you typo'd "things" as "thinks".
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.
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.
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/
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.
Come to think of it, it is interesting that they server all this traffic using Varnish + HHVM/3.3.0.
[deleted]
Stop using my internet connection without my consent!
How is a browser extension you explicitly have to install, from a page that explains what it does, "using your internet connection without consent"?
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 imagine the first one could maybe be somehow guaranteed through the protocol. Maybe you can just solve the second by invalidating your local copy after it is more than one day old.
The github link on the homepage does sadly not work for me (firefox on linux), so I can't check.