fix: Potential fix for interop with rust subscriptions

[maschad]

No description provided.

[what-the-diff]

PR Summary

• Improved message distribution in topic mesh The code now checks if there are more peers in a topic mesh than the number of subscribers, ensuring messages reach more users and not just direct neighbors. This change might lead to receiving duplicate messages, as others are also implementing the same logic.

[codecov-commenter]

Codecov Report

Patch coverage: 50.00% and project coverage change: +0.01 🎉

Comparison is base (a959b09) 82.98% compared to head (4a0bf4b) 83.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #418      +/-   ##
==========================================
+ Coverage   82.98%   83.00%   +0.01%     
==========================================
  Files          48       48              
  Lines       11874    11878       +4     
  Branches     1280     1283       +3     
==========================================
+ Hits         9854     9859       +5     
+ Misses       2020     2019       -1     

Impacted Files	Coverage Δ
src/index.ts	70.38% <50.00%> (+0.07%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[dapplion]

This conversation can only be viewed if you sign up. Can you add more detail of what's going on?

[maschad]

The discussion is in a public channel #libp2p-implementers on Filecoin slack (which is bridged to IPFS Discord/Matrix).

The problem has been resolved now so this is no longer relevant. Essentially in debugging I had found that there was an issue of rust-libp2p sending subscription messages to js-libp2p-gossipsub after GRAFT messages over webRTC