Alex Potsides

Refs: https://github.com/murat-dogan/node-datachannel/issues/172

> I don't believe the third item in that comment is accurate > >> the gateway does not need to be able to dial the browser (e.g. WebRTC) > >...

Blocked on https://github.com/paullouisageneau/libdatachannel/issues/970

For the most part we only use `BigInt`s where a protobuf definitions means we need to handle values encoded as 64 bit numbers - we cannot use the js `number`...

Closing as this is configurable via env vars as pointed out above and any extra work would not be carried out in this repo.

> I would like this to work: > > ``` > fetch(https://QmPeerID.libp2p/some-http-api) > ``` Can you define some inputs and some outputs please? > -ChatGPT (proofread by me) 😩

This seems quite reminiscent of https://github.com/SgtPooki/helia-service-worker-gateway - it's an application that uses libp2p and bitswap (e.g. IPFS) in a service worker to intercept HTTP requests and serve the content from...

Aha, awesome stuff. There's one fairly serious caveat - fetch in the browser cannot do full-duplex streaming, so the only protocols usable over something like this will be simple request/response...

It might not be an app at all, it might even be a special transport that creates the service worker and uses fetch to do the stream creation and muxing...

Related issue: https://github.com/libp2p/js-libp2p-utils/issues/12