You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now creating a new Matrix sender will generate a new access token which also adds a new device to the user's account on the homeserver.
The issue is that given enough time, the homeserver will fill up with these unnecessary sessions and they are difficult to clean up because matrix clients get really slow when there are so many sessions to display and the only way would be to logout all sessions which is inconvenient.
Some potential solutions could be:
Add a way to log in using an access token instead of the login and the password to the matrix:// URL along with a mechanism to refresh them on a soft logout
Call POST /_matrix/client/v3/logout to invalidate the access token and remove the device from the account when the access token is no longer being used
The text was updated successfully, but these errors were encountered:
had it running for a few months and didn't notice, 60.000 sessions were created. If anybody else has the problem that you can't delete them anymore because your matrix client gets overwhelmed. You can clear out all sessions using the matrix API. I used the python-matrix-io wrapper and its client.devices() and client.delete_devices() to clear them out.
Right now creating a new Matrix sender will generate a new access token which also adds a new device to the user's account on the homeserver.
The issue is that given enough time, the homeserver will fill up with these unnecessary sessions and they are difficult to clean up because matrix clients get really slow when there are so many sessions to display and the only way would be to logout all sessions which is inconvenient.
Some potential solutions could be:
matrix://
URL along with a mechanism to refresh them on a soft logoutPOST /_matrix/client/v3/logout
to invalidate the access token and remove the device from the account when the access token is no longer being usedThe text was updated successfully, but these errors were encountered: