sapphire-backend issueshttps://gitlab.freedesktop.org/alyssa/sapphire-backend/-/issues2023-03-16T14:13:31Zhttps://gitlab.freedesktop.org/alyssa/sapphire-backend/-/issues/3"joined" events don't always get emitted2023-03-16T14:13:31ZFlorrie"joined" events don't always get emittedIn order for the frontend to display the multi-user chat's user list, it must receive the list of users from a `{"op": "joined"}` event. Typically, the backend sends this data in response to an `{"op": "joinChat"}` event. However, it doe...In order for the frontend to display the multi-user chat's user list, it must receive the list of users from a `{"op": "joined"}` event. Typically, the backend sends this data in response to an `{"op": "joinChat"}` event. However, it does not respond with that if the chat was already joined, according to `id_to_joined`. (This happens for chats in non-deferred services, for example the `sapphire` XMPP chat.) So as a solution, the `{"op": "joined"}` event should *always* be sent in response to `joinChat`, even if nothing actually changed on the backend.
(Aside: I noticed the `{"op": "joined"}` event can also be emitted by a buddy joining, and then it sends *just* the new user, not the full updated user list... do we have a corresponding event `{"op": "left"}` event, for when users leave the chat?)https://gitlab.freedesktop.org/alyssa/sapphire-backend/-/issues/2Proper support for resurrecting instances2018-12-27T01:11:56ZAlyssa RosenzweigProper support for resurrecting instancesRight now, if either the proxy or the instance crashes, it's prohibitively difficult to get it back alive without also restarting the other one. We need to support 'resurrection', so to speak -- raising a crashed instance/proxy back from...Right now, if either the proxy or the instance crashes, it's prohibitively difficult to get it back alive without also restarting the other one. We need to support 'resurrection', so to speak -- raising a crashed instance/proxy back from the dead with minimal disruption.
See !1https://gitlab.freedesktop.org/alyssa/sapphire-backend/-/issues/1Presence (status)2023-03-16T14:13:19ZAlyssa RosenzweigPresence (status)Right now, we're always idle. We should track presence correctly, setting idle time accordingly and going invisible when we're ghosted.Right now, we're always idle. We should track presence correctly, setting idle time accordingly and going invisible when we're ghosted.