Skip to content
This repository has been archived by the owner on Apr 29, 2023. It is now read-only.

[OTHERS] Put all logos in the same IPFS folder #2

Open
NatoBoram opened this issue Mar 27, 2023 · 3 comments
Open

[OTHERS] Put all logos in the same IPFS folder #2

NatoBoram opened this issue Mar 27, 2023 · 3 comments

Comments

@NatoBoram
Copy link

NatoBoram commented Mar 27, 2023

What:

In https://github.com/revanced/revanced-polling-api/blob/main/app/data/processed.json, all IPFS assets are in a different IPFS folder.

Why:

Having them all in the same IPFS folder make it way, way easier for any IPFS node to find them.

Moreover, once that folder is created, it becomes easier to cheat IPFS discovery with a tool like https://natoboram.gitlab.io/public-gateway-cacher to make assets easily discoverable.

When: During asset processing

Who: The person in charge of deployment

Where: On that person's computer. Note that these can be pinned on other computers as well for redundancy.

OBS: If not, then this issue is a great place to document the requirement that prevents that. (Likely keeping assets secret from each other. However, putting them on IPFS makes them public in the first place)

@oSumAtrIX
Copy link
Member

The assets are public and not considered confidential.

@oSumAtrIX
Copy link
Member

We use https://web3.storage, maybe you can assist in uploading them in the same folder. https://web3.storage does not have such an option.

@NatoBoram
Copy link
Author

Oh I think you have to use the IPFS CLI for that: http://web3.storage.ipns.localhost:8080/docs/how-tos/pinning-services-api/#using-the-ipfs-cli

Once you've ipfs add -w the list of assets, you can upload them to web3.storage with something like this:

CID=QmZnG6Qfx5yySaERWoJoqABct2iY8snN2jQfnceTwmDLUo
YOUR_AUTH_KEY_JWT=4e3f85d2-6710-48c3-8175-fa69633d0378

ipfs pin remote service add web3.storage https://api.web3.storage/$YOUR_AUTH_KEY_JWT
ipfs pin remote add --service=web3.storage --name=Processed $CID

It should even show up in the IPFS Companion

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants