Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Neocities is implementing IPFS – distributed, permanent web

ipfs.io

Post reply on HN
Print view View original

31–40 of 249 posts

Re: Neocities is implementing IPFS – distributed, permanent web

#31

Post by [deleted] »

radlad wrote: post #16
jeswin wrote: post #13

Earlier quoted context omitted.

> So is this primarily for static websites? More work would be needed here perhaps. But decentralized apps should happen one day. As someone without real technical knowledge in security and decentralized platforms, I'd love to hear from some on HN where we really stand on decentralized apps and security. - Public data. Distributing, searching and querying is not a problem. - Restricted data. You'd be distributing enc…

> Now, if we have a way to send an encrypted query to the peer and have it run on encrypted data without the peer being able to understand the query or the data, we'd be set perhaps. Is that possible? It doesn't seem to be "N versus NP" but it seems similar. How can a computer find a correct answer to a question it doesn't know? I suppose you could send off small units of processing across many nodes, such that none…

[deleted]

Re: Neocities is implementing IPFS – distributed, permanent web

#32

Post by gtrubetskoy »

hardwaresofton wrote: post #29
gtrubetskoy wrote: post #23

My first thought is how does it handle SHA hash collisions? Googling for it took me back to HN: https://news.ycombinator.com/item?id=9322489 AFAICT it's not yet resolved.

In the (relatively rare) case of a SHA hash collision, couldn't you try and resolve a collision by using (the results) of other hashing functions? While two things may produce the same SHA hash, they may differ with other hashing functions.

It will reduce the probability of a collision at the expense of the address being longer - because now you need to carry around hash1 + hash2. But still it doesn't eliminate the possibility, only makes it less likely.

Re: Neocities is implementing IPFS – distributed, permanent web

#33

Post by titfn »

hardwaresofton wrote: post #29
gtrubetskoy wrote: post #23

My first thought is how does it handle SHA hash collisions? Googling for it took me back to HN: https://news.ycombinator.com/item?id=9322489 AFAICT it's not yet resolved.

In the (relatively rare) case of a SHA hash collision, couldn't you try and resolve a collision by using (the results) of other hashing functions? While two things may produce the same SHA hash, they may differ with other hashing functions.

instead of calculating multiple hashes every time, might as well use a better hash?

Re: Neocities is implementing IPFS – distributed, permanent web

#34

Post by TheDong »

hardwaresofton wrote: post #29
gtrubetskoy wrote: post #23

My first thought is how does it handle SHA hash collisions? Googling for it took me back to HN: https://news.ycombinator.com/item?id=9322489 AFAICT it's not yet resolved.

In the (relatively rare) case of a SHA hash collision, couldn't you try and resolve a collision by using (the results) of other hashing functions? While two things may produce the same SHA hash, they may differ with other hashing functions.

All you're doing then is fiddling with probabilities. You can do that just as well by changing the length of the sha unless you have a reason to think sha is broken.

However, the probability of a hash collision is already incredibly low. As a demonstration of this, here's a list of a tiny subset of bitcoin private keys: http://directory.io/

The human mind just isn't capable of understanding how large of a number the number of sha hashes is.

Re: Neocities is implementing IPFS – distributed, permanent web

#35

Post by phodo »

This is great news. Dapps [1] are coming, and DHT [2] /storage technologies like IPFS (although IPFS is more than just a DHT) are the other much-needed side of the coin - no pun intended - to make that reality happen. Exciting times ahead. [1] decentralized app [2] distributed hash table

Re: Neocities is implementing IPFS – distributed, permanent web

#36

Post by viraptor »

mortenjorck wrote: post #5

Reading this felt kind of like the first time I read a writeup on Bitcoin. There's the same sense of throwing out some old, formerly immutable rules here, the excitement of something that's going to test some boundaries and inevitably clash with some authority (how can you, for instance, comply with the EU's "right to be forgotten" when that information is scattered into a redundant mesh?). Interesting times ahead fo…

Right to be forgotten however applies only to search engines right now, doesn't it? The articles the results used to point to still exist. So a redundant mesh itself doesn't seem to apply here.

Re: Neocities is implementing IPFS – distributed, permanent web

#37

Post by whyrusleeping »

gtrubetskoy wrote: post #23

My first thought is how does it handle SHA hash collisions? Googling for it took me back to HN: https://news.ycombinator.com/item?id=9322489 AFAICT it's not yet resolved.

ipfs currently uses what we call a 'multihash' where every hash value is tagged with the hash function used to generate it. As of now, the default hash function is sha256, and if I recall correctly, the chances of a world ending asteroid hitting earth and wiping out the planet is far more likely to occur than a collision. If sha256 is shown to be broken, we can change our default hash function to something like sha512 without breaking any existing data.

Re: Neocities is implementing IPFS – distributed, permanent web

#40

Post by HeyImAlex »

> Organizations like the NSA (and our future robot overlords) now only have to intercept our communications at a few sources to spy on us.

If you had the hash of some content, couldn't anyone find all of the ips currently serving it?

EDIT: Found this

https://github.com/ipfs/faq/issues/12

Post reply on HN