Home » Blog
Our jabber server certificate is currently expired.
Unfortunately this expiration date was not correctly set in our schedule and hits us now in a time where Roi is in his well-deserved vacation.
He will update the certificate next week once he is back.
Sorry for all the inconvenience.
We just upgraded ejabberd to 2.1.10. Therefore the service was down for some minutes. Everything should be up and running again.
Do you want to contribute with content or content translation?
Unfortunally we don’t have as much time as we wish to have and also we don’t speak all the languages in which we want to offer this website. We are happy about any help you can offer us. 
The deletion of inactive users from the Jabber server and all Spectrum based transports will take today or tomorrow.
We will delete all users who did not login one year or longer. Also we will delete all users who did not login after the creation of their accounts. This could also affect users who did register less than a year ago. So if you registered and did not login since then you have to reregister again.
Again, we have an exclude list. If you want to have your account on the exclude list, contact us and tell us why.
To show why we will clear up the databases here some statistics:
We just picked out the big players on our server for this blog article.
The first number are total users, the second number are the users, who did not login within the last 365 days.
The only service with mostly active users seems to be the Facebook Transport.
In the next days we will implement script to delete inactive users from our databases (Jabber server and Transport services). Most users in our databases are inactive so we want to get rid of them. This reduces the overhead and leads to better usage statistics. Also it is freeing up usernames which can be registered again by new users.
There will be an exclude list. If you think your username should be on the exclude list, please get in touch with us and tell us why.
As soon as the deletion jobs are ready to run the first time we will announce this about a day in advance.
We just blocked Nimbuzz traffic via our iptables firewall. At the moment this is just a test, but maybe we will block Nimbuzz for good.
The system has way too much CPU and memory usage and is not running stable. We have to do something about it. If it means that we have to block out Nimbuzz as there is no other way, then it is has to be the solution.
At the moment we don’t have any idea why. As I am in Italy right now I will investigate this after my return home in the middle of the week. Please stay tuned.
Is anybody aware of any current exploits for ejabberd?
English 
Deutsch 
polski 
Русский 
roi@jabber.hot-chilli.net
beorn@jabber.hot-chilli.net