Most chat systems have done away with it. Slack has it, but that's about it. For anything you use from your phone, what does it even mean?
Slack, Discord, Matrix, FB Messenger, Instagram all have it to name a few.
The only ones that don't have it are SMS replacement apps (Whatsapp, Signal) and IRC.
I for one greatly rely on presence. It very often informs if I should or should not send a message to someone.
Do you have an example? I certainly don’t operate this way. I just fire off a message. The status only informs my expectation of when a reply might arrive.
In the absence of a status I have no expectation of a reply. With mobile devices I still get immediate replies frequently because of notifications. So I don’t rely on status.
i.e. basically every corporate chat system
I do keep wondering though what's the deal with the performance of the Matrix protocol. From reading the overview in the spec, it doesn't feel like there's anything that could have a significant performance cost. It's essentially a standardized but extensible REST API that passes JSON objects over HTTP. Is it that the existing server implementations aren't optimized very well?
The reason there is stuff to optimise is that Matrix passes JSON around over HTTP in a byzantine fault tolerant manner: every time you send an event you have to sign it and justify why you’re allowed to send it, and every time you receive one you need to execute that proof effectively and do a merge resolution algorithm to authenticate the event and store it in the right context - very similar to how Git works, but with events rather than commits. A naive implementation of this can be very heavy. We’ve improved it by 3-4x over the last year or so, and there are other big algorithmic improvements in general on the horizon too.
So you d have an enormous graph with one node in the center refreshing presence for everyone. And end up worse.