Closed daviddias closed 9 months ago
Currently, a pinner is simply another node that tries to participate in all collaborations is sees and blindly tries to replicate the state.
We plan to have the pinner save state to IPLD and then pin it.
This will allow to easily migrate every collaboration to IPLD by just revisiting all past collaborations.
Having said that, I don't feel strongly on guaranteeing persistence on an alpha, and I'm ok with waiting for the current endeavour of decentralised IPNS saving to be finished before we can communicate that guarantee (but this is a PM decision).
Our super short term goal is to use it for our working group meeting next week. We could probably manually copy the data to a github gist for long-term persistence for that particular meeting. As @pgte says, the IPLD solution is where we want to be.
There needs to be a strategy around long-term persistence support. If I bookmark a pad today, will I be able to see it in a year? The answer should be always yes.
This leads to start thinking on how to upgrade the data model of PeerPad without breaking retro-compatibility. It also highlights how the current Pinner is a short-cut that might lead into a very complicate situation soon.