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

Jump to navigation Jump to search

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

Revision as of 20:41, 17 April 2020

273 bytes added ,  20:41, 17 April 2020
no edit summary
(Created page with "= 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. Buddyclo...")
 
 
(5 intermediate revisions by 2 users not shown)
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).
 
= Reliability issues =
 
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.
Pep.
416

edits

Retrieved from "https://wiki.xmpp.org/web/Special:MobileDiff/8213...12966"

Navigation menu