Re: Extending the roster item element
Florian Schmaus <[email protected]>
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <[email protected]> |
On 08/11/2025 16.59, Thilo Molitor wrote: > I'm volunteering to write a XEP adding an <extensions/> element > alongside the > <group/> element to allow arbitrary extensions for roster items. Extending roster items is tempting and seems like an ideal fit at first, but there is a reason this isn't usually done (probably besides some internal deployments): It's fragile, inefficient, and there are better alternatives. There is a good summary of the problems that come up in the "Bookmarks 2 extensibility" thread from Nov 2019. I'll try to come up with a link (assuming this is still accessible somehow). Basically, things you have to keep in mind include: you have to avoid clients overriding unknown extensions when re-submitting things. You may end-up with having to resubmit extensions even though you did not modify them (which is ineffective). You may want to distinguish between extensions that have been synthesized by the server. A dedicated PubSub node is in every case the better approach. - Florian _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
OpenPGP_signature.asc
(application/pgp-signature, 618 B)
-----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEl3UFnzoh3OFr5PuuIjmn6PWFIFIFAmkTeNJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk3 NzUwNTlGM0EyMURDRTE2QkU0RkJBRTIyMzlBN0U4RjU4NTIwNTIACgkQIjmn6PWF IFJZGwf/U/3cXNYR+TLXAnr0JkEIf+5lZf0PnV4mwtzPuRL+ZNdPTeecrR/wmhoJ fALc+ZXqxilaeCe1yXEshsBuQSIy+n7kFppCldE7lGk2IpjfDaL0rPxCEtzVdWxe GBP+ItU8N80+PFGe/UEW3xfSfu8GEsa5r8YyP5cqRtWr2ndScpjJ//PiZo+EHD62 PXqiSPZltZhHQIllVpjEZ3q3NnOftj5V1uf8m1EgfPEA9NQ+mMd4VjwE9X4KI0uc dfBewHziJdYPsw2XgW5O0wx8MhlbbSoUjptigv2RogZ2zbVNLhgmhX+VVeNd7IWA 7GJFK4aFbqQL7jwor+5O8h+tXA3O3w== =kSF4 -----END PGP SIGNATURE-----