How often do you garbage collect files on your IPFS node and how long will a file persist after upload?

We support pinning your IPFS content. If you don’t pin it, we garbage collect when we need to reclaim space. However, we will be collecting more periodically soon.

1 Like

So as long as it’s pinned it stays up indefinitely?

I see that the pinning API is unauthenticated. Is there a way to associate my pins to my account so I can manage them?

[Cross-posting from twitter at @mike’s suggestion.]

Correct, that is the functionality now, we are very close to adding auth to the IPFS endpoint which will give you greater control over your content. If you want to provide more details on your use-case we’d love to hear more, always helps us make sure we are going in the right direction.

1 Like

Oh that’s cool! The use-case I have in mind right now is simply deleting content in case I don’t want it to be seeded anymore. (Of course peers who have a copy of it can keep seeding it, but I’d at least remove the stable seed I myself uploaded to.)

I do hope there remains some unauthenticated option to use Infura though, even if more strongly rate-limited, because it makes for such a wonderful and frictionless on-ramp to new users. Infura is the only default upload method for ipfs-deploy, an npm package I’m working on, at the moment because it’s the only one I know of that can be used right away without needing to sign up or leave the command line.

Really appreciate the feedback!

1 Like

Hey Mike!

I have some doubts about infura’s IPFS remote node, and you “almost” answered them. Could you give me more insights?

- Infura’s IPFS remote node doesn’t pin files; it only add them, for obvious reasons. That’s it?

I’m using ipfs-http-client with infura in my DApp, and that’s the kind of thing hard to test, once GC could take months to remove them.

We definitely support pinning, when making a request to /add, the IPFS API defaults to pinning content if not explicitly requested not to
pin [bool]: Pin this object when adding. Default: "true". Required: no.

Does your use case depend on being able to control GC or file deletion?

My need is that the file added will be always available.

So, when you need space, you unpin them, and then GC?

Currently, we do not unpin anything that has been pinned or added using the default pinning setting.

1 Like

Nice. Thank you!

I thought that, in a logical way, infura would need space at some point, and would remove files that had already been around for a long time.

Also, that’s a important information that I could’nt find anywhere. Still, I found other people with the same doubt who did not get the answer. This information deserves to be highlighted.

Thank you again!

1 Like