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
The main concern is the URL contains the hash and it changes with each update. The goal of this project is to have a static URL that always returns updated trackers. If you have the IPFS URL, it will get out of date quickly.
However, this doesn't mean you need to remember a long string of CIDs — IPFS can find the latest version of your file using the IPNS decentralized naming system, and DNSLink can be used to map CIDs to human-readable DNS names.
The text was updated successfully, but these errors were encountered:
The main concern is the URL contains the hash and it changes with each update. The goal of this project is to have a static URL that always returns updated trackers. If you have the IPFS URL, it will get out of date quickly.
Please... see this: "OrbitDB is a serverless, distributed, peer-to-peer database. OrbitDB uses IPFS as its data storage and IPFS Pubsub to automatically sync databases with peers. It's an eventually consistent database that uses CRDTs for conflict-free database merges - making OrbitDB an excellent choice for decentralized apps (dApps), blockchain applications and local-first web applications."
What do you think of the idea of having a webapp in ipfs to publish, store or list torrent trackers list with orbit-db?
(My idea is to use orbit-db to solve the above problem)
The main concern is the URL contains the hash and it changes with each update. The goal of this project is to have a static URL that always returns updated trackers. If you have the IPFS URL, it will get out of date quickly.
From the official page: https://ipfs.tech
The text was updated successfully, but these errors were encountered: