5 ms·
IPFS has a so called IPNS system that use mutable hashes. So when you publish using this piece of software you got always a permanent link to share with your us
by paulogr 9y ago
IPFS has a so called IPNS system that use mutable hashes. So when you publish using this piece of software you got always a permanent link to share with your users.
- foxhop 9y agoWhat if I wanted to always link to the latest, like from my normal HTTPS powered web site? Is there a way to link to the head so that it always references the latest version?
- mstade 9y agoI believe that's what the previous poster means, you get a namespace that points to the canonical version of your resource, whatever that may be. Kind of like how HEAD is an alias for the latest SHA on a branch in git. But I don't know, this is just how I understood the previous comment.
- jstanley 9y agoThe latest would be a link like /ipns/yourcompany.com, and you'd have a TXT record pointing at your node's IPNS hash (or an IPFS content hash directly) and you update it by either updating what your node's IPNS hash points to, or by editing the DNS record to point to the latest IPFS content hash.
- foxhop 9y agoNow I'm even more confused. I suppose I'll watch a talk on youtube or something. Edit: currently watching this - https://www.youtube.com/watch?v=BA2rHlbB5i0 https://www.youtube.com/watch?v=BA2rHlbB5i0 (10 minutes)
- StreamBright 9y agoSo far we learned that the HTTP web is slow, impermanent and centralized. This is why it can support billions of people daily in every corner on the planet and have services like https://archive.org/ https://archive.org/. Time to move on I guess. I wonder why do we need an http to IPFS gateway for that video he just uploaded though.
- foxhop 9y agoEach time the page is updated, the TXT record would need to be modified with the latest IPNS hash?
- jstanley 9y agoNo, if you put an IPNS hash in the TXT record you just update your IPFS node. If you put an IPFS hash in the TXT record then you need to update that every time. I personally do this (domain name jes.xxx) because it means you don't need to leave your IPFS node running constantly in order for your IPNS name to be resolvable. The record is: jes.xxx. 300 IN TXT "dnslink=Qme12vJPtMpeUwmG2NLG11Q47jy2unSonegNJxQb9QgYax" And I have a small shell script to update it automatically.
- vertex-four 9y agoIPNS has a huge flaw, as I understand it - there is no way to prove, as a consumer of an IPNS name, that you’ve got the latest data. A malicious node in the network could present you with outdated information and you’d have no way to tell.
- yorwba 9y agoNot if the page itself contains the time it was last updated (IMO all status pages should have this, IPFS or not). Then you could still get outdated information, but you'd be able to tell.
- andyjohnson0 9y agoEven with a last update time on the page, how would you know whether that was really the latest update? You'd also need to know the update schedule.
- KirinDave 9y agoProcedurally; since updating IPNS records is free it's pretty straightforward to continuously deploy a tree. What's obnoxious about that is that existing IPFS daemons aren't really good at managing multiple identities so if you have multiple trees to maintain you're left writing custom software or using docker containers.
- diggan 9y agoYou can't prove that you got the absolute latest data (same with DNS by the way) as it's being distributed. However, a malicious node in the network can't present you with outdated information or false information, as the IPNS record is signed with the key from the peer. If the IPNS record wasn't signed, it would indeed be a huge flaw as it wouldn't be tied to a key from a peer. That would defeat the entire purpose of IPNS. Luckily, we don't have that flaw in IPNS :) Disclaimer: I work for Protocol Labs on IPFS
- vertex-four 9y ago