796 karma · joined January 7, 2012
[ my public key: https://keybase.io/lgierth; my proof: https://keybase.io/lgierth/sigs/96UTewVcgE6mn2Hh1Tg3WCHUDRP_jWSFookoCcfruAg ]
I don't see why that'd not be allowed -- please do go ahead!
So what were you trying to say?
What I did find in that first link of yours [1] is this gem though:
> The IOTA hash function, Curl-P, was designed to allow for practical collisions. The IOTA protocol’s security depends solely upon the one-wayness of the function, not its collision resistance. The rationale behind the design of Curl-P is a much more complicated question which we explain in detail.
This statement is alarming on so many levels.
[1] https://blog.iota.org/official-iota-foundation-response-to-t...
// edit: oops, I see now that it's a multipart post, so I'll have a look there.
// edit: yeah okay, nothing of substance in the other parts either.
I don't know man, the MIT Digital Currency Initiative found a pretty bad one last August:
https://medium.com/@neha/cryptographic-vulnerabilities-in-io...
> the IOTA developers had written their own hash function, Curl, and it produced collisions (when different inputs hash to the same output). Once we developed our attack, we could find collisions using commodity hardware within just a few minutes, and forge signatures on IOTA payments. We informed the IOTA developers, they patched their system, and we wrote a vulnerability report
IPFS itself has never had any cryptocurrency integration, although there are external services that store your data on their IPFS nodes in exchange for Bitcoin.
(source: https://filecoin.io/blog/update-2017-q4/ and I'm on the IPFS team)
This is false. Where did you get that impression?
It has more detailed information about the dataset.
There's means for dynamic content too: IPNS and Pubsub, the latter was on HN just 3 days ago: https://news.ycombinator.com/item?id=15879752
> However, note that the official client comes with "blocklists" which may be used for censorship
There's no blocklists in any of the IPFS clients and libraries at the moment. However there are plans for opt-in, community-maintained blocklists that'll allow communities to govern what content they allow.
[1] Domain fronting lets you use a well-established web frontend for your web service. E.g. we could host /ws nodes in Google Cloud, and to the ISP the TLS handshake looks like it's for google.com, while inside the connection there's e.g. a `Host: libp2p.googlecloud.com` header. More info: https://www.bamsoftware.com/papers/fronting/
But then again, net neutrality is a political issue! You don't solve it for good with technology.
A shining example of pubsub in use is PeerPad, a collaborative text editor exchanging CRDTs over IPFS/Pubsub: https://peerpad.net
You're absolutely right here of course
edit: what I also meant to say is, a chat room doesn't need computation (although there certainly use cases that do)
This is one of the very points that IPFS tries to address: decoupling content from location, so that additional copies of the same content in different locations of the network can actually strengthen the content's availability, instead of being non-addressable and thus wasted.
Yes, that's the basic idea of all multiformats: "it's never gonna change" is considered harmful.
> Unifying here might allow git objects to be served natively over IPFS.
IPFS can already do that thanks to the CID format: https://github.com/ipld/cid
There's no good examples for Git specifically yet, but there's a good bunch of working code for transporting e.g. Ethereum and Zcash transaction blobs over IPFS. For Git it's in principle the same: import the raw object into IPFS, and starts addressing it with /ipfs/<git-cid><original-git-hash>
Files and directories are just one particular data structure you can store on IPFS. Think of it as a global unified content-addressed graph database really, and Filecoin can store any arbitrary (sub)graphs within that.
- https://ipfs.io/ipns/peerpad.net
- https://ipfs.io/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6...
- http://localhost:8080/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW...
And with the ipfs-companion browser extension:
- dweb:/ipns/peerpad.net
- dweb:/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD
- ipns://peerpad.net
- ipfs://QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD
Or by grabbing it using `ipfs get /ipns/peerpad.net` and clicking the html file in the resulting directory.
This is also the tech that PeerPad is built on: https://peerpad.net && https://news.ycombinator.com/item?id=15624158