Snikket Server - Your own messaging server in a box

[djxx]

@jdaviescoates What it requires is that your username matches the TLD it is deployed to, which means it needs to be installed as the "root" application on that domain. This is incompatible with Cloudron, and frankly with how many organizations operate. It's very common to have XMPP installed somewhere like xmpp.domain.com , and the protocol supports configuration to use the TLD for accounts. This is one of the areas where Snikket is firmly standing by "it should be so simple and require no configuration" - so either you install it at the root or you live with ugly usernames like user@xmpp.domain.com.

I don't think it's worth the time to customize something that doesn't want to be customized - but rather use something that is meant to be configured and come up with sane defaults that fit Cloudron. That's what I've tried to do with my Prosody packaging.

[robi]

Maybe it's a simple thing to adjust in the code and have a fork.

Then there is the maintenance issue.

[djxx]

@robi said in Snikket Server - Your own messaging server in a box:

Maybe it's a simple thing to adjust in the code and have a fork.

Then there is the maintenance issue.

Yes, the maintenance would be quite an issue. I guess Snikket will put 0 effort into not breaking customizations they told people not to make in the first place.

Prosody (and ejabberd) take care to be backwards compatible with older configurations, and follow a well-documented deprecation process when they're going to make breaking changes.

[jdaviescoates]

Thanks for explaining. A shame as I liked the sound of Snikket (and it's by one of the lead devs of Prosody, I think)

[robi]

@jdaviescoates can you ping him and ask how hard the upkeep would be for a new fork the way we need it?

Perhaps call it Snicketteer