IPNS Persist Proposal
IPNS is Great. IPNS builds a decentralized DNS-like system and makes us possible to create a mutable website. However, IPNS also has its own problem and the problem is that IPNS could lose record. This problem will be pretty annoying sometimes when I use IPNS in my project. For example, Image that you are building a decentralized web forum and you decide to save an IPNS address as a pointer to user’s posts. Unfortunately, users are not tech-savvy and they will forget to, or just don’t want to, republish their IPNS address every 24H (Default IPNS lifetime). Maybe someone will say:” Why not let users push their posts to a special sever and then let the server publish posts to IPFS? ” Yes…It works and it is an effective way. Actually, the ZeroNet forum exactly uses the same model. (See their slide). But, It means centralized and the owners of the forum still have the right to censor, or prohibit, posts that they do not like. (I come from China, so you know why I hate censorship so much).
Anyway, saving IPNS records is a quite common need for many services. If it is a common need, It’s worth standardizing. And there are two ways to finish this job.
The first way is that makes this function to become a feature of IPFS. As I know, IPNS record is just special data in the IPFS world. Maybe we can pin this data and automatically update it when the data changed?
Or, We can follow the same stand and make some libraries to handle this job.
And those are my opinions. I’m not a native English speaker, so if I made any grammar mistake, welcome to point out.