i've been trying to get that out of a iOS/Android dev for quite some time. they wont load sounds until a user interaction is made, but they will load images (which are a lot larger in most instances than sound are). there are a lot of things that are done "weird" in the mobile OS's, for odd reasons.
Well that is indeed a bit surprising. I would guess its to optimize the resource usage. Which makes sense. But how are websockets supposed to work then
I have around 65% of the users using mobile devices (Chrome Mobile and Safari Mobile). So the chat tab being "suspended" seems quite likely. Anyway. I'll wait for an update
the problem is with the way i did it, the error became apparent after some testing. I am gonna have to think of a better way to do it (as the one for 3 was similar with a few tweaks). there is a update function in the JS that is suppose to send out a "keep alive" signal to the node that then gets sent out everyone else (as each user maintains the online list for their instance), and if you don't get that "keep" alive, it will remove them after 5 minutes.
so what is happening you are not always getting or sending the keep alive (some OS's and devices will freeze interval functions of JS when the page isn't focused or when you are scrolling on the page, which is weird, but it is what it is). so what i might do is reverse it, have the node that ask for a keep alive notice from the user, instead of the user sending it to node. this way it will avoid the above mentioned scenario of some OS's doing stupid things
Any news on this subject? Or is the goal to rather wait for v3? If so I would hope that is ready before IPS retires its service
We have switched back to the IPS chat for now because it was to confusing.
I remember having a little struggle getting Node.js and forever installed on CentOS... wish I kept a step-by-step so that you could add that to the tutorial.
https://nodejs.org/en/download/package-manager/#enterprise-linux-and-fedora Is pretty good though.