pubnub / chrome-console Goto Github PK

If I call the history or here_now end points from the javascript sdk, it would be cool if they could be included in the channel output classified as history/here_now

If you go to pubnub.com, there is an init against sub_key : sub-c-726c7474-9540-11e3-9615-02ee2ddab7fe

If I go to pubnub.com/console and subscribe to a test channel on the demo/demo key pair, publish a message, and then click the here_now or history buttons, instead of issuing these against demo, it is issued against the first sub_key seen on the page, which happens to be "sub-c-726c7474-9540-11e3-9615-02ee2ddab7fe"

The end effect is that there appears to be no uuids and no history.

15:51
It's like, I publish "test" to "chat" on "demo","demo", and then I switch to a client's key "blahblahl","blahablah", but leave the channel alone
Looking back later at your extension's output, it's like hmm... which key did I send that to?

Does this extension still work? If not, it should probably be removed from the chrome store.

Chrome 90, MacOS 11.3.1

Events are being sent, but nothing logged:

scrollbar gets stuck at the bottom

like here for example
http://www.pubnub.com/console/?channel=a%2Cb%2Cd&origin=pubsub.pubnub.com&sub=demo&pub=demo&cipher=&ssl=false&secret=sec-c-OWFkNWQ1NDctN2JiNy00NzJmLTk3Y2ItN2ExODZlYzkyNzY0&auth=

The registered network listeners parse the path parameters and look for various path components to figure out what to render...but all of the path components are offset by +1 when using the v2 API.