Did a test installation with MongooseIM. Testing with Monal. This doesn’t look good at all. I wonder what’s going on here, since some of the missing features are definitely there. Wrong version of the XEP implementations?
Now I wonder if it’d be worth spending time on this and work towards better compliance for MongooseIM.
Is there a community interest in having one more server option?
Planned for future releases:
* support Roster Pre-Approval to further smoothen UX
* manage invites from your web-admin interface
* stand-alone page for creating invites using your account credentials (in case your client doesn’t support that)
* create invite token URIs for password-resets
* accessibility improvements to landing pages
Outside the scope of ejabberd:
* create a guide on how to create invites for a selected set of clients.
* Port to MongooseIM.
I still very much think #xmpp is pretty darn good. Development on the IM standard has kept going. Even after the corps came in and gobbled mindshare for it. 😡 The protocol is still powerful and can actually support mobile usage. 📱
Servers have gotten considerably better. Hell #MongooseIM 6 has #GraphQL api now.🤯
What I'm saying, don't take #matrix as the only alternative we have to the proprietary ones.
Next we have Accessible Time-Series data with TimescaleDB and Building blocks and how to use them: a MongooseIM case study. Did you know that #MongooseIM can utilise the resources of multiple clustered machines, and easily scales for more capacity by simply adding a box or a VM?
🐦🔗: https://twitter.com/CodeBEAMio/status/1588249044534468608
“Next we have Accessible Time-Series data with TimescaleDB and Building blocks and how to use them: a MongooseIM case study. Did you know that #MongooseIM can utilise the resources of multiple clustered machines, and easily scales for more capacity by simply adding a box or a VM?”
PositivDenken 🤯
Neustradamus :xmpp: :linux:
Ailuridae
Alejandro Baez
Chris Engelbert / noctarius