Backup holders forgetting about / losing backups is a show-stopping problem too
All three problems are actually symptoms of a more fundamental problem: Lack of regular maintenance. Maintenance and verification need to be central to Kin.
Kin needs a server component that does three things:
Allows the owner to upload newer data
Allows the backup holders to automatically download newer data during a verification process
Notifies the owner when a backup holder hasn't run the verification process for a while
This could involve potentially setting up a Docker container on a server somewhere, or perhaps a free-tier Heroku app. The project settings would need a URL to the server, and that URL would be included in backup metadata.
This also drastically increases the scope of the project. Maybe I'll tackle it after another 3 years...
After more than 3 years of letting Kin rot, I have some fresh perspective:
All three problems are actually symptoms of a more fundamental problem: Lack of regular maintenance. Maintenance and verification need to be central to Kin.
Kin needs a server component that does three things:
This could involve potentially setting up a Docker container on a server somewhere, or perhaps a free-tier Heroku app. The project settings would need a URL to the server, and that URL would be included in backup metadata.
This also drastically increases the scope of the project. Maybe I'll tackle it after another 3 years...