Difference between revisions of "XEP-Remarks/XEP-0060: PubSub"

XEP-Remarks/XEP-0060: PubSub (view source)

21 bytes added , 20:41, 17 April 2020

no edit summary

416

edits

@@ Line 1: / Line 1: @@
-= Missing functionality =
+{{remarks}}
-XEP-60 appears to be missing some important use cases, so that some implementations have to resort to using their own flavor of PubSub, e.g. Buddycloud. Which prevents those projects from using standard compliant PubSub implementations (e.g. Buddycloud uses a patched version of Smack's PubSub implementation).
-Examples include
+= Reliability issues =
-* Adding a new access model 'local'. See [http://buddycloud.github.io/buddycloud-xep/#default-roles Buddycloud-XEP: Channel Access Models] vs. [http://www.xmpp.org/extensions/xep-0060.html#accessmodels XEP-60 4.5 Node Access Models]
+https://mail.jabber.org/pipermail/standards/2019-October/036503.html
+ Is there a way to know as a client when we're going to run into the
+ limit [of items]? Or when we've gone over the limit? Or is the pubsub
+ service just overwritting stuff and nobody ever noticies?
+= No mechanism to query all items after an item with a certain ID =
+This makes it hard and very inefficient to catch up on a PubSub node, after an client comes online again.
+= XMPP address of publisher is not included in the notification =
+Sometimes you want to know who actually published the item.