-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass XMPP Compliance Suites 2022 test #1832
Labels
Comments
Reopen #643? |
Once the compliance test is passed, the Profanity deserves official 1.0 release. XMPP Core ComplianceBasic
Advanced
IM ComplianceBasic
Advanced
XMPP Web ComplianceBasic
Advanced
Mobile ComplianceBasicAdvancedAudio/Video (A/V) Calling ComplianceBasic
Advanced |
Thanks for creating the overview!
This will be done only when MUC MAM is finished as well.
This report is crated through our doap file in our repo ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On https://xmpp.org/software/ they list the compliance of clients.
We can see that Profanity is recognition of:
Where as poezio, for example, is only missing:
We need to check XEP-0459: XMPP Compliance Suites 2022 and make a list here with the requirements that we are missing.
It could also be that we just didn't mention something that we actually support in our doap file.
The overview on the xmpp.org website is generated by comparing this file against the Compliance Suite.
The text was updated successfully, but these errors were encountered: