XMPP Service Operators - 2018-11-26

  1. Neustradamus

    Who manages https://check.messaging.one/ ?

  2. Holger

    I do.

  3. Holger

    No I can't fix it.

  4. Neustradamus

    Why a redirection to broken xmpp.net? :/

  5. Holger

    I can remove the redirection if you think that helps anyone.

  6. Neustradamus

    For use the service on https://check.messaging.one/ yes with an updated code too :)

  7. Holger

    I can't fix it, as I said.

  8. Holger

    If you can, I'll redirect to your site.

  9. Holger

    I could also give you SSH access to fix my instance.

  10. Neustradamus

    Previously you have not launched your service?

  11. Holger

    I launched it back when xmpp.net was completely down, then check.messaging.one broke for unknown reasons, and I gave up on it.

  12. Neustradamus

    :'(

  13. Neustradamus

    And no change from Jonas... https://github.com/horazont/xmppoke-frontend-docker/issues

  14. Holger

    And no change from you :-)

  15. Neustradamus

    Why I can do? I have not rights to resolve it... No support for xmpp.org/net and same for jabber.org.

  16. Neustradamus

    Tickets here: - https://github.com/stpeter/jabberdotorg/issues - https://github.com/xsf/xmpp.org/issues - https://github.com/horazont/xmppoke-frontend-docker/issues

  17. Holger

    You could use a different domain, like I did.

  18. Neustradamus

    https://github.com/stpeter/jabberdotorg/issues/1

  19. Holger

    And I guess the xmpp.net guys will be interested in fixes.

  20. Neustradamus

    We can create a new service yes

  21. Neustradamus

    I have created tickets for have a trace, because without ticket no solution.

  22. Holger

    My point is, this is not about domain names or SSH access or the XSF or whatever. It's simply about nobody having the necessary time/motivation to fix it right now. Obviously, you don't have it either. That's fine, but you won't change that by bugging others to do the work.