Unfortunately, this now means that normal 1:1 chats (that are synchronized as roster items) lag behind.I'm volunteering to write a XEP adding an <extensions/> element alongside the <group/> element to allow arbitrary extensions for roster items. This would bring 1:1 roster items on-par with bookmarks2 and immediately allow XEP-0492 and XEP-0469 to be applied to roster items as well.
While I have always been team "1:1 items in bookmarks2 is fine" this seems like a very clean solution here. I don't know that we need an <extensions/> element per se but a XEP to specify that custom children of roster items should be preserved would solve the "yet another roster in pep" issue we seem to keep having.
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
