Skip to content

Conversation

@guusdk
Copy link
Contributor

@guusdk guusdk commented Oct 6, 2025

Addresses the persistent misunderstanding that the 'http://jabber.org/protocol/pubsub' feature is safe to use, and provide clear guidelines to minimize current interoperability challenges.

Key changes:

  • Advise client implementations to use identity, not feature, when discovering services.
  • Advise service implementations to advertise the feature for compatibility with common interpretations of the protocol.

These changes have been discussed in the XMPP Standards chatroom (logs: https://logs.xmpp.org/xsf/2025-10-03#2025-10-03-f173fd843da7c3ee ) and on the standards mailinglist: https://mail.jabber.org/hyperkitty/list/[email protected]/thread/R4K2OAPVBQ4IC757F2YBZDV4PPHFGRNS/

… feature

Addresses the persistent misunderstanding that the 'http://jabber.org/protocol/pubsub' feature is safe to use, and provide clear guidelines to minimize current interoperability challenges.

Key changes:
- Advise client implementations to use identity, not feature, when discovering services.
- Advise service implementations to advertise the feature for compatibility with common interpretations of the protocol.
@github-actions github-actions bot added the Needs Council The affected XEP has the Council as Approving Body and it needs to decide on the change. label Oct 6, 2025
@guusdk
Copy link
Contributor Author

guusdk commented Oct 6, 2025

If this is merged as-is, a Registrar change (to add the http://jabber.org/protocol/pubsub Service Discovery feature) should be performed.

Flowdalic added a commit to Flowdalic/Smack that referenced this pull request Oct 8, 2025
The previously used feature of PubSub.NAMESPACE is wrong (see also
xsf/xeps#1468).
Flowdalic added a commit to Flowdalic/Smack that referenced this pull request Oct 8, 2025
The previously used feature of PubSub.NAMESPACE is wrong (see also
xsf/xeps#1468).
Flowdalic added a commit to Flowdalic/Smack that referenced this pull request Oct 8, 2025
The previously used feature of PubSub.NAMESPACE is wrong (see also
xsf/xeps#1468).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs Council The affected XEP has the Council as Approving Body and it needs to decide on the change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants