vyzo

So where are we blocked here?

its an RLock, so they should not content, they can hold it concurrently. Only close takes the exclusive lock. It is not entirely the same because an active publish would...

Let me think about it a bit. I dont think there will be any deleterious effects from the change, but it is still a change in behaviour.

it is not as simple, without the hello packet the other nodes will not see them as part of their topics of interest. A possible approach is to have these...

ok, maybe `badly` was too strong; basically supernodes wont talk or mesh with each other. But given the architecture you describe maybe it is not so bad, might even be...

On the architecture side, what you describe is very sane and i think it could work well. There shouldnt be an issue with supernodes having many topics and yes, it...

Note that I will accept a pr implementing an option (`WithLazyHello` might be a good name) that enacts the lazy hello policy. Basic outline would be to not emit the...

Info is an appropriate level for this I think; it used to be Warn and we lowered it to info sometime ago.

You probably want to set your log level to WARN; INFO generates lots of spam.

Its a go-libp2p problem, not a pubsub bug.