- Standards

NEW: XEP-0496 (Pubsub Node Relationships)

by Daniel Gultsch

Version 0.1.0 of XEP-0496 (Pubsub Node Relationships) has been released. Abstract: This specification describes how to establish links between pubsub nodes, allowing for optional hierarchical organization. Changelog: Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0496.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.

11 months, 2 weeks

1
0
0 0

PSA: Change your CSI implementations to let PEP notifications from the account through

by Daniel Gultsch

Hi, TLDR: It is common practice for CSI (Client State Indication) implementations to withhold (and deduplicate) PEP notifications and/or headline messages. Due to the rise of XEPs such as Message Displayed Synchronization (MDS) those implementations need to be changed to immediately let through PEP notifications from nodes that are on the account itself. I noticed the MDS problem in theory a while ago but didn’t care too much because due to a lack of implementations I’m not using MDS on a daily basis. (MDS needs to be able to dismiss notifications even if the client is in background) However today I ran into a related problem with Bookmarks 2 and User Nickname. I was writing code that actually performs a rename in a MUC if the desired nick changes (either pulled from the bookmark or if that one is unset from XEP-0172) instead of only using these sources on initial join. I think it is somewhat obvious that the rename should be done fairly instantly on all clients once a client has made the change (either to the bookmark or to 0172). Otherwise other users would see the user as being joined multiple times with different nicks until all clients have come to the foreground. I guess letting through all PEP notifications from the account (instead of allow listing certain nodes) is good enough. That’s beneficial for Nick, Bookmarks, OMEMO. The only one for which we technically don’t need it is Avatar. But how often do you change that one (meaning how many false positives would you generate?!) cheers Daniel

11 months, 4 weeks

1
0
0 0

STABLE: XEP-0490 (Message Displayed Synchronization)

by Daniel Gultsch

Version 1.0.0 of XEP-0490 (Message Displayed Synchronization) has been released. Abstract: This specification allows multiple clients of the same user to synchronize the displayed state of their chats. Changelog: Accept as Stable as per Council Vote from 2024-11-05. (XEP Editor (dg)) URL: https://xmpp.org/extensions/xep-0490.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 year

1
0
0 0

XMPP Council Agenda 2024-11-05

by Daniel Gultsch

Good morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, November 5 2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join The Agenda is as follows: 1) Roll call 2) Agenda Bashing 3) Editors update - none 4) Items for voting a) Move 'XEP-0490: Message Displayed Synchronization' to stable https://xmpp.org/extensions/xep-0490.html 5) Pending votes Travis on 3 PubSub proto xeps from last week. See the spreadsheet of Doom: https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa… 6) Date of Next 7) AOB 8) Close

1 year

1
0
0 0

LAST CALL: XEP-0490 (Message Displayed Synchronization)

by Daniel Gultsch

This message constitutes notice of a Last Call for comments on XEP-0490. Title: Message Displayed Synchronization Abstract: This specification allows multiple clients of the same user to synchronize the displayed state of their chats. URL: https://xmpp.org/extensions/xep-0490.html This Last Call begins today and shall end at the close of business on 2024-10-31. 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!

1 year

4
3
0 0

Problem with the mailing list

by Schimon Jehudah

Good day! Am I the only one to not receive emails that are sent by Mr. Jérôme Poisson? (Email "goffi") Kind regards, Schimon

1 year

6
10
0 0

Proposed XMPP Extension: Pubsub Extended Discovery

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Pubsub Extended Discovery Abstract: This specification extends the discovery requests used with the XMPP PubSub protocol by introducing mechanisms to discover linked nodes, descendants, or metadata. URL: https://xmpp.org/extensions/inbox/pubsub-extended-discovery.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 year

3
2
0 0

Proposed XMPP Extension: Pubsub File Sharing

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Pubsub File Sharing Abstract: This specification explains how to share files and optionally include directory structures similar to filesystems over XMPP Pubsub. It leverages XMPP Pubsub to enable notifications about file changes and manage permissions, providing users with real-time updates and control mechanisms. An optional mechanism is also specified for managing uploaded files. URL: https://xmpp.org/extensions/inbox/pubsub-file-sharing.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 year

3
2
0 0

Proposed XMPP Extension: Pubsub Extended Subscriptions

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Pubsub Extended Subscriptions Abstract: This specification extends the XMPP PubSub protocol by introducing mechanisms for users to subscribe to an entire node hierarchy or to receive notifications on node metadata updates. URL: https://xmpp.org/extensions/inbox/pubsub-extended- subscription.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 year

3
2
0 0

XMPP Council Agenda 2024-10-29

by Daniel Gultsch

Good morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, October 29 2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join The Agenda is as follows: 1) Roll call 2) Agenda Bashing 3) Editors update * UPDATED: XEP-0394 (Message Markup) * UPDATED: XEP-0491 (WebXDC) * Proposed XMPP Extension: Pubsub File Sharing * Proposed XMPP Extension: Pubsub Extended Discovery 4) Items for voting a) Proposed XMPP Extension: Pubsub File Sharing https://xmpp.org/extensions/inbox/pubsub-file-sharing.html b) Proposed XMPP Extension: Pubsub Extended Discovery https://xmpp.org/extensions/inbox/pubsub-extended-discovery.html 5) Pending votes * Dan and Daniel on 'Proposed XMPP Extension: Pubsub Node Relationships' See the spreadsheet of Doom: https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa… 6) Date of Next 7) AOB 8) Close

1 year

2
1
0 0

2025

2024

2023

Standards