jdev - 2022-02-20

https://upload.magicbroccoli.de/a11cd1c5c3316374c6cd412dcf2dff134e54e8d1/V7nvA99ygvOnzMM80QTDhPy1d9IwdlCUWUuMXGHR/PGzqe96HQCidoxJkJY8Zrw.pdf

^ Client Comparison Chart update

https://upload.magicbroccoli.de/a11cd1c5c3316374c6cd412dcf2dff134e54e8d1/yCjX3eEyb6cmUN52LIH0FXdWCj3uRnsaJ7cugQId/xep_status_graph2.png

👍️

kikuchiyo, What's with all those question marks for Dino?

Dino is very questionable

larma: dinos doap doesn't have a status value for those xeps, but mentions them

Therefore it's unknown if these features are fully implemented, if so there should be _complete_ flag

This is version 0.5 it's still a little buggy and I forgot some clients with existing doap file.

kikuchiyo, really nice work! maybe consider a simple webapp to make filtering and reviewing easier? 1. allow the user to filter clients by OS 2. then/and/or allow the user to filter by XEP

The chart is mostly meant to help the jdev community and XSF members. linkmauve is doing something similar: https://linkmauve.fr/extensions/

https://github.com/xsf/xeps

kikuchiyo, I guess the status complete is very often a lie if present. For example, afaik all on the list except Dino don't support XEP-0167 § 7 Negotiation of SRTP <https://xmpp.org/extensions/xep-0167.html#srtp>. But I can go through the Dino doap and put complete or partial in there as I see fit.

But does complete mean it follows every MUST or literally the whole XEP?

XEPs that have service discovery typically have a phrase like "if supported, MUST/SHOULD be announced via service discovery". This means that if you don't support it, you just don't announce it and then are fully compliant with the XEP, because you follow all its rules for the case when not supporting the feature? 😀 ✏

I'd say complete means really all features of the XEP, not only a subset of it, because some features are only SHOULD. But even then, if you support, e.g. parsing all of a vCard, do you completely support it if you don't display all of it to the user?

I mean, in the end this is for other developers to know which clients did implement the XEP already. If I want to find another client for testing SRTP and the doap claims "complete" without supporting SRTP, how does it help? How do I find the clients that actually do support SRTP?

larma: you can use _partial_ that would have helped parsing it into my chart.

I just put partial for pretty much all things I implement, unless I'm confident I'll never need to touch that code again

larma: Yes, it would great to have a status. We can improve the wording once this has been more established