Mike wrote <<< Thanks for pointing this out! When websocket support is ready on the ephemeric gate I'll add a ping to API server so application will work continuously without any effort. I think conceptually it should "just work". Also I plan to have a "sticky-run" option so you can mark some of ephemerics not to go to sleep mode. What do you think?

...

...

That sounds like a good approach. Just to dig into this a bit more, here is our first use case. We have an iPhone/web app which is a multiuser countdown timer. The data are hosted on Firebase. The iPhone app can set the time, and control start/pause. The web apps count down by themselves, but the start/stop/reset signalling is done in real time by the Firebase server. So, if you imagine a timer that is set to run for 45 minutes, we would need to signal start to the image. That would be reflected to all connected clients via wss, and then, for example, stopped with 5 minutes to go. We would need the app to remain live whilst a timer was running. However, we don't use the timers all the time, so keeping the whole app live might burn up more of the server's resources than necessary. Cheers Andy