WikipediaP2P • Hacker News Board

Re: WikipediaP2P

#111

Post by oceanofsolaris » Fri, Nov 18, 2016, 11:37 PM UTC

gcr wrote: post #108

posterboy wrote: post #107

Earlier quoted context omitted.

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.

It's 320 MB. 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.

Re: WikipediaP2P

#112

Post by fiatjaf » Sat, Nov 19, 2016, 1:06 AM UTC

striking wrote: post #82

fiatjaf wrote: post #60

Earlier quoted context omitted.

Not this, but cachep2p, which works in normal webpages.

You consent to it by visiting the site. If you're so incensed, block the cachep2p js file with your "hosts" file or extensions.

You don't know what you're saying.

Re: WikipediaP2P

#113

Post by BrianMickeyD » Sat, Nov 19, 2016, 8:56 AM UTC

osense wrote: post #55

oceanofsolaris wrote: post #48

I 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.

Me too!

Re: WikipediaP2P

#114

Post by exadeci » Sat, Nov 19, 2016, 8:54 PM UTC

qznc wrote: post #19

gield wrote: 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.

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.

Re: WikipediaP2P

#115

Post by exadeci » Sat, Nov 19, 2016, 8:55 PM UTC

agumonkey wrote: post #90

janus24 wrote: post #13

Earlier quoted context omitted.

Doesn't seems to work for me, all links are orange.

Mine are all blue. But I run Canary so I don't have to complain.

It's on mouseover that they change

Re: WikipediaP2P

#116

Post by iansowinski » Sun, Nov 20, 2016, 11:47 AM UTC

fermuch wrote: post #46

iansowinski wrote: post #2

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?

Re: WikipediaP2P

#117

Post by oceanofsolaris » Mon, Nov 21, 2016, 1:12 PM UTC

guerrerocarlos wrote: post #95

oceanofsolaris wrote: post #48

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

- 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.