Categories
Features Transports

Remote roster feature renames buddies in Jabber roster

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.

Categories
Features Transports

Remote roster

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.

Categories
Features How-to's Transports

Twitter Transport upgraded

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

Categories
Features Transports

IRC transport migrated to Spectrum

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.

Categories
Downtimes Features Maintenance

Pubsub/PEP migration to MySQL complete

…and it seems to work. Sorry for the 30 minute downtime because of that.

Categories
Downtimes Features Maintenance Transports

Server offline due to maintenance work this morning

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.

Categories
Features

New public domains added

Last night we added two new public domains to the Jabber server:

  • jabber-hosting.de
  • xmpp-hosting.de
Categories
Downtimes Features Maintenance

Proper certificates for secondary domains

To avoid login errors or messages and also to avoid certain problems with server-to-server connections we installed proper certificates for the secondary domains today.

We had to restart the Jabber services several times, sorry. The ejabberd config file isn’t commented very good, also Google didn’t tell us the correct settings in the first place. But everything works fine now.

PS: For old SSL connections to port 5223 there are no dynamic certificates. This just isn’t possible because of how SSL works.