11 Nov
2025
11 Nov
'25
10:48 a.m.
(Belatedly, although I’ve shared the feedback prior to LC)
On 20 Oct 2025, at 18:35, Daniel Gultsch <daniel(a)gultsch.de> wrote:
This message constitutes notice of a Last Call for comments on
XEP-0485.
Title: PubSub Server Information
Abstract:
This document defines a data format whereby basic information of an
XMPP domain can be expressed and exposed over pub-sub.
URL: https://xmpp.org/extensions/xep-0485.html
This Last Call begins today and shall end at the close of business on
2025-11-03.
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?
It specifies something not otherwise done. I’m not sure I could claim it’s a real gap, nor
that it’s ’needed’.
2. Does the specification solve the problem stated in the introduction
and requirements?
Largely.
3. Do you plan to implement this specification in your code? If not,
why not?
No (I don’t think it’s useful, and I’m concerned by the privacy implications).
4. Do you have any security concerns related to this specification?
I remain concerned about the privacy implications, even when opt-in (I guess maybe that a
server operator might opt-in but not include it in their privacy terms is a social problem
rather than a technical one, but whether users are able to understand the potential
fingerprinting seems unlikely).
5. Is the specification accurate and clearly written?
AFAICS.
/K