3 ms·
Fwiw, IPNS is mutable - you wouldn't use applications directly over IPFS, you'd view them over IPNS. So it has mutability in the sense that a single address ca
by notheguyouthink 9y ago
Fwiw, IPNS is mutable - you wouldn't use applications directly over IPFS, you'd view them over IPNS.
So it has mutability in the sense that a single address can change content over time. It's nice though, in that if it's important that content stays the same, it always will.
- cocktailpeanuts 9y agoIPNS is virtually unusable at this stage. It's super slow that most people who use IPFS just use IPFS directly and try to come up with their own solution for this. I do hope they figure out how to solve this problem but looking at the discussions around the issue, it doesn't sound like something that can be easily solved, maybe never.
- diggan 9y agoI left you a comment addressing the IPNS slowness here: https://news.ycombinator.com/item?id=16434057 https://news.ycombinator.com/item?id=16434057 Short version: we know, it sucks and we have a couple of ways of making it better, fear not I also want to add that we have many other ways of doing mutable data over IPFS, not just IPNS. While IPNS is a naming system, having services on protocols with streams or using pubsub can also give you the ability to do mutable state in your application.