Live data from Hacker News

ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

zeronet.io

31–40 of 171 posts

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#31

The project looks very promising but relies on running a lot of javascript from untraceable sources in the browser. Given the long history of vulnerabilities in the the browsers, trusting js from a well-known website might be OK, trusting js from zeronet is unreasonable. If ZeroNet could run with js code generated only by the local daemon or without js it would be brilliant.

Chrome added a feature a long while back I really wanted for ages. The ability to specify the checksum of a linked asset, so that it can be verified as it's downloaded (and untrusted/discarded if not). I just can't find the docs for it. :( My Google-fu is not strong.

EDIT:

Found it :D

https://w3c.github.io/webappsec-subresource-integrity/

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#32
post #29

> Page response time is not limited by your connection speed. Huh? What do they mean?

If you have previously visited a page then the response time will be limited by your computers ability to locate and open the correct html document.

If you haven't previously visited a page then the response time will be limited by how many peers are available and then by your connection speed.

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#33
post #31

The project looks very promising but relies on running a lot of javascript from untraceable sources in the browser. Given the long history of vulnerabilities in the the browsers, trusting js from a well-known website might be OK, trusting js from zeronet is unreasonable. If ZeroNet could run with js code generated only by the local daemon or without js it would be brilliant.

Chrome added a feature a long while back I really wanted for ages. The ability to specify the checksum of a linked asset, so that it can be verified as it's downloaded (and untrusted/discarded if not). I just can't find the docs for it. :( My Google-fu is not strong. EDIT: Found it :D https://w3c.github.io/webappsec-subresource-integrity/

It's called Subresource Integrity, see https://hacks.mozilla.org/2015/09/subresource-integrity-in-f... and https://www.w3.org/TR/SRI/

Browser support is noted here: http://caniuse.com/#feat=subresource-integrity

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#35
post #30
post #24

Earlier quoted context omitted.

> Neither argument has been tested, but the defense would that you were acting as an ISP with dumb pipes. Unlikely. To become a peer, you must first visit the website, fully downloading the content. Which makes an argument to you consenting to share the information.

Just like an ISP has to take your request and transmit it and the response. No difference in theory. In practice, I would worry whether courts would ignore theory.

But there is no person involved directly in the pipeline with an ISP. Every request goes through an automated process.

Governments do and have asked ISPs to update and block against certain websites. Thus, the automated system is expected to behave adequately.

However, as a person becomes involved, they become an active participant in the pipeline.

That is a huge theoretical difference.

A person is not automated, they have common reason, and intellect that goes beyond the rules that can be encoded in a dumb system.

This reasoning is what allows us to hold a person accountable to their actions.

If you visited a ZeroNet site, found it was bad stuff, immediately left and deleted the cache, you might have a case for innocence.

But if you immediately left, but continued to actively share the content... It's a different message.

You could become part of a child pornography ring, for example.

And courts enjoy making examples of distributors of such materials.

Pleading your innocence, becomes difficult at that point.

You've shared illegal content from your own property.

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#36
post #33
post #31

Earlier quoted context omitted.

Chrome added a feature a long while back I really wanted for ages. The ability to specify the checksum of a linked asset, so that it can be verified as it's downloaded (and untrusted/discarded if not). I just can't find the docs for it. :( My Google-fu is not strong. EDIT: Found it :D https://w3c.github.io/webappsec-subresource-integrity/

It's called Subresource Integrity, see https://hacks.mozilla.org/2015/09/subresource-integrity-in-f... and https://www.w3.org/TR/SRI/ Browser support is noted here: http://caniuse.com/#feat=subresource-integrity

It's kind of a shame they didn't let their imagination fly with that one... I wish integrity were a global attribute, because I could totally see using it for things like images and audio/video.

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#37

It would be great if a simpler webtorrent version was available just for fun.

There's a year-old project called peercloud that might scratch that itch:

* https://github.com/jhiesey/peercloud

* https://peercloud.io/

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#39

No comment about ZeroNet itself, but am I alone in the opinion that this website takes grid layout too far? It looks outright cluttered and overloaded.

Looks great on mobile however

Yeah, the advantage. Tables on steroids.

Re: ZeroNet – Uncensorable websites using Bitcoin crypto and BitTorrent network

#40
post #15
post #8

I always wondered why you couldn't just download a torrent of torrents for the month.

It would be interesting to create a distributed catalog of torrents itself.

if you substitute torrents with ipfs this is trivial:

    # create empty folder
    FOLDER=`ipfs object new unixfs-dir`
    # add folders to object
    FOLDER=`ipfs object patch "$FOLDER" add-link 2017-01 "$HASH_2017_01"`
    FOLDER=`ipfs object patch "$FOLDER" add-link 2017-02 "$HASH_2017_02"`
    FOLDER=`ipfs object patch "$FOLDER" add-link 2017-03 "$HASH_2017_03"`
    # print final hash
    echo $FOLDER
This would result in a hash that has the folders for January, February and March, which can have arbitrary nested folders and files in them.
Post reply on HN