I don't use Vue.js and I have never heard of the debounce API. Neither is specific PubNub and there are dozens of JS frameworks out there so not possible, or necessary, to know them all.

I still think PubNub needs a new configuration parameter in subscribe() which sets the polling interval for presence, but let me take another look tomorrow since you have made some changes in our configuration and see if I set subscribe presence to TRUE in my code (it is current set to FALSE), if it keeps polling and polling like crazy.

Subscribe already has an interval, it is the subscribeTimeout config, that you can set in the PubNub init, but please do not. It should only be changed for very specific reasons, that I will not get into right now. You will only cause your app to have increased transactions at no additional upside or cause your app to break depending on whether you set it shorter or longer. The default subscribeTimeout is 280s, and this is exactly the same for listening to presence events because it is on the subscribe connection. The hereNow is a completely different API and a different connection which does not work on the subscribe connection.

When you subscribe withPresence:true, you are just adding presence channels (with the -pnpres suffix) to the list of subscribed channels. When another person subscribes to that channel, those listening to presence events (withPresence:true) on that channel will receive that presence event, in realtime, not on some polling cycle.

But see my response about Announce Max. The increased transaction were self-inflicted Not that you would have known the side effects but rarely does anyone change that setting.

And I just checked the chat app again. It appears you upgraded to lastest PubNub JS SDK version - cheers - and I see that the client is not having the 10s interval response anymore. At most it will be 280s or everytime someone joins, leaves, timeouts, or a message is published and therefore received.

Cheers
Craig