Deactivating account leaves the account "stuck" in rooms

[brycied00d]

When I setup my own homeserver, I deactivated my matrix.org account. I expected that deactivating the account would be akin to deleting it, including removing the account from the various rooms it's in. Unfortunately, this is not the case, and worse still is that my prior account had power=100 in a couple of rooms so I'm unable to /kick it (having power=100 with my "new" account).

I believe the solution is for the /deactivate endpoint(s) to also "clean up," and for there to be a periodic (or at least one-time) process to clean up deactivated accounts from rooms.

What are the developers' thoughts on this deactivation process?

[brycied00d]

I should add that, had I realized that deactivating the user would leave it "stuck," I would have "cleaned up" myself before deactivating. This speaks to a client usability issue, true, however I believe still that /deactivate should also perform this type of cleanup.

[onePinger]

Not sure if "stuck" addresses this, but when you deactivate your account, enter your password and click on "Deactivate Account", resulting message that the session has been signed out and clicking on "OK" returns you to the deactivate page again.

[tulir]

This seems to have been fixed in #3201