HelloZeroNet / HelloZeroNet/ZeroNet

[Suggestion] API to freeze specific files (prevent deletion or modification)

未关闭
#1,256 4 条评论 0 个 reaction 已指派 1 人 已被 @HelloZeroNet 认领 在 GitHub 查看
enhancement
主要语言
JavaScript
星标
18.8k
派生
2.3k
PR 合并指标
30 天内没有已合并 PR

描述

In some cases and particularly with Big Files, you would want to prevent the deletion of a user file or even a zite file. For example, if you seed a useful 2go image file and suddenly the user who posted it remove it, you will completely lose the file. I think even if the zite is deleted by the owner (ex: private-key compromised, all data removed), you should be able to prevent update/deletion of some files.

Implementation-wise, each file indexed in content.json could have a "frozen" flag, but no idea about how ZeroNet will share the files between peers if they are locked at a specific version in time (and I don't know if content.json files can be "customized" locally).
Use case: for a zite like ZeroUp, every file you seed could be frozen by default.

I know there are suggestions about versioning, but you can use tools like rdiff-backup if you really want to backup a zite. It's more about trusting your files from not being deleted, as you'd expect with things like torrent.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。