jdev - 2020-08-03

lovetox, code that checks that assumptions are met, and otherwise takes care that they are met, appears to be always sensible

lovetox, there are good reasons to not have persist items set to true by default, but you should get away with assertions during item publish

(XEP-0060 assertions, not `assert node.config == correct`)

jonas’, xep60 allows to publish with an item and given configuration options that need to be fulfilled? or what are xep60 assertions (there is one hit for 'assert' in xep60)?

exactly that

<publish-options/>

the publish fails with <conflict/> if an option is set to a different value, and the options are applied otherwise

ahh that, I stopped reading at 7.1.3

jonas’, yes i know about publish options

it about what to do if there is a conflict

tell the user to contact the admin, or simply force all nodes to my will ✏

the later is of course much more work and even more error cases to handle

lovetox, if there’s a conflict, it may not be the admins fault at all

might also be the user’s fault

or another client’s fault

how does that help me :)

there is not many config options we can change at all, i think access model and persist, and then it ends

so persist items is the most likely one to fail