At the moment, the server starts sending updates on the /api/kansa/people/updates WebSocket as soon as it's operational, which e.g. kansa/admin applies to the data it received from GET /api/kansa/people. If an update happens in that interval, it's not reflected in the client state. Adding support for a ?since=[timestamp] query parameter to the WebSocket could help make sure any such updates can be sent to the client when the socket is initially opened.
At the moment, the server starts sending updates on the
/api/kansa/people/updatesWebSocket as soon as it's operational, which e.g. kansa/admin applies to the data it received fromGET /api/kansa/people. If an update happens in that interval, it's not reflected in the client state. Adding support for a?since=[timestamp]query parameter to the WebSocket could help make sure any such updates can be sent to the client when the socket is initially opened.