Describe the problem
Especially on mobile, I need to frequently select my desired space and room when the app relaunches. The app unloads several times throughout the day. It is a daily annoyance to have to click two buttons to get back to my last conversation.
Describe the solution you'd like
It would be nice if Sable saved the last space and room that you are in, and when the app relaunches, returned to the room (unless kicked or left or otherwise not available).
Alternatives considered
A possible option would be to have an option for a "default space/room" that you always go to on launch, but this feels less intuitive and would require more UI.
Additional context
It was mentioned in the chat that depending on the content of some rooms, they might crash Sable, which could result in a softlock if Sable kept trying to open the same broken room.
To get around this, I suggested that perhaps a "graceful shutdown" flag could be added. The saved room/space could be ignored if the last run of Sable resulted in a crash. This is perhaps less viable on the Web client, however.
It would be fine to me if this functionality was only for the mobile and desktop apps, if that was a constraint. My nr 1 use case is on mobile, as on desktop I can leave the app running longer.
Describe the problem
Especially on mobile, I need to frequently select my desired space and room when the app relaunches. The app unloads several times throughout the day. It is a daily annoyance to have to click two buttons to get back to my last conversation.
Describe the solution you'd like
It would be nice if Sable saved the last space and room that you are in, and when the app relaunches, returned to the room (unless kicked or left or otherwise not available).
Alternatives considered
A possible option would be to have an option for a "default space/room" that you always go to on launch, but this feels less intuitive and would require more UI.
Additional context
It was mentioned in the chat that depending on the content of some rooms, they might crash Sable, which could result in a softlock if Sable kept trying to open the same broken room.
To get around this, I suggested that perhaps a "graceful shutdown" flag could be added. The saved room/space could be ignored if the last run of Sable resulted in a crash. This is perhaps less viable on the Web client, however.
It would be fine to me if this functionality was only for the mobile and desktop apps, if that was a constraint. My nr 1 use case is on mobile, as on desktop I can leave the app running longer.