Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storing content in Filecoin that already exists in IPFS. #1083

Closed
kuzdogan opened this issue Oct 18, 2021 · 1 comment
Closed

Storing content in Filecoin that already exists in IPFS. #1083

kuzdogan opened this issue Oct 18, 2021 · 1 comment
Assignees
Labels
dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or an improvement to an existing feature P3 Low: Not priority right now

Comments

@kuzdogan
Copy link

kuzdogan commented Oct 18, 2021

What's the subject of the item you're requesting?
IPFS pinning via Filacoin

What's the content of the item you're requesting?
I was considering pinning the IPFS content I have using the Filecoin for a more decentralized pinning, instead of using a centralized pinning service. However, it wasn't really clear how to achieve this in the docs. The IPFS and Filecoin section is more on the technical side.

FPS section brings even more confusion. What's the relationship of this with IPFS pinning? I see the how to use section but it's not really explaining how to use it. Then jumps into the architecture of an FPS? Do I need to know this to use? I just want my IPFS content pinned on Filecoin and there's nothing explaining that.

It seems other people also need more clarity on this, as this was exactly the problem I was trying to solve mention in this issue: filecoin-project/specs#1191 There's the impression that Filecoin is a way to pin things on IPFS seamlessly in a decentralized manner. I believe most of the content within the linked issue should be baked into the IPFS and Filecoin page.

What will the user know how to do after going through this item?
What are the options to use Filescoin to pin IPFS content. This may include third-party services or one's own setup.

Would you be interested in helping create this item?
I first need to figure out myself.

Is there any other feedback you'd like to share about Filecoin docs?

@kuzdogan kuzdogan added feature-request need/triage Needs initial labeling and prioritization labels Oct 18, 2021
@johnnymatthews johnnymatthews moved this to Needs triage in Protocol Docs Oct 19, 2021
@johnnymatthews johnnymatthews changed the title [CONTENT REQUEST] Pinning IPFS content over Filecoin Storing content in Filecoin that already exists in IPFS. Oct 26, 2021
@johnnymatthews
Copy link
Contributor

johnnymatthews commented Oct 26, 2021

This is a fair issue. Something that we need to clear up is that content is never pinned in Filecoin; only IPFS can pin things. Filecoin nodes do run IPFS in the background, but the process that does the pinning is IPFS, not the Filecoin miner (lotus, venus, forest, fuhon, etc).

If you're looking for a service that does this already, then take a look at either Estuary or Web3.Storage.

It'd be good to clarify how pinning, IPFS, and Filecoin all work together.

@johnnymatthews johnnymatthews added dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or an improvement to an existing feature P3 Low: Not priority right now status/ready and removed feature-request need/triage Needs initial labeling and prioritization labels Oct 26, 2021
@johnnymatthews johnnymatthews moved this from Needs triage to Backlog in Protocol Docs Oct 26, 2021
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Protocol Docs Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or an improvement to an existing feature P3 Low: Not priority right now
Projects
None yet
Development

No branches or pull requests

3 participants