|
|
|
|
|
|
by devrandomguy
3217 days ago
|
|
|
Thanks for the correction, I was wondering when I would have to burn a namecoin or something. > IPFS and the Blockchain are a perfect match! You can address large amounts of data with IPFS, and place the immutable, permanent IPFS links into a blockchain transaction. This timestamps and secures your content, without having to put the data on the chain itself. While I'm at it, I should also mention the caveat that IPNS won't put an entry into the classic DNS system, so you won't get a yourdomain.com out of it. It just gives you a random permanent base62 name to refer to some updateable content. You could ameliorate that for yourself by running your own DNS service, and I actually like the idea of that - I'll name things for myself as I see fit. I'll be i.pub, facebook.com can be troll.psych, and Google can be surveillance.borg. Can't wait for people to see that over my shoulder. Oh, and good luck to anyone at work who is blocking domains for me. Yes, names have power, I think I should be in control of them. I'm sure it will be worth the hassle of canonicalizing URLs before sharing or passing them to third party systems. |
|
|
True that, but we (I work on IPFS) have support for DNS with IPFS. I guess the best example is the website for IPFS.
ipfs.io resolves to the following TXT record: dnslink=/ipfs/QmPCawMTd7csXKf7QVr2B1QRDZxdPeWxtE4EpkDRYtJWty
Which means the ipfs.io website is built on IPFS and can be accessed via the public gateways:
https://ipfs.io/ipfs/QmPCawMTd7csXKf7QVr2B1QRDZxdPeWxtE4EpkD...
But, the dnslink record also means we can resolve ipfs.io via IPNS and get the same hash:
https://ipfs.io/ipns/ipfs.io/
All three links actually resolves to the same content, but in different ways.
A little bit of magic :)