- Standards

by Schimon Jehudah

Greetings. I advise to moderate people who have never posted to this mailing-list. It is bad enough that there is only a single official mailing-list; and Having issues with that single one will even worse. Please advise. Kindly, Schimon

1 month

2
2
0 0

Simultaneous

by kitana3310＠gmail.com

I am digital marketing expert

1 month

1
0
0 0

Participation of civil society in the standardization process + Last Calls

by Daniel Gultsch

Hi, I saw a talk by Sophia Longwe, who I believe works at Wikimedia Germany, at 39C3 (Chaos Communication Congress). I saw the talk in person, but there is a recording of it here: https://media.ccc.de/v/39c3-who-runs-the-www-wsis20-and-the-future-of-inter… The talk is a rudimentary overview of how the different bodies that "steer" the internet work t ranging from UN committees and ICANN down to mere mortals such as us. The XMPP Standards Foundation (XSF) was not called out specifically, but our colleagues at the IETF and W3C were mentioned. In her talk, she criticized the lack of participation from "civil society" in standardization work. She attributed this partially to high barriers to entry at IETF events (high costs, fancy hotels) and said (I’m paraphrasing) that it’s basically just rich FAANG employees. Some of that doesn’t exactly match my own experience at the IETF, but I don’t think any of what she said was in bad faith. I hope to meet her in Vienna (IETF126) to discuss some of these things in person. And who knows, maybe she is right. Anyway, long story short, this got me thinking about our processes here at the XSF (which, again, she didn’t mention at all): I think the XMPP Standards Foundation is in a unique position where many of our members can be described as "civil society" - people who might describe themselves as activists or promoters of XMPP rather than developers. (And/or people who do software development for a living, but whose jobs are unrelated to XMPP and who joined the XSF more in the capacity of a user.) At the same time, I’m observing that a lot of our Last Calls (and standards work in general) have few participants, at least relative to our overall membership numbers. Furthermore, I've heard criticism that the XSF doesn’t take the concerns of some minority groups seriously enough. (Which may or may not be true; I don’t want to take sides on that at this point.) This leads me to a question: Can we kill two or three birds with one stone here? Can we either rephrase some of the questions in the Last Call or add new ones that explicitly invite feedback from "civil society" (for lack of a better word)? I just want to get the discussion started, so I don’t have a final list, but the questions could go in a direction like this: * Would you use this feature if it were implemented in the XMPP client you currently use? * Do you think an implementation of this feature could negatively impact your community? * Does this improve (make easier) the work you do in your community? Cheers, Daniel

1 month, 1 week

7
10
0 0

i1_m2ogwfahkc6bk@anonymous.cheogram.com

by joseperezguerrero730＠gmail.com

hello

1 month, 1 week

2
2
0 0

UPDATED: XEP-0386 (Bind 2)

by Daniel Gultsch

Version 1.1.0 of XEP-0386 (Bind 2) has been released. Abstract: This specification provides a single-request replacement for several activities an XMPP client needs to do at startup. Changelog: It's authorization-identifier not authorization-identity (dg) URL: https://xmpp.org/extensions/xep-0386.html Note: The information in the XEP list at https://xmpp.org/extensions/ is updated by a separate automated process and may be stale at the time this email is sent. The XEP documents linked herein are up-to- date.

1 month, 1 week

1
0
0 0

Means to handle spam

by Schimon Jehudah

Greetings to one and all. I would want to apologise for posting to this mailing-list, as mailing-lists "general" and "jdev" are closed. I am interested in discussing automated spam, and automated counter measures against that issue. I have created a moderation service (i.e. "bot") software to handle this concern. The interface of that software is of XMPP client, so anyone can operate it from anywhere. I would be glad to be honored by your kind participation. https://git.xmpp-it.net/sch/KaikOut Merry Christmas and a Happy New Year, Schimon

1 month, 4 weeks

1
0
0 0

XSF Membership Application period Q1 2026

by Alexander Gnauck

I have setup the XSF membership application Wiki page for the application period Q1-2026 Applications are encouraged from developers and others who are actively involved in the Jabber/XMPP community. To apply, create a page about yourself on the Wiki: https://wiki.xmpp.org/web/Membership_Applications_Q1_2026 If you don't have a wiki account, send your full name, preferred nickname and email address to me or one of the other Sysops: https://wiki.xmpp.org/web/Sysops When you need help with your application then don't hesitate to contact me directly Apply now!!! Thanks, Alex

2 months

1
0
0 0

LAST CALL: XEP-0484 (Fast Authentication Streamlining Tokens)

by Daniel Gultsch

This message constitutes notice of a Last Call for comments on XEP-0484. Title: Fast Authentication Streamlining Tokens Abstract: This specification defines a token-based method to streamline authentication in XMPP, allowing fully authenticated stream establishment within a single round-trip. URL: https://xmpp.org/extensions/xep-0484.html This Last Call begins today and shall end at the close of business on 2025-01-27. Please consider the following questions during this Last Call and send your feedback to the standards(a)xmpp.org discussion list: 1. Is this specification needed to fill gaps in the XMPP protocol stack or to clarify an existing protocol? 2. Does the specification solve the problem stated in the introduction and requirements? 3. Do you plan to implement this specification in your code? If not, why not? 4. Do you have any security concerns related to this specification? 5. Is the specification accurate and clearly written? Your feedback is appreciated!

2 months, 2 weeks

6
20
0 0

Bind2 question

by Thilo Molitor

Why are the inlined bind2 features inside <feature/> elements rather than using the exact same syntax as when announcing the same features in the stream features element (e.g. <csi xmlns='urn:xmpp:csi:0'/>) For reference: <bind xmlns='urn:xmpp:bind:0'> <inline> <feature var="urn:xmpp:carbons:2" /> <feature var="urn:xmpp:csi:0" /> <feature var="urn:xmpp:sm:3" /> </inline> </bind> -tmolitor

2 months, 2 weeks

1
0
0 0

NEW: XEP-0509 (Initial Authentication Pipelining)

by Daniel Gultsch

Version 0.1.0 of XEP-0509 (Initial Authentication Pipelining) has been released. Abstract: This specification defines a protocol for discovering if the SASL2 <authenticate> can be pipelined safely along with the stream open, and if so allows the client to perform this pipelining safely. Changelog: Accepted as Experimental by council vote (dg) URL: https://xmpp.org/extensions/xep-0509.html Note: The information in the XEP list at https://xmpp.org/extensions/ is updated by a separate automated process and may be stale at the time this email is sent. The XEP documents linked herein are up-to- date.

2 months, 2 weeks

1
0
0 0

2026

2025

2024

2023

Standards