Provide more information on the requirements of your own pinning service
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
调研方向
从 issue 中链接的“create your own pinning service”部分开始,并查看相关的 ipfs-docs issue #1798。明确其中应包含哪些关于基础设施、可用性、存储、安全性和合规性的指导;完成的标准是文档为潜在的 pinning 主机提供已达成共识的要求和保护措施。
由索引模型根据 Issue 内容生成。
描述
Pinning seems to be one of the most fundamental requirements of some form of data permanence.
If you are an organization looking at IPFS as providing some form of long-term knowledge base or information records management then there needs to be a way to ensure the longevity of documents, e.g. within disposal schedules or longer within archival contexts.
Beyond that, it is also likely if you are seeing to further the decentralization of the web, you will inevitably want to support community pinning in some way, thus increasing the number of peers offering this, and reducing centralized points of failure.
Given, can some consideration be given to the create your own pinning service section of the docs such that it can provide some basic technical requirements that individuals and organizations might want to consider as they determine if they can host a pinning service.
E.g.
- server spec,
- specifically, minimum and desired storage amounts,
- requirements for memory versus compute, or both,
- minimum bandwidth needs,
- expected availability and uptime,
There seems to be related technology helping to determine if a service is compliant, e.g. https://github.com/ipfs-shipyard/pinning-service-compliance but to get to that place there seems to be little information, i.e. i could create a host, make it publicly available, and support the pinning API, but if it has 4GB memory and 10GB storage, I have no idea if it approaches anything considered a community standard.
Some documentation on protections for pinning hosts/peers may also be beneficial, e.g. the type of data that might land on a pinning service and be made available by pinning hosts, should be considered, as well as how to ensure legal and data protection compliance if at all possible. Content encryption isn't used by default by IPFS so how is data maintained on a pinned service? Is it visible to the provider? Could data be viewed outside of IPFS on those servers, and so on? Specifically from the perspective of a pinning host protecting themselves versus those adding content to IPFS as the general guidance there of encrypting your own information if you need to do that is likely better understood.
Connected to https://github.com/ipfs/ipfs-docs/issues/1798
- 主要语言
- Go
- 星标
- 334
- 派生
- 503
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ipfs/ipfs-docs 的其他 Issue
-
kind/suggestion need/triage
难度 1/5 1-3 小时 新手友好度 65/100
-
难度 1/5 1 小时以内 新手友好度 65/100
-
need/triage
难度 5/5 一周以上 新手友好度 5/100
-
难度 3/5 1-2 天 新手友好度 15/100
-
better gov ph未关闭
难度 5/5 一周以上 新手友好度 10/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 80/100
blinklabs-io/gouroboros#3026 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
AvengeMedia/DankMaterialShell#4291 ·
-
[Bug]: autoexport rejects OTEL_*_EXPORTER values that differ only in case可能已有人在做 @yuminn-k 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 79/100
open-telemetry/opentelemetry-go-contrib#10291 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
podman-container-tools/skopeo#3041 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复