> Live presence was switched off. As more users came on board, the load from live presence (the real-time “online/away” indicator) started to affect performance, so the team disabled it.
im taken back to my AIM days; imagining someone setting up special alert sounds for when their favorite official comes online
This seems surprising to me. I think live presence is an essential part of real time communication, but also something that should be well understood how to scale?
i could see how after 10k users, the logarithmically? growing time/resource pressure of checking more users against every list, without properly distributing the data / sharding, starts to creep in
loading story #50559422
Indeed, this seems like a really low number for when to run into issues, unless they're running it on a shared VPS and/or it's just not very well built.
It's an asynchronous protocol, the need for someone to be visibly online is your own.
Send me a message, I'll get back to it when I'm online.
loading story #50560253
loading story #50559983
I mean, if the user names and the messages themselves are cached and displayed, why can't user location be done the same way every ~5-10min or so, or ~1m with an active direct user-to-user (with approval) lookup? it's an exchange of two ~6-10 digit grids and an elevation, I'll give allowance for a timestamp.
loading story #50561183