Hi Am 13.01.2017 um 00:31 schrieb James Valleroy: > Package: ejabberd > Severity: wishlist > > I found that there are some XEPs that are not currently enabled by > default, but recommended by https://github.com/iNPUTmice/ComplianceTester: > > XEP-0237: Roster Versioning (mod_roster) > XEP-0313: Message Archive Management (mod_mam) > XEP-0363: HTTP File Upload (mod_http_upload) > > The Conversations client on Android can make use of these features. > > Can these be enabled by default in the ejabberd config? I think that > would help to promote the use of these features that allow XMPP to > compete against other mobile chat services.
It's easily done, though a little late for the freeze as I don't intend to upload a new revision just for that. However, I would only do it for mod_roster, as we strive not to deviate too much from the upstream default. Quoting Holger from https://github.com/processone/ejabberd/issues/1368: 'I don't think they should all be enabled "out of the box", though. Things such as the MAM and HTTP(S) upload setup should be done consciously by the admin, due to their specific requirements and privacy implications.' And I wholeheartedly agree. Furthermore you might unexpectedly run into the 2GB limit of mnesia tables when not setting up MAM with an SQL backend. Similarly, a root partition could be filled up through HTTP(S) upload if the admin is unaware of it. Regards, -- .''`. Philipp Huebner <[email protected]> : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `-
signature.asc
Description: OpenPGP digital signature
