bug: Messages are not rendered in the frontend when sent via the go-peer

[p-shahi]

@2color :

I did some testing of the go-peer.
There’s a bug that I think we saw with Rust where sometimes messages aren’t rendered in the frontend even though there’s a log in the frontend saying RPC gossipsub:
https://share.descript.com/view/rXxz0yCOHjF

@p-shahi :

This issue occurred with the rust peer since it was sending each message with the same sequence number. Js-libp2p-gossipsub’s default behavior was to use the sequence number to deduplicate messages and since the numbers were the same it was discarding some messages received. Adding the message ID function in js-libp2p-gossipsub fixed it.
I don’t think it’s the same issue since the same message ID function will be applied to all incoming messages regardless of go or rust peer. Can try to dig into this today.