​Description from here: https://github.com/ipfs/go-ipfs/issues/8499

​Background

​Many (most?) Gateways Providers use go-ipfs or some forked version. go-ipfs is in a challenging position of being a single binary supporting desktop application and web-service needs via configuration. go-ipfs maintainers are concerned that we're either not serving either party very well and/or more slowly than we ought.

​What are we going to do?

​We are not committed to any changes yet, but we believe it's appropriate to at the minimum:

1. ​Check in and review current Gateway operator usecases and understand Gateway operator needs/wants.

2. ​Determine if a separate/different development effort targeted towards gateways would be appropriate. Should the answer be yes, the next step would be to create a plan as a community and also execute it as a collective.

​Feel free to link/post ideas/thoughts, and go-ipfs maintainers will as well.