-
pep.
marc_: I think he's away for the time before the meetup
-
Link Mauve
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?
-
Link Mauve
For sending notifications to subscribers.
-
ralphm
Unsure, I'd have to look up discussions around then
-
marc_
pep.: ah, do you have information on time and date?
-
marc_
I would like to ask the Wiki guys for a room
-
pep.
marc_, sent you that in private
-
marc_
pep.: okay, I would like to organize a Room. Do you know when you guys are in Munich?
-
pep.
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.
.
-
Daniel
pep.:?
-
marc_
Dino guys+others, would you like to do a Meetup during the Mentor Summit? If yes, when?
-
Seve
Mentor Summit?
-
mathieui
Seve, GSoC
-
Seve
Ah :)
-
lovetox_
hm i think we discovered once more a problem with pubsub
-
lovetox_
.
-
lovetox_
pubsub does not define a option of "maximal possible" for some fileds
-
lovetox_
like max_items, and item_expire
-
lovetox_
if we have a XEP like bookmarks2, the client is FORCED to set a abritary max_items value
-
lovetox_
because there is no possiblitiy to tell the server take whatever is your max allowed amount
-
lovetox_
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