Hello Vac Team,
First of all, thank you for making Waku! I’m late to the p2p messaging party and was dismayed to find that Whisper is deprecated, and not even geth supports it anymore. But no matter, because Waku now exists and you all seem very serious about carrying the torch.
As the topic states, I have some questions about the
js-waku API (for pure browser use). I got the basic functionality up and running with no trouble (thanks to the excellent readme examples on the github repo). However, the
queryHistory is giving me some issues due to my lack of understanding - particularly around obtaining the right
So, my questions:
peerIdeventually going to be exposed in the Waku API proper? Anything special I need to know about getting
change:protocolsto fire on
Are there any examples at present of the light push API?
Is deleting the content topic from
relay.observersthe correct way of removing a topic observer?
Will it be possible to either cancel the
queryHistorycallback at some arbitrary point (eg when a certain prior message age is reached), or otherwise set limits on it? Ideally I would only care about a fixed number of prior messages (eg 50 or less). And in my use case, the user is likely to click away from a given chat topic before it finishes loading old messages, so being able to fully cancel a query might be helpful.
Did I read correctly (somewhere, can’t remember where) that something like 1% of nodes would need to be full (non-browser) nodes, for everything to scale? My app will initially be desktop-centric despite running in a browser, so perhaps I can come up with some ways to incentivize running a full node (better chat experience etc). No promises, but if I’m using Waku, I’d want the app to be a good citizen.
I think that’s all for now! Let me know if I’m in the wrong place for asking this sort of thing.