A friendly reminder for new users: LW.Org offers its users a Public jabber/xmpp service which you can register an account for here. After you registered you can access it through our web client (Jappix a great opensource web app by the PostPro association) at im.lightwitch.org which is on the site's primary links menu.

Or if you have a stand alone client of your own you can access the service by pointing it to lightwitch.org after you registered an account.

If you want to only access our web groupchats you can from now access 'em from: webchat.lightwitch.org

Due to an issue in the server code, there have been several hang ups and restarts in the past two days. Which I'm sorry for but it wasn't exactly immediatly evident where the culprit was and it took time to debug.

The good news is that this allowed also several optimizations which should lighten up and make the server a little more faster even.

Sorry for the inconvenience,
Mar.

Attention! Revs of Metronome ranging from 17ba511e2fbf to a0233739ebbf are NOT to be used, the stanza util tag mapping function did cause the software to freeze if the xml stanza contained choppy newlines between elements.

That was fixed in version 1.8.20 (8450de74542b)

EDIT: This was changed to reflect the real bug.

Even if it was discussed as a possibility in the past, given the recent comments (and rumors) on the net I thought it was going to be more of a merging, of Prosody 0.9 plus Metronome's Pubsub API.

I admittedly was sort of caught by surprise myself when I was asked by Val, but none the less I'm very happy that people are satisfied by a piece of "0 and 1s" to which I dedicated several months almost endlessly, and finally that Metronome simply out performed ejabberd on jappix.com by a large margin, expecially pubsub and pep wise, with the same amount of load, dumping a few stats:

ejabberd on 32 bits Arch ->

• CPU load: Around 50-60% average
• RAM usage: From 600-700 MiBs to peaks of 1GiBs. (with 250+ c2s connections average, and 1 or 2 hundreds or so s2s connections)

Metronome on 32 bits Arch ->

Our upstream provider informed us, that they will start a maintenance on the server physical machine/s beginning at 11:00am UTC and possibly ending within or before 11:55am UTC of the above mentioned day.

Both all the LW.Org hosted site/s and xmpp services will be down during that time window.
Sorry for the inconvenience.

UPDATE: We have been informed that the planned maintenance has been cancelled.

To perform the cyclic operating system software updates on Storm, I will be bringing down the server at around midnite CET of the specified day.

As it's just a reboot, the downtine should be minimal.
Sorry for the inconvenience.

EDIT: Due to personal issues, the machine reboot was rescheduled today (11th) at 1:48 am CET.

To resolve a few outstanding issues within the server software socket & tls managing stack, some on-the-fly tweaking (which also lead to a minimal downtime which lasted around 15 mins) and patching was necessary this required some restarts as it's not a reloadable part of the software.

Sorry for the troubles.

EDIT: More work was necessary to address a possible vulnerability in the roster manager, timeframe of "troubles" was around 6:20~7:00 am GMT +2:00 of the 6th of April. Maintenancing is fully complete now.

For most of the day I have been conducting some work on the server s2s bits regarding federation interoperability, unluckily that has been more trial & error then usual and ended in heavily affecting s2s connectivity today (and some service restarts). I'm working on saving for a more proper test environment or at least some software instancing but until then that's all a person "doing a 10 men work" can do.

Sorry for the trouble but I'm confident the service has improved a bit today.

52 accounts which met the following inactivity criterias were deleted:

1. Last login versus Time of registration
2. Roster size
3. Auxiliary Bayesian checks

Best regards,
The Administration.

Completed minor maintenance to the XMPP related systems,

1. Minor bug fix to the site registration form
2. Minor bug fix to the server registration system
3. Restarting xmpp server to clean out its enviroment from eventual layovers

Downtime should have been minimal, sorry for the inconvenience.