Active relay peers are peer which are part of the gossip mesh.
Which means that it's not just a peer we are connect to but a peer on
subscribed to the same pubsub topic, with a good score, part of the
mesh, etc.
Mesh maintenance is done during the gossipsub hearbeat so it's the best
time to review the count.
A store peer is any peer we are connected to that support the store
protocol, so it can be counted when a new peer is added to the store.
This does not cater for store peers that disconnect, but we are not
handling those just yet.
It is a type used for the [TOY-CHAT](https://rfc.vac.dev/spec/22/)
protocol;
js-waku users should not build on top if this toy protocol and instead
design message data structures appropriate to their use case.
Only retrieve historical messages when starting the app.
This allows avoid re-rendering issues. This is an example dApp. No need
to waste time on React optimisation.
It does not work as it can lead to infinite loops due to the handling of
the Waku instance. It should disconnect and reconnect to peers instead
of starting a new waku instance.
