jabber.developer2
61a5de6ab9
Two gaps kept /omemo gen from ever publishing on a fresh account: - _omemo_receive_devicelist() only recognised the legacy code='404' error attribute as "node does not exist". Prosody sends the RFC 6120 <item-not-found/> condition instead, so the empty-list bootstrap never ran. Accept the defined condition too, and log the expected bootstrap case at debug instead of error. - connection_request_features() disco'd only the server domain, but XEP-0163 PEP services (including pubsub#publish-options) announce their features on the account's bare JID. Query the bare JID as well, registering it in the feature table, so connection_supports() sees PEP features. Fixes #169
CProof
CProof is a console based XMPP chat client based on Profanity.
See the Quick Start Guide for information on installing and using CProof.
Project
CProof enables you to communicate with privacy, freedom and comfort. Our open-source chat application delivers secure, end-to-end encrypted messaging (OTR, PGP, OMEMO, OX) built on the trusted XMPP protocol. With a decentralized design, you can connect directly or even host your own server, keeping your data in your hands. Whether you're chatting with friends or collaborating securely, CProof makes private communication simple, reliable, and truly yours.
Installation
Check our installation guide for detailed instructions.
How to contribute
See our Helping Out page for a concise summary of ways to help us.
Review the Contributing Guide and Code Overview pages for advanced technical details.
Getting help
Prior to asking questions, check our User Guide, then check out the FAQ.
If you are still having a problem then search the issue tracker.
As a last resort, feel free to write us on support@jabber.tech or create a new issue depending on what your problem is.
Links
Website
Feel free to visit our website: jabber.space.
You may also check the repository if you like, available on git.jabber.space/devs/profanity.
Plugins
Plugins repository: https://git.jabber.space/devs/cproof-plugins