XSF Discussion - 2019-09-28

marc_: I think he's away for the time before the meetup

ralphm, what is the justification for retract requiring notify='1' (§7.2.2.1) but not publish (§7.1.2.1) or purge (§8.5.2) in PubSub?

For sending notifications to subscribers.

Unsure, I'd have to look up discussions around then

pep.: ah, do you have information on time and date?

I would like to ask the Wiki guys for a room

marc_, sent you that in private

pep.: okay, I would like to organize a Room. Do you know when you guys are in Munich?

Mentor summit is from the 17th to the 20th, I don't know exactly when I'll be in Munich, I think the dino people will here exactly during these dates

.

pep.:?

Dino guys+others, would you like to do a Meetup during the Mentor Summit? If yes, when?

Mentor Summit?

Seve, GSoC

Ah :)

hm i think we discovered once more a problem with pubsub

.

pubsub does not define a option of "maximal possible" for some fileds

like max_items, and item_expire

if we have a XEP like bookmarks2, the client is FORCED to set a abritary max_items value

because there is no possiblitiy to tell the server take whatever is your max allowed amount

this means we have to ask all server implementations what they support, then take the lowest value, then write it to the XEP, and later if we want to update it we get into a much more shity situation, now clients force max_items via publish options to some number, then if one client wants to raise that, other clients reconfigure the node back to the old value