Tor connectivity restored!
Unfortunately there are plenty of XMPP clients, which connect via trashserver.net A/AAAA IP address and not via the SRV record. Using Tor can be one cause, since Tor DNS does not support SRV records.
Therefore a redirection for these clients has been created.
Welcome back, Tor users! :-)
I'm sorry for yesterdays service outage from 2018-10-02 8:55 pm [GMT+2] until 2018-10-03 9:34 am [GMT+2].
The server's RAM resources were fully utilized and most processes could not allocate any more memory. This lead to a crash of several services, including XMPP.
Unfortunately I could not handle the situation during night.
Service has been restored this morning.
https://webchat.trashserver.net/ updated to ConverseJS 4.0.1
Compliance status for trashserver.net:
94% Specifications compliant
Since Conversations version 2.2.6 MAM for MUCs is available again! 🎉
Conversations got support for MAM:1. Compatibility with MAM_MUC should be restored in the next version :)
Today I did some analysis of secured connections to trashserver.net.
Here are the results: https://transfer.sh/butgm/tlsresults.txt
The numbers on the right side show the count of connections using a certain TLS version / Cipher.
As you can see, clients announce quite a lot of ciphers/versions, but negotiation makes server and client choose strong encryption mechanisms. :-) (server choosen cipher is, what counts!)
The tool for creating these stats will be published, soon!
This is the information I just extracted from all the XMPP client connections to trashserver.net:
Is the analysis was valid, I can be proud of my users! No TLS < 1.2 used and also almost every client is using a DH (forward secrecy) enabled connection! 🎉
(although this analysis is not really representative because IPv6 connected clients were not considered).
Statusmeldungen zum XMPP-Server trashserver.net
One of the first Mastodon instances, there is no specific topic we're into, just enjoy your time!