Open lidel opened 4 months ago
I think we should consider how we name this and call it in the docs and materials we will create before we make a splash. I propose we call it "Service Worker IPFS Gateway" or just "Service Worker Gateway" since the fact that it uses Helia is an implementation detail for most users. Moreover, it should be pretty clear that it's powered by Helia since it's the most actively maintained JS IPFS implementation.
I figured it's a good time be bring it up since we're going to be using the inbrowser.link
domain for it (which already doesn't have Helia in it).
@2color agree, we can mention Helia on the landing page (https://github.com/ipfs-shipyard/helia-service-worker-gateway/issues/58) but this project should be branded as "Service Worker [IPFS] Gateway" or ipfs-swgw
.
We already have to move to ipfs/ org, renaming repo could happen at the same time. Let's discuss details in https://github.com/ipfs-shipyard/helia-service-worker-gateway/issues/80
I added a list of CID of sites for manual testing to the issue body. Feel free to add any additional ones.
NOTE: subdomains don't automatically refresh the service worker.. so we need some clever logic for checking for service worker assets, and then redirecting to /#/ipfs-sw-config again.
see https://github.com/ipfs-shipyard/helia-service-worker-gateway/pull/96 for some changes that make this more likely to happen
Question: should we default to an ipfs favicon when favicon.ico doesn't exist...?
We should not modify immutable data. If the DAG that user tries to load does not have favicon, we should not add it.
Add the following examples to the list and make sure are working well enough before sharing:
For general use
Minimal feature set
Optimizations
Security and Compliance
UX / Configuration
For
inbrowser.link
inbrowser.link
(subset of https://github.com/ipfs-shipyard/helia-service-worker-gateway/issues/30)105
107
Until we get automated testing in place, here's a list of CIDs of websites for testing the Service Worker Gateway
bafybeiaysi4s6lnjev27ln5icwm6tueaw2vdykrtjkwiphwekaywqhcjze
bafybeifaiclxh6pc3bdtrrkpbvvqqxq6hz5r6htdzxaga4fikfpu2u56qi
bafybeiae366charqmeewxags5b2jxtkhfmqyyagvqhrr5l7l7xfpp5ikpa
cid-ipfs-tech.ipns
bafybeiedlhslivmuj2iinnpd24ulx3fyd7cjenddbkeoxbf3snjiz3npda
docs-ipfs-tech.ipns