Modern XMPP project discussion - 2026-04-10

One thing I always found strange: Clients have "delete account" instead of logout. The first time it freaked me out as I couldn't find the "logout" button after half an hour an I thought I'd gone mad.

Why is it mostly labelled "delete account" if the account is not deleted, but instead just removed from the client..?

Wdym? Most clients have a toggle to deactivate an account, which is logging out.

> Test icles ↺

> Wdym? Most clients have a toggle to deactivate an account, which is logging out. i think what theyre describing is removing an account from the client ↺

Yeah. Calling it "Deleting" makes it scary, as a user you might believe the account gets deleted.

As that is what it says.

Back then I even created a test account to make sure I wouldn't accidentally delete my main account from the server, which would've been... bad

probably confusion takes place because clients make it too easy to create an account. if you firstly went through the list of servers, then to the server to register one, you'd assume what to delete it you should go to the same place

it was for me like that

Whatever, it should be called "remove account from app" instead of "delete account" if we want it to make sense :D

That's something that would be good as a bug report in affected clients

or

if you had to manually save account to login into it easily, then it would be obvious what delete means ✏

> if you had to manually save account to login into it easily, then it would be obvious what delete means well then make the account login page look like a file browser ↺

> Whatever, it should be called "remove account from app" instead of "delete account" if we want it to make sense :D otherwise i prefer this. Or even "logout" ↺

login by loading credentials.json? :p

Hello, I was able to use migrate.modernxmpp.org to export my user data from chatterboxtown.us to movim.eu. But now, I am trying to migrate data from movim.eu to chatterboxtown.us and I am getting Sorry, we could not connect to the XMPP host with domain: "chatterboxtown.us"

why do you want to migrate back?

chatterboxtown.us isn't a very well managed server and I wouldn't be be surprised if it ended up being blocked or so due to spam issues originating from it.

I'm the admin and I ban every spam report I get. But I only receive spam reports from singpolyma ✏

No one else has contacted me directly

well in that case I strongly recommend to not have open in band registrations as your server is getting used for spam and ban evasion constantly.

little point in even reporting them as it is hit and run all the time.

disposable accounts.

Well I have a lot of JMP users registering in conjunction with JMP.chat so how do you suggest I move forward with that

dunno, discuss with Singpolyma a way to enable invite based registration tokens for JMP.chat users maybe

ejabberd supports that now

Ok. I look into setting that up. But in the meantime you're saying modernxmpp is blocking my domain

no idea, sorry. was just a guess

but migrate.modernxmpp.org is just a webbased client afaik

so there shouldn't be any server side blocks.

maybe a XEP-0156 config issue?

anything in the browser console about websocket connections failing?

but it is odd that you could export with it before

XEP-0156 passes compliance test

I can log in with movim, jsxc, conversejs, app.cheogram.

no errors in the browser console?

None as far as I can tell

Is MattJ the main developer for the migrate tool?

Any references you can point me to a fully working invites configuration for ejabberd? I'm seeing a lot of general instructions about creating a landing page and setting up scripting to run API calls. I'm just not that deep into the coding.

https://joinjabber.org/tutorials/self-hosted/ejabberd/#great-invitations

The current situation is that server migration couldn't transfer user accounts to the new instance. Notifications have been made for users to pre-register their accounts to the new server while it was still in the staging phase. However, there are those that missed the boat and are currently re-registering their accounts. If I implement this, I'm going to end up locking out people who are trying to recover their accounts and have to go through more hoops. As it is, myself and JMP have been receiving support requests for account recovery I'm trying to take most of the burden off of JMP to have to deal with this. This is going to complicate things in the immediate circumstance. Will have to wait for the situation to settle then switch to invite only.

In the meantime, I would like for the community to communicate with me directly about spam issues.

just wait a bit before implementing invites 🤷 ✏

are you in xmpp:operators@muc.xmpp.org?join under an easy to identify name (not "admin" obviously)?

that would help a lot already for communication between server admins for such issues.

No. I'm not a member of the XMPP Standards Foundation which they cite as a requirement.

There must be a misunderstanding, you're not required to be a member to be there

That room is specifically for server operators to share knowledge and issues, it's not about the xsf

says I can join read only, but not an active participant https://xmpp.org/community/channels/operators/

you need to configure your JID as the admin of your server

that is also good for contacting you in general

but if you configure it you get write permission automatically in that channel

Verified only means your jid should be listed as contact address that's all

It was only invited to get the noise down. But it turned out operators can make enough noise alone too

I thought I had that contact info in my server config. Does it not show up?

Also even if you don't list your account you'll be given voice by MattJ likely if they can somehow verify it's you

XEP-0157 passes compliance test

I think the bot is broken that is responsive to give member status, 😀

You'll need to just request it old fashioned

Seems your contact works > contact addresses for chatterboxtown.us are > - abuse-addresses : xmpp:admin@chatterboxtown.us > - admin-addresses : mailto:admin@chatterboxtown.us , xmpp:admin@chatterboxtown.us >

there is something odd with your server. When I try to query contact info via a bot I get: `Could not reach chatterboxtown.us: Server-to-server connection failed: unexpected eof while reading`

Menel, how did you query that info?

Magicbot

xmpp:magicbot@magicbroccoli.de

connected to what kind of server?

my Riddim connected to latest release prosody fails as mentioned above

it works with other servers

ah ok ejabberd 26.01, you need to update 😏

maybe there is some issue with Prosody to chatterboxtown.us communication? That might also explain why the migratior fails.

Indeed. Looks like am s2s bidi issue

https://github.com/processone/ejabberd/issues/4375 I've seen this for some time but never got someone on the ejabberd side to attempt to debug it. A restart on ejabberd did fix it in the past. It's unknown when it appears. Or why.

I'm running ejabberd 26.03

can you try reloading your server?

as in reload not restart

once you do please tell me so that I can check again with the bot

done

hmm, still fails via my bot

> maybe there is some issue with Prosody to chatterboxtown.us communication? That might also explain why the migratior fails. migrate.modernxmpp.org? Has nothing to do with Prosody

I assume some misconfiguration on the chatterboxtown side, but I haven't investigated myself yet