Darius Clark

As I think on this, I wonder if we could remove `futures-ticker` instead. It was introduced in https://github.com/libp2p/rust-libp2p/pull/3973 and from my understanding it was to used as an `Interval` alternative...

Hey @MrishoLukamba could you provide any logs or any informations showing that the browser-side doesnt work with relay when connecting and obtaining a reservation with the native side (which currently...

> and [@dariusc93](https://github.com/dariusc93) how can a wasm browser based relay client reserve itself in relay server if it cant support listening to an address? the browser doesnt support opening sockets...

Hey. Thanks for the report. Do you have any logs from when you dont see ReservationReqAccepted being emitted?

Since we will delay this, I will move this to draft for now.

I do like the idea of this being documented but I do wonder if we should make sizes configurable, either as a const or adding fields to `Codec` for the...

> I like the idea too, it would require more work but it might be usefull Though outside the scope of this issue, I would imagine it being something along...

Thanks for the PR. While the concept does seem interesting, unfortunately this is not something we can just add to rust-libp2p unless there been an update to libp2p specs to...

Hey @12TreeMan31. While I am not against having it public, could you explain what your use case might be to having it public besides consistency? I would have to double...

Thanks! Well im not against it being public. It would probably make it more consistent across other protocols that have it public as well.