Allow self-closing of account #120
Open
opened 2023-04-11 09:49:48 +00:00 by raucao
·
2 comments
No Branch/Tag Specified
Labels
Clear labels
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
integration
btcpay
integration
discourse
integration
ejabberd
integration
email
integration
ldap
integration
lndhub
integration
mastodon
integration
nostr
integration
remotestorage
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/akkounts#120
Reference in New Issue
Block a user
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