Oliver Wangler

Another option would be to let `Fn::ImportValue` have a type param of the expected resource.

Hey! Thanks for your feedback. First of all, the state and workings of this crate is subject to change. I was thinking about a) making it compatible with `libp2p-webrtc-star` signaling...

Maybe a viable solution for you would be to amend the signaling server with a libp2p node offering a `rendezvous` point for host discovery. I did exactly that for another...

It's not public (yet). But the gist of the discovery mechanism would be to follow the example of the rendezvous protocol from https://github.com/libp2p/rust-libp2p/blob/303490103b8c1641b9182b622810639a1c86b739/protocols/rendezvous/examples/rendezvous_point.rs#L33-L40 And in your client code you'd connect...

Not sure I understand your problem. The `rendezvous` behaviour protocol (both server and client) is transport agnostic. Anyway, happy to help out further, but maybe not in this issue. >...

So it seems the request returns indeed does return a 200 (so no problem with this library per se nor with `tonic-web`; developer console), but the Promise returned by the...

This is about being more liberal in what we accept when parsing, see for example https://github.com/ipfs-rust/libipld/blob/d92d261f4831f943ab243aa215d871a5734e8d89/dag-cbor-derive/src/gen.rs#L239-L241 and https://github.com/ipfs-rust/libipld/blob/d92d261f4831f943ab243aa215d871a5734e8d89/dag-cbor-derive/src/gen.rs#L298-L300

No, I think what it needs is - [ ] a more convenient API, maybe included in #38 - [ ] fix for #72 (probably #48)

Did users really request snap packages?

Now this feature could be a differentiator for Actyx, making Event Sourcing _more friendly/productive/whatever_. But this feels very grave, like time-wrap grave, and is from what I concern **NOT** the...