Re:Why build this blog, or anything, on IPFS?
by Sargos on Sunday January 19, 2020 @05:43PM
(#22094662)
I consider IPNS fundamentally broken and have stopped using it. ENS is better in almost every way and is extremely reliable so it's not that big of deal.
Re:Why build this blog, or anything, on IPFS?
by momack2 on Sunday January 19, 2020 @06:03PM
(#22094760)
IPFS and ENS work pretty seamlessly together (https://medium.com/the-ethereum-name-service/ethdns-9d56298f...), but some folks also want the mutable pointers layer of IPNS too. We're working on making that faster: https://www.youtube.com/watch?v=XniIDIXU8RE&t=10s
Re:Why build this blog, or anything, on IPFS?
by StavrosK on Sunday January 19, 2020 @06:12PM
(#22094803)
How can I register an ENS domain/id? I've found very little practical info on a cursory search.
Re:Why build this blog, or anything, on IPFS?
by Sargos on Sunday January 19, 2020 @06:20PM
(#22094849)
There's probably a simple article out there but I'll summarize it a bit:
You go to https://manager.ens.domains/ to register a .eth address and on the settings page for your domain you add a Content record and point it to ipfs://Qma7nxS98CAb2BTaxLJBSFozxxSp5XTu6tMtCrKcRQ9ByV or whatever the IPFS hash of your website is.
After that you can visit your site at https://myname.eth in a browser that supports ENS/IPFS or you can go to https://myname.eth.link in any browser and see your website.
Re:Why build this blog, or anything, on IPFS?
by StavrosK on Sunday January 19, 2020 @06:23PM
(#22094866)
This is what I needed, thanks!
Re:Why build this blog, or anything, on IPFS?
by mmurthy on Monday January 20, 2020 @07:40AM
(#22098375)
I created a service to make it easy to buy and configure ENS domains in one step. Hope it helps! www.namestack.io.
Re:Why build this blog, or anything, on IPFS?
by StavrosK on Monday January 20, 2020 @07:43AM
(#22098393)
That's helpful, thank you. Unfortunately it looks like .eth domains have already been squatted to hell.
Re:Why build this blog, or anything, on IPFS?
by AgentME on Monday January 20, 2020 @02:41AM
(#22097109)
I really wish everything written about IPFS would just ignore IPNS, and stop presenting it as a standard part of IPFS. The thing IPNS tries to do can be done better by the existing DNS system (which works fine combined with IPFS) or blockchain-based systems like ENS. IPNS is a slow incomplete tech demo glued to the rest. Ignoring IPNS won't impact your understanding of the rest of IPFS. I don't think people relying on IPFS even use IPNS for anything but a curiosity, and it's so bad that I expect many people get turned off of IPFS because they get confused by IPNS's flaws or assume that the rest of IPFS works as badly.
IPFS is good at content-addressed storage. IPNS is not part of content-addressed storage. Tutorials about IPFS should ignore IPNS, and talk about alternative ways to link to IPFS links, like using DNS.
* = unless something has radically changed in the last few months and they just haven't closed the GitHub issue: https://github.com/ipfs/go-ipfs/issues/3860