IPFS：重复固定 - 在两个不同的位置固定文件？
我目前正在使用FileBase（付费IPFS固定服务）来固定我的IPFS文件。 Filebase仍在Beta中，因此价格较低，但将来可能会上升。
因此，我想将所有文件的副本保留在家用计算机上的驱动器上，以防Filebase在将来有问题，中断等。我的本地计算机文件将是IPFS节点本身。
我也应该在计算机上固定这些本地文件吗？还是重复的固定会导致问题？
I'm currently using Filebase - a paid IPFS pinning service - to pin my IPFS files. Filebase are still in beta, so the prices are low but could rise in the future.
Therefore I'd like to keep copies of all my files on a drive on my home computer too just in case Filebase has problems,outages, etc. in the future. My local computer files will be an IPFS node itself.
Should I pin these local files on my computer as well? Or will duplicate pinning cause problems?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可以将本地文件完全固定在运行家庭计算机上的本地IPFS节点上。但是，您的家用计算机上的节点更有可能崩溃，否则机器本身会比文件库损坏。 TRUE Filebase是一项具有单一故障的集中服务，但是他们可能正在运行多个IPF节点来固定您的文件并将其长期存储在SIA网络上。
最安全的选择是探索在
You can totally pin the local files on your local IPFS node running on your home computer. However, it is more likely that your node on your home computer will crash or the machine itself will corrupt than Filebase. It's true Filebase is a centralized service with a single point of failure, but they are likely running several IPFS nodes pinning your files and storing them long-term on the Sia network.
To safest option is to explore storing your data on Filecoin, which is equivalent to Sia in the sense that it is for long-term persistence (which IPFS is not). Think of IPFS as the decentralized version of Redis. It can cache and store information, but it's not designed to store them like a database is.