XSF Discussion - 2023-04-11

I am not sure if this is the right place to ask. Please let me know if it is. Anyway, does there exist any XEP for creating polls for group chats?

Abdul, yes this is the right place. I’m not aware of any. depending on what you want to build you might be able to reuse reactions (simple up/down votes) or build something new with data-forms

Abdul: https://xmpp.org/extensions/xep-0004.html https://xmpp.org/extensions/xep-0444.html

> Daniel: > Abdul, yes this is the right place. I’m not aware of any. depending on what you want to build you might be able to reuse reactions (simple up/down votes) or build something new with data-forms I was enquiring because I was going to request for creating polls in Conversations and monocles chat. But reactions are a good way to poll. Anyway, I have no background in programming.

search for reference implementations via https://xmpp.org/software/software-comparison/

ok

tmolitor: > Upgrade task names SHOULD have a prefix of "UPGR-" (to distinguish them from "normal" SASL mechanisms) Is there a technical reason for that? From reading the XEP the upgrade task name is always inside an <upgrade> element, so no confusion is possible, and to me, `<upgrade xmlns='urn:xmpp:sasl:upgrade:0'>SCRAM-SHA-512</upgrade>` has a more natural flow

plus, you don't overload IANA registry territory

*Elbe-Sprint Hamburg 2023* Dear developers & community, I am communicating this already, but I still need to get a final confirmation. So if you can please wait with bookings, but feel free to sign up. If you want to join, but don't got a wiki account ask me or others for a favor to do so (atm better ask others, as I am traveling 🙏) https://wiki.xmpp.org/web/Sprints/2023-06_Elbe-Sprint_Hamburg https://jabbers.one:5281/file_share/RD3geQ-OCYRKE1_6I0Hzweoe/elbe-sprint.png

The mailing lists, they're alive!

🧟‍♂️

That's a good thing. Thanks to the people involved!

🎉🎉

theTedd, was it implied that it's ok for me to do https://github.com/xsf/xeps/pull/1282 ? (because I just did)

Ge0rG: yes, the upgrade tasks are used as task names and this is something different than a task doing additional SCRAM-SHA-512 authentication, for example). Imagine a SASL-EXTERNAL auth followed by a SCRAM-SHA-512 SASL2 task for additional authentication. Naming the upgrade task "SCRAM-SHA-512", too, would create a name clash. In general you just aren't as flexible as with this extra prefix. Additionally I made the prefix to have exactly the same length as the -PLUS suffix used for channel binding auth-methods to not introduce some length problems, should these upgrade tasks some day be standardized by the IETF TLDR; yes, they are needed, because a name clash with other SASL2 tasks could occur and in general make the protocol more flexible.

``` <continue xmlns='urn:xmpp:sasl:2'> <tasks> <task>UPGR-SCRAM-SHA-256</task> </tasks> </continue> ```

Zash, it was for _Someone_ 👍

well, now _Someone_ can't do it because of you Zash!

today, Zash is a Someone!

I'll try to be Somebody tomorrow then.

🥇