Websockets are a better suited abstraction for long running chats. It will greatly simplify the server API to relegate all the messaging to sockets rather than requiring polling of various endpoints with queues of messages.
The concern with websockets is that they will require JS to use in the browser which is slightly limiting for tor browser users. However, the primary use case is to use a dedicated client. Additionally, there is the possibility of having a non-websocket api added back in for nonJS web usage if needed. That's still a dubious use-case, as it would also restrict the ability to use additional encryption and verification making proxying chat servers to spy on users nearly trivial.
Websockets are a better suited abstraction for long running chats. It will greatly simplify the server API to relegate all the messaging to sockets rather than requiring polling of various endpoints with queues of messages.
The concern with websockets is that they will require JS to use in the browser which is slightly limiting for tor browser users. However, the primary use case is to use a dedicated client. Additionally, there is the possibility of having a non-websocket api added back in for nonJS web usage if needed. That's still a dubious use-case, as it would also restrict the ability to use additional encryption and verification making proxying chat servers to spy on users nearly trivial.