XMPP Service Operators - 2023-06-03


  1. msavoritias

    Hey is the admin of jabbers.one here?

  2. msavoritias

    We have a spam/transphobia problem at the news channel and all the accounts come from there

  3. emus

    huxxer: ^

  4. emus

    ah, you found iy

  5. emus

    ah, you found it

  6. msavoritias

    Yeah the accounts are deleted

  7. msavoritias

    And we put the news channel in moderated mode for now

  8. huxxer

    Yes the Accounts were eliminated

  9. ☭Mike Yellow

    “conference.conversations.im” publishes creater's XMPP user address by default?

  10. Licaon_Kter

    ☭Mike Yellow: where?

  11. Licaon_Kter

    There was a bug in ejabberd, maybe it does not have that fix? Holger

  12. ☭Mike Yellow

    I can see it in Gajim join dialog.

  13. Licaon_Kter

    Ref https://github.com/processone/ejabberd/issues/3609

  14. Licaon_Kter

    Yes, Gajim showed that

  15. ☭Mike Yellow

    Not all ejabberd servers do it.

  16. Licaon_Kter

    Yes, those updated to 21.xx or later won't

  17. ☭Mike Yellow

    Thank you. Maybe I should teach users to use another account as owner for daily management, or teach them to use XEP-0016 when the owners are too famous. (^_^)

  18. moparisthebest

    Why not just teach them to run up to date software? 🤔

  19. ☭Mike Yellow

    > Why not just teach them to run up to date software? 🤔 You mean server software?

  20. savagepeanut

    Found the Arch user ;) Not that I disagree with your solution

  21. moparisthebest

    All software

  22. Licaon_Kter

    savagepeanut: it's not an Arch thing. Even Debian Stable has 22.xx or 23.xx in Backports

  23. moparisthebest

    Or run a container with podman

  24. Licaon_Kter

    iirc conversations.im has a custom patched version so I guess Holger needs to add another patch and restart a beam or smth

  25. moparisthebest

    You can't be running out of date servers on the internet until we can start writing code without bugs, and it ain't looking good :P

  26. ☭Mike Yellow

    > All software We are still working on the XMPP user manual. But my small organization has not plan to study how to build, host, manage server softwares.

  27. ☭Mike Yellow

    We paid much energy to learn and write a manual. We have no the ability to keep the manual up-to-date duly, so we can only choose a specific version to teach.

  28. Licaon_Kter

    While I don't tweak my setup these days, ejabberd is slowly moving compared to prosody let's say, it does need to tend to the stuff around it, sslh, certs, storage, kernel, OS updates, etc.

  29. Licaon_Kter

    You can set and forget but...

  30. ☭Mike Yellow

    Errr... I guess “user” is a ambiguous word here beacause here are client software users and server software users. :P

  31. Brian

    Licaon_Kter: Thankfully, things like certs and Linux updates are a lot easier than they used to be

  32. Licaon_Kter

    You're new here? Certs are the #1 hosters enemy :))

  33. Brian

    Been using Let's Encrypt automated renewal for years... hardly an enemy :-) ]

  34. moparisthebest

    Yea works great until it doesn't

  35. Brian

    I guess I'm one of the lucky many, then

  36. Menel

    It is still easier then before. It fails for some people sometimes isn't a contradiction

  37. ernst.on.tour

    ☭Mike Yellow: > Errr... I guess “user” is a ambiguous word here beacause here are client software users and server software users. > :P You know this is XMPP-Server-Owner-MUC ? Have a look in Chatdetails, MUC is named "XMPP-Service *Operators*" 😉