Community Pinning / PinCoop

[ghost]

We want to make it easy for the community to pin stuff in order to keep it around. We have Pinbot in #ipfs already, but we want moar!

@victorbjelkholm has been working on PinCoop, which is a web app that pins any given hashes on a number of nodes, via their IPFS API. One problem with this push-based approach is that the API needs to be opened up, in particular /id and /pin/{add,rm,ls} endpoints.

There is another idea around a pull-based approach, where users submit hashes to a pinlist, which participating nodes pull and apply at their convenience. The pinlist could live within https://ipfs.io/refs (see ipfs/refs), and there could as well be multiple different pinlists.

[victorb]

Nice! PinCoop was supposed to be a community run service where people can "donate" pinning of content that the community would like to stay up forever. Early on, I was thinking about the benefits of a push based model which is minimal setup from the node-owners point of view, and speed of getting an overview of the network. But quickly after starting prototyping, I starting realizing the downsides. Security and complexity being the top ones.

So right now, I'm working on a much simpler pull-based model, which is easier to develop and hopefully will be easy to setup as well.

Looks a bit like this atm:

My main point with this is two things. Provide a GUI to easy pin content that you've added elsewhere. Second point being to provide an API to pin things that you've (or your user) have added through your service.

All feedback is good feedback so speak your mind please :)

[davidar]

👍

@victorbjelkholm have I already discussed the possibly of splitting large datasets across multiple nodes with you?

[victorb]

@davidar I don't think so. I know it's something we want but I haven't give it a thought yet. If you have any thoughts around this, please explain more so I can understand it :)

[jbenet]

Let's please make ipfs-cluster