[momack2]

Thanks! We've been making a lot of updates to the documentation to make it easier to use - so glad it feels easy to follow!

I'll follow up on the Pinata docs example. There are a lot of options for how to persist content in the IPFS network, and we should describe all of them (even if Pinata is one of the smoother/easier to use ones for those new to IPFS who don't want to run their own persistent node). Feel free to file an issue or PR on that docs page if you get a second and we'll help get that fixed ASAP.

Given interest in decentralized persistence, you may be interested in collaborative clusters which allow a group of peers to all persist each other's content: https://collab.ipfscluster.io/ & https://cluster.ipfs.io/documentation/collaborative/

[toomuchtodo]

Would you happen to know if the Internet Archive intends to use collaborative clusters to globally distribute archive contents on IPFS?

[momack2]

That's a great idea! I know there's a project in the works to have redundant copies of the Archive stored on Filecoin, so expanding that to also make the data available for Collaborative Clusters should be totally doable. We'd have to slice the archive down into bites that small machines like yours and mine can help with though. Thanks for the suggestion!

[IgorPartola]

Thank you for that info. I am still very new to IPFS but am going to try to learn more before I submit any PRs or anything like that. Is there some way to see how pinned content is distributed? Do pinning services have a standard API for talking to them?

[momack2]

We're actually implementing a standard Pinning API right now! You can check out the spec here (https://github.com/ipfs/pinning-services-api-spec) - currently being integrated by Pinata and soon others.

By the way, here's a PR to add other pinning options to the docs: https://github.com/ipfs/ipfs-docs/pull/471