Steve Loeppky

@Jorropo : what are the next steps here? Is this realistically going to get merged the next month?

@Jorropo : fine if not, but were you able to reproduce on Linux?

@Jorropo : I assume you haven't had a chance to reproduce it on Linux.

I'm putting this as "Best Effort" as core maintainers need to decide if they want to invest more in MFS and the requirements before putting more weight on the feature.

@hacdias @Jorropo : I'm hoping you can take this given having recently gone through this with 1.21. Minimum: point to the set of PRs we had to do for 1.21...

2023-11-09 maintainer conversation: * High level: we either need to be able to update or we revert the breaking changes in go-libp2p-kad-dht * We can't test WAN mode in the...

2024-01-04 maintainer conversation: * We don't know why 0.25 broke. We need to start here. Once we understand (and document) this, we will then figure out how we respond. (Getting...

2023-07-06 maintainer convesation: we agree this is good/reasonable todo. That said, we are ok to ship a go-libp2p update without this as things will "still work" :)

> Noted that it does not appear to be used yet by the latest kubo https://github.com/ipfs/kubo/blob/master/go.mod#L74 , is it safe to simply include this module version in a source build?...

I expect this will land in Kubo 0.21 (not 0.20) given Kubo maintainers are busy preparing for IPFS Thing and WebRTC hasn't shipped in go-libp2p yet.