Estuary Gateway

[alvin-reyes]

There's currently an existing /gw on estuary to serve contents.

It would be great to map this to a domain name (https://estuary.link or https://gateway.estuary.tech) and use that on the frontend (estuary-www) for files uploaded via estuary shuttles.

Slack discussion(s) here: https://filecoinproject.slack.com/archives/C016APFREQK/p1655227850747479

Update / Proposal

We need a separate gateway for upload and retrieval that is separated from the main node. This gateway will act as a forwarder to the api or one of the shuttles.

• we need to create a separate gateway. We can use the shuttle-proxy as the basis of this new standalone node
• we need to extract the authentication and the forwarder (we can use alvin-reyes/estuary-auth)
• we need to add a shuttle selection process (geo aware). This means we need to get the requesting client geo location and use that as the basis of where to forward the request.
• we need to put it behind a estuary.tech gateway domain (shuttles.estuary.tech)
• all shuttle endpoints should be available plus basic gateway endpoint for retrieval (/ipfs/)

[alvin-reyes]

We need to figure out a way to "validate" or "stage" requests before handing them off to Estuary. (Cloudflare?)

[Jorropo]

https://gateway.estuary.tech/

Don't make the same error as ipfs.io, putting a gateway on your main domain is bad since spam lists and search engines wont understand how to differentiate the spam and the not spam.

[3456091]

In line with ipfs/in-web-browsers#128 , and its associated issues, the ability to get a CAR from the gateway would be useful.

[alvin-reyes]

We can create a separate gateway for estuary (estuary-gateway) specifically just for retrieval. We can then map this gateway.estuary.tech