That’s all good news.
Is there a list of all the available rpc nodes somewhere? Right now the extension makes practically all requests through the testnet-node-0001.nkn.org or whatever, which isn’t really the ideal decentralization you’d hope for. If there was a JSON file of the IPs that I could find, then I could send messages to a different one every time, basically.
About the buckets: if I’m subscribed to bucket 0, will I receive messages that someone sends to bucket 1? Will the publish method take care of that? Well, it’s not a concern for the add-on at this time.
About the duration: for a chat application, I see that a “subscribe until unsubscribe” would be nice.
Here’s a few more things that I think should be useful, for anyone interested in extending the libraries:
- Already almost exists in the publish method.
- Useful for getting the # of chatters online, for example.
- isSubscribed (and for how long?)
- Currently the only way(?) to know if you’re already subscribed is to re-sub and see the error.
I’d add the first one myself, but I’m just heading to summer vacation and won’t be online for a couple of weeks.