You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 29, 2023. It is now read-only.
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)
The text was updated successfully, but these errors were encountered:
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)The text was updated successfully, but these errors were encountered: