ipshipyard / waterworks-community

Discussion and documentation concerning the operation of the Public Goods for IPFS and Libp2p.
https://docs.ipfs.tech/concepts/public-utilities/
MIT License
2 stars 1 forks source link

Landing pages for gateways at ipfs.io, dweb.link, trustles-gateway.link #15

Open lidel opened 8 months ago

lidel commented 8 months ago

This is followu-up for verbal discussed in one of recent meetings between Shipyard and IPFS Foundation. cc @cewood @mishmosh @2color for visibility and feedback.

Need

We want to reduce confusion by having meaningful landing pages at public utilities such as https://ipfs.io, https://dweb.link, and https://trustless-gateway.link

https://ipfs.io is the biggest problem, it redirects to project website, creating an impression the IPFS Project and Shipyard-run gateways are the same thing.

Below is my first stab at describing current state + what I would do to "fix" the confusion.

Proposed information

https://ipfs.io

https://dweb.link

https://trustless-gateway.link

Logistics

TBD. We could have separate repos, but I'd like to keep this contained and easy to review/maintain.

MVP does not have to be involved. We have about.ipfs.io at https://github.com/ipfs-shipyard/ipfsio-about.

We could reuse ipfsio-about repo and setup, and have landing pages at:

And then set up Nginx for non-/ip[nf]s on these domains as reverse-proxies for these URLs.

I think this makes things easier to land, @mishmosh can review above URLs before we deploy Nginx configs and publish them at roots of these domains. And we can apply changes across all of them via a single PR to a single repository.

Thoughts?