@blademccool I did not say it is the responsibility of Brave. What I said was peer distribution models of data that are persistent forever (IPFS can b...

@blademccool Identifying who put the data up is not what "canonical origin" means. Canonical origin means being able to locate the *network* origin of...

@atmchuck Hole punching (or more generally, NAT traversal) is indeed one of about a dozen problems that have to be solved. Most techniques (as the doc...

An addendum: Kumar and I spent a bit of time writing out a (generally ignored) post where we responded point-by-point to Larry Sanger's original ess...

@atmchuck Hello! IPFS and OPSS is sort of an apples-to-mammals comparison. IPFS is a distributed file system and for what it is seems to have a nice...

@whatusername Brave is a pretty good browser already from what I hear. I haven't used it myself but I'll probably give it a try soon. Really, for most...

@whatusername Yes. It is certainly a step in the right direction, it just isn't anywhere near enough to base a distributed application on.

@tuupola Correct. This does not mean that end-users fully understand the situation, though.

The most interesting use of this would be to use it as a CDN for static content to reduce load on webservers. There are two problems with this, thou...

@admin They have added an IPFS client into the browser, so you can browse static files that are stored on IPFS as well as normal HTTP URLs. You can:...

@whatusername Any node in a web of trust can selectively lie.

@whatusername You are again discussing mere data verification. That is already a solved problem. I'm talking about validation of behavior because ap...

@whatusername Those mechanisms check only the integrity of the data. A hash achieves that: make the address of a resource its hash and it's done. A si...

Bingo! Good job integrating it all into a single document. Nice.

@whatusername What makes you trust the "server" nodes?