NOTE: This is a draft and is not finalize yet. We'll have to polish it until we all agreed on the approach.
Have mutable references to CID's. This could be through IPNS or an uuid stored on a db etc.
This feature would allow us to build out the following quality of life features.
A stable reference to a mutable CID allowing users to host a static site, and easily make changes without having to update DNS
Shorter gateway urls for sharing content (ex: estuary.tech/X67HG) (this is assuming we create a random uuid for the CID)
Proposed Implementation
I have tinkered with IPNS this quarter and here are the following issue I came across.
Each record needs to have a public and private key. If we are managing this on behalf of the user then it's simpler to store an uuid associated with the CID
If a user is to manage the public and private key, they need to create a new account on their wallet every time they want a mutable CID
This is why my personal preference is to create a new table in the database that stores a uuid with a reference to a CID that can be changed by the user. I'm interested in hearing other suggestions on how we can implement this feature wether it be through IPNS or my proposed implementation.
Idea/Proposal: Mutable Naming for CIDS
Proposal
NOTE: This is a draft and is not finalize yet. We'll have to polish it until we all agreed on the approach.
Have mutable references to CID's. This could be through IPNS or an uuid stored on a db etc. This feature would allow us to build out the following quality of life features.
Proposed Implementation
I have tinkered with IPNS this quarter and here are the following issue I came across.
This is why my personal preference is to create a new table in the database that stores a uuid with a reference to a CID that can be changed by the user. I'm interested in hearing other suggestions on how we can implement this feature wether it be through IPNS or my proposed implementation.