Steve Loeppky

@SgtPooki : unfortunately we don't have WebRTC in go-libp2p yet. Here is the new PR: https://github.com/libp2p/go-libp2p/pull/2337 . I have updated the "Preconditions" above. I believe go-libp2p is targeting mid-July, so...

Kubo 0.25 conversation: there will be work here if there is a new go-libp2p that has webrtc-direct that is non-experimental and/or if there is the webrtc (private-to-private) support

2023-11-30 conversation: given the conditions in https://github.com/ipfs/kubo/issues/9724#issuecomment-1804141957 haven't happened, there is no work for 0.25 on this. This is blocked until https://github.com/libp2p/go-libp2p/issues/2656 is addressed.

Thanks for creating this issue @Jorropo . I made some adjustments to the issue description including adding a formal task list. (Feel free to look at the changes in the...

Reopening since this isn't complete (only https://github.com/ipfs/kubo/pull/9718 is).

I just wanted to say thanks for folks sharing about their usecases and needs. For transparency, Kubo maintainers havne't done any work on this yet. In case it wasn't clear,...

2023-05-18 conversation: 1. Generally aligned to go with the less disruptive approach: https://github.com/ipfs/kubo/issues/9717#issuecomment-1543827199 2. We need check the validator that "ipns over pubsub" uses. We need to know what we're...

@pinnaculum : > Excellent reasoning. Will the merge of https://github.com/ipfs/kubo/pull/9684 break pubsub communications with previous kubo versions (say .. 0.18.x), or does it only affect the validator ? Good question....

Thanks for the continued feedback here. Just an update from the maintainers that changes here aren't going to make it in for [Kubo 0.21](https://github.com/ipfs/kubo/issues/9814). We'll be targeting it for [Kubo...

@Jorropo : what are the next steps here for getting this merged?