|(4 intermediate revisions by 2 users not shown)|
= Missing functionality =
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).
* 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]
Latest revision as of 20:41, 17 April 2020
This is a page for information about XEP-Remarks/XEP-0060: PubSub, including errata, comments, questions, and implementation experience.
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.