Currently, we do not allow users to close accounts themselves, because we have not implemented deleting accounts automatically on the various connected services, and doing that in a manner appropriate to the respective use cases.
To do
Identify/list which data can be deleted and which has to be preserved (e.g. public comments on Gitea issues and such)
Identify where tombstones may be needed
Decide if it's ever a good idea to free up a username again after account closing. Can be problematic for all of security, privacy, impersonation, etc.
...
Currently, we do not allow users to close accounts themselves, because we have not implemented deleting accounts automatically on the various connected services, and doing that in a manner appropriate to the respective use cases.
### To do
* [ ] Identify/list which data can be deleted and which has to be preserved (e.g. public comments on Gitea issues and such)
* [ ] Identify where tombstones may be needed
* [ ] Decide if it's ever a good idea to free up a username again after account closing. Can be problematic for all of security, privacy, impersonation, etc.
* [ ] ...
Prosody (I wasn't sure which XMPP service we use) has the prosodyctl command which allows adding and deleting users (prosodyctl deluser JID): https://prosody.im/doc/prosodyctl
Gitea, there's a gitea command which can manage users as well. e.g. gitea admin user delete --id 123. It's unclear whether this will remove posts as well, and I wasn't able to find any specific information on that. https://docs.gitea.com/next/administration/command-line
This still leaves the Lightning node, and the Kosmos account itself. Not sure what else?
To help out here I collected Info on deleting accounts for each of the services I knew we served (though I'm guessing about Prosody).
- Mastadon, there's a `tootctl` command: https://github.com/mastodon/mastodon/issues/1175
- Prosody (I wasn't sure which XMPP service we use) has the `prosodyctl` command which allows adding and deleting users (`prosodyctl deluser JID`): https://prosody.im/doc/prosodyctl
- Discourse, enter the `launcher` console and run some commands: https://meta.discourse.org/t/delete-my-account-with-the-console/82450
- MediaWiki, seems like just an SQL command and nothing else: https://www.inmotionhosting.com/support/edu/mediawiki/mediawiki-manage-user-accounts/
- Gitea, there's a `gitea` command which can manage users as well. e.g. `gitea admin user delete --id 123`. It's unclear whether this will remove posts as well, and I wasn't able to find any specific information on that. https://docs.gitea.com/next/administration/command-line
- Drone CI also has a command-line tool `drone user rm [username]`: https://docs.drone.io/cli/user/drone-user-rm/
This still leaves the Lightning node, and the Kosmos account itself. Not sure what else?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently, we do not allow users to close accounts themselves, because we have not implemented deleting accounts automatically on the various connected services, and doing that in a manner appropriate to the respective use cases.
To do
To help out here I collected Info on deleting accounts for each of the services I knew we served (though I'm guessing about Prosody).
tootctlcommand: https://github.com/mastodon/mastodon/issues/1175prosodyctlcommand which allows adding and deleting users (prosodyctl deluser JID): https://prosody.im/doc/prosodyctllauncherconsole and run some commands: https://meta.discourse.org/t/delete-my-account-with-the-console/82450giteacommand which can manage users as well. e.g.gitea admin user delete --id 123. It's unclear whether this will remove posts as well, and I wasn't able to find any specific information on that. https://docs.gitea.com/next/administration/command-linedrone user rm [username]: https://docs.drone.io/cli/user/drone-user-rm/This still leaves the Lightning node, and the Kosmos account itself. Not sure what else?
We're using ejabberd. I looked up the API endpoint:
https://docs.ejabberd.im/developer/ejabberd-api/admin-api/#unregister