Marcin Rataj

@hsn10 this is a sensible improvement. Do you have any suggestion on how this should be presented in the user interface?

Mind elaborating? What browser are you using? Opening https://ipfs-search.com/#/search/detail/video/QmNsSibFj2vAu7feh83kw26nym4Mx94hXSVF2yUxtJ7Qnc?q=mp4&page=1 in Firefox with IPFS Companion loads video from the local gateway. What is not loaded from local IPFS node are centralized...

Kubo: - afaik android/ios is not officially supported, but if you are able to run Kubo on these platforms, the modern default settings should be ok - we are encouraging...

I would be afraid to ship this under shipyard-owned domain like inbrowser.dev without having some story for applying https://badbits.dwebops.pub. I've added task "BLOCKER for deployment to inbrowser.dev" to the list...

Denylist from https://badbits.dwebops.pub/badbits.deny is ~15 MiB (gzipped). If we go the JS blockstore route, no matter how it is fetched (remotely, or embedded in same DAG as SW), ~16 MiB...

@2color I agree, been marinating on this for a while and I think we can enable it on `inbowser.tld` without waiting for badbits for JS. I think we could have...

@2color we could do it, but not sure if we want to do that by default. We had false-positives in the past, there should be a way of disabling denylist....

This is specific to subdomain gateway, so does not benefit users who use `veirfied-fetch` directly, but yes, implementation-wise, it would be the easiest if it lived in `verified-fetch` and returned...

@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...

We should not modify immutable data. If the DAG that user tries to load does not have favicon, we should not add it.