Replies: 3 comments 4 replies
|
Having a shared cache seems to be a compelling feature, which is worth exploring. Currently, we do not collect any usage data, so it is hard to estimate the effect of having such a cache. |
|
Great idea in my opinion. What about copyright infringements? Could it have financial consequences for the actors if we build up such a database? |
|
Considering distributed caching? I've pondered leveraging IPFS, datproject, or similar decentralized file systems for caching. It's an intriguing idea, especially for communal scraping endeavors. The choice of protocol boils down to trade-offs - for instance, IPFS offers robustness but requires managing content addressing, while datproject emphasizes versioning. As for the usefulness in your project, it depends on data density and request frequency. Sparse data might not benefit greatly, but it's worth exploring for efficiency and scalability. |
Uh oh!
There was an error while loading. Please reload this page.
Just a question if anyone has given much thought on doing some sort of caching via IPFS, datproject or similar decentralized file-system. I am mostly curious about opinions on protocols/choices/trade-offs for communal scraping activities, not sure if the caching for this particular project would actually be useful given the sparsity of the data and number of typical requests.
All reactions