Refactor ejabberd API integration #226
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
No labels
kredits-1
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/akkounts#226
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.
This is pure grunt work to eliminate future technical debt, except for adding content types when fetching ejabberd avatars, so they could be imported to our storage later (relevant for ejabberd-only to akkounts+ejabberd migrations, or if we want to import the rest of the avatars from XMPP users who aren't Mastodon users).
It makes everything consistent with the other REST API integrations, inherits from the same REST service, and decouples the XMPP jobs from the specific ejabberd implementation. So if one adds e.g. Prosody support, it's easy to just call a different integration service.
Looking good 👍