XMPP Service Operators - 2022-10-30

heads up, User zek <romu754@conversations.im> spambot repeatily connecting to my server

pattern:

Ищу работу

repeating over and over again randomly between 10 seconds and 8 minutes

> xmpp.net is dead, long live inspect.xmpp.net :) This doesn't work for me or my server. The test doesn't give any information. The old version worked fine.

etaurus: you may need to manually refresh the page later

Because something runs in the background?

yeah

Ah, you are right. Something is happening.

the page needs a bit of polish in that regard :)

or a bit of javascript...

Contributions are welcome :)

The intention was to keep the old IM Observatory running a bit longer, but I upgraded the system it runs on the other day, and for some reason it's not running

It will come back if we work it out

> It will come back if we work it out oh no

I didn't want to shut it down until some of the minor UI issues in testxmpp have been fixed, and we also have a replacement for the xmpp.net badges

But maybe that's what I'm doing today

I have so many things I'm doing in so many terminals at the moment, I can't even remember them all

Does anyone know a server with a website that had an xmpp.net badge?

MattJ: https://www.jabber.de

Thanks!

np. and, name your terminal tabs!

I try. I try :)

or maybe that should be "Probably T"

If they have a badge, it's A. So just give everyone with a badge an A... Otherwise they wouldn't include it anyway 🙂

exactly

although it probably degrades to T automatically while they're not watching

_" *A* today, expired cert tomorrow"_

is there a list of all these sites? like search, inspect, connect

🤔️ needs an index.xmpp.net?

or, a better place for it is xmpp.net itself :)

So many sites link to xmpp.net as tester, so better forward to i.x.n

i being inspect, not index. 😉

the redirect can be non-machine-readablie, methinks. just a piece of text at the top, with the link to i.x.n

Okay, the Observatory is officially gone

I've put up a static badge for now, so *omething* will appear for anyone that previously embedded them, and everything else goes to a static page explaining things

the update actually put it out of its misery? :)

A bit sooner than planned, but yeah

I'd planned to maybe turn it off around the end of the year

> the update actually put it out of its misery? :) Update? OS?

Yes, just an apt upgrade and a reboot

I don't know what the problem is exactly, it might have been an easy fix

So not a dist-upgrade?

But since I was going to turn it off anyway and I don't have much time to go digging through the tangle of code and containers and config, it was easier to just work on turning it off now

No

Then it's not normal if something breaks.

But it's days were counted anyway.

You're welcome to assist with debugging if you want it back :)

But believe me, I wouldn't recommend it

I don't think it makes much sense to spend time on the old thing.

Exactly

The king is dead. Long live the king!

For inspect: No matter how long I wait and how often I reload. I always see: > TLS > The TLS scan has not been scheduled.

Now it works out of a sudden. It just waited until I complain.

Mean software. 😂

https://github.com/horazont/testxmpp/issues/3

👍🏽

I also still have to file a feature request for alpn.

Does the bosh and websocket test work for somebody at inspect.xmpp.net or is it not yet implemented? I always get the result of error, though both should work fine, as conversejs can use them successfully ✏

What are you expecting to happen for it to "work" ?

Oh, didn't know it did tests against those endpoints

raver: mine says error too

moparisthebest: thx, so I guess still work in progress🙃

Definitely a work in progress

Establishing a secure connection from lebihan.pl to muc.poez.io failed. Certificate hash: db56ac68a00242be96d9c22d132f066ab9e8cd1c2033f0d9cdc36e5747b4fd3d. Error with certificate 0: certificate has expired.