XSF Discussion - 2022-06-29

We are missing a way to specify an element in a pubsub item in XEP-0372: it's usable out of the box to mention somebody in a XEP-0277 blog post, but we can't specify the substring.

I would love to be able to specify something like `element=entry{http://www.w3.org/2005/Atom}/title'

XPath is knocking at the door, the windows, and trying to climb down the chimney

yes of course XPath would be great. At least a simplified version.

For pubsub mentions, maybe it would be simpler to just do something specific to XEP-0277.

`element="title" type="text"`, `element="content" type="xhtml"`

What is the expected Connection Manager behavior if a BOSH client sends a 'pause' value that's higher than the 'maxpause' value?

terminate/policy-violation ?

or https://xmpp.org/extensions/xep-0124.html#errorstatus-recover ?

although replaying it doesn't make sense.

could we not communicate some kind of hash in the disco info for the pep notify features

then the server could know what we last received

and does not need to send us the same info all the time again on going online

or maybe the timestamp we received the last notify

http://jabber.org/protocol/tune+notify@2022-07-01T12:23Z

then the server can check if there was a update to the node since then

https://xmpp.org/extensions/xep-0312.html ?

hm same idea, but the solution seems much more fragile

when communicating the timestamp its the last timestamp when the client received something from that node

is per-node needed?

yes

time since last connecting is too fragile

there is no indication for a client when a pubsub catchup was or is complete

server can be down while i come online

then i go offline, server comes online, i come online, and send, last onlince since 2 seconds

server determines, no updates in the last 2 seconds

but missed me coming online 20 times before

who is "server" here?

the remote server from which i want updates ✏

is there only one?

no, but the example was about one that is down

i come online, i tell you my last logout time was 100 seconds ago, but this nice presence never reaches the remote server because its in maintainence

then i reconnect

and so last logout time = 2 seconds

now this presence reaches the remote

and it sends me nothing

further there is no indication for a client that a pubsub catchup is complete

so i cant even delay my reseting the last logout time

what if i crash while connecting?

did i crash befor i got all pubsub notifications? or after?

i see stale info with this approach everywhere

advantage is, i would not have to store last received timestamps