Evaluate usage of IPFS_GATEWAY_URL

AmplicaLabs / content-watcher-service

A Gateway microservice that watches for content on Frequency

https://amplicalabs.github.io/content-watcher-service/

Apache License 2.0

1 stars 0 forks source link

Evaluate usage of IPFS_GATEWAY_URL #76

Open mattheworris opened 2 weeks ago

mattheworris commented 2 weeks ago

During testing of SAT, it was discovered that content-watcher doesn't seem to use IPFS_GATEWAY_URL.

[ ] Evaluate whether or not content-watcher needs to use the IPFS_GATEWAY_URL or whether it should be removed.

wilwade commented 2 weeks ago

It doesn't require it, but it likely should use it?

Using your own gateway, if you have one, for IPFS content can improve your content retrieval times. (Specifically if you setup to use a larger gateway such as Cloudflare or Infura)

wilwade commented 2 weeks ago

That said, I don't think this is a v1 needed feature, so perhaps we remove it if it isn't used and then plan the feature