XMPP Service Operators - 2018-11-26

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

I do.

No I can't fix it.

Why a redirection to broken xmpp.net? :/

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

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

I can't fix it, as I said.

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

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

Previously you have not launched your service?

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

:'(

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

And no change from you :-)

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

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

You could use a different domain, like I did.

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

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

We can create a new service yes

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

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.