jabber.hot-chilli.netOn the new server we activated two new public domains:
Feel free to register accounts. ;-)
In-band registration is open for now (also for the other domains migrated to Prosody already) – and might be changed as soon as possible to our web registration form which has to be changed because of our migration to Prosody.
One of the main reasons we were really looking forward for ejabberd 2.1.6 is the support of captcha for mod_register. This module handles in-band registration, which means the interface where users can register through their client. This interface is also abused by spammers. We hope that the use of captchas will prevent most spam registrations.
If you client does not support captcha you well see a url where you can see the captcha in your browser window.
We noticed that buddies in Jabber roster are now renamed into the original names from the legacy networks, e.g. ICQ or Facebook.
This affects just local transport users as remote roster only works on the same server.
Sorry about that… But now the rosters are synced and renaming the contacts will also rename the contacts in the legacy network roster. If renaming in the legacy network is not supported the databases of Jabber and the transport service are synced anyway.
We just restarted the server to activate Remote roster. What is that?
What’s Remote roster?
Remote roster is protoXEP which allows your server to synchronize legacy network contact list with your users’ rosters. Currently it works only for local users (users registered on the same server which supports this protoXEP). It’s available for Ejabberd 2.1.x and Prosody.
Why should I use it?
It allows to your users following features:
- When they register their account and login for first time, they won’t receive lots of subscribe presences or Roster Item Exchanged stanza. All their legacy network buddies just appear in their roster with proper groups and nicknames.
- When they will unregistering their account, buddies are just removed from their rosters without need of unsubscribing them.
- When they rename some buddy in their Jabber roster, it’s renamed also in legacy network.
- When they move some buddy into different groups, it’s moved also in legacy network.
- All changes made in legacy network when transport is disconnected are synchronized with Jabber account once they become online in Jabber.
Taken from Spectrum website.
With today’s development version of Spectrum the Twitter Transport got upgraded. The package pidgin-twitter is not developed anymore and caused dozens of crashes daily. Spectrum now uses pidgin-microblog instead.
Please delete all old Twitter contacts in your roster, exept twitter.jabber.hot-chilli.net. (Maybe we will delete the old contacts in the near future for our local users.)
Then please allow Spectrum access to your Twitter account. When first connecting to the new Twitter Transport, you will receive the following message from twitter.jabber.hot-chilli.net:
Open following url and send the PIN number from the web page back to Spectrum.
https://api.twitter.com/oauth/authorize?oauth_token=tokenid
Follow these instructions and post the PIN number into the chat window which shows the above message and send it to the transport.
Then approve the authorization request for twitter.com@twitter.jabber.hot-chilli.net.
This contact will post all tweets from your twitter contacts.
If you want to post a tweet to Twitter, just post it into the the chat window of twitter.com@twitter.jabber.hot-chilli.net. Please don’t use more than 140 characters. For more information type:
/help
We just migrated IRC transport to Spectrum. Before it was a core feature of ejabberd, the software we use for the Jabber server itself. Spectrum has more features, so we switched.
If you experience any problems please let us know.
…and it seems to work. Sorry for the 30 minute downtime because of that.
The server was offline this morning because of Kernel and MySQL upgrade. It would have happened faster if the server rebooted cleanly after “shutdown -r now” which it didn’t. So we had to send someone there to reset the machine manually.
We also upgraded Spectrum to support JID escaping. If this works after our tests (there seem to be some problems with clients who don’t support the unofficial % character which is used for @) I write more about this here.