Doug A
Doug A
Yes you can. In fact, this library is meant for native applications (such as a WebRTC Server) and cannot be used in the browser.
Also look to try this out, hitting the same issue.
> You could use libp2p's circuit relay, but the real question is who is going to allocate bandwidth for private peers to use Update: I believe with libp2p `circuit-relay-v2` it...
Also if Waku is focused on scalability with this issue, then eventually you'll likely consider Gossipsub over webrtc if you haven't already (I'm not that familiar with the Waku architecture)....
Perf, I'll try this! Just so you know.... the description is still saying `IndexedDB`. Which led me to an issue search, which led me to here. But it's still erroneous...
According to https://github.com/libp2p/rust-libp2p/blob/c93f753018af3a63c07e38c09672e0e1e8f1a385/protocols/identify/src/behaviour.rs#L79-L81 at least, it's described for Identify as ```rs /// Application-specific version of the protocol family used by the peer, /// e.g. `ipfs/1.0.0` or `polkadot/1.0.0`. ``` I know...
the example also uses a version from years ago (`0.10.0` vs today's `1.2.2`), and the API has changed since then
Thanks for your feedback 😀 For context, my use case is essentially: "Here is my public key, can you please send me a UCAN?" which is coming from someone who...
Cool! Where can we read up on the breakthrough change? (Is it the multiwriter stuff?)
Thanks Rod! Yep, what you suggested totally works. Don't even need to load the codecs, looks like Multicodecs auto loads that for us? ```js import * as dagJose from 'dag-jose';...