On Wed, 15 Mar 2023 at 00:01, Maxime Buquet <[email protected]> wrote:
> I have just submitted https://github.com/xsf/xeps/pull/1275
>
> I remember first mentioning it here[0] and jonas giving me a quick
> answer[1] at the time. I've seen this happen again recently and I
> decided to give it some time.
Yay, thanks so much for tackling this one! :)
> When configured to "reject", I propose to have the service return
> cancel/conflict. It seems conflict is already returned on
> publish-options error so a <node-full/> element SHOULD be returned
> alongside to differenciate.
That seems sensible.
> When configured to "retract", I propose to allow the item to be published,
> retracting an existing item beforehand. It is currently worded as "the
> item with the earliest creation date MUST be retracted", but I wonder
> there should be more options for this, such as "retract_created",
> "retract_updated", etc.
>
> For backwards compatibility, which is implementation defined, this
> option simply won't be set. I am not sure there is a way to unset a
> node option though, so maybe there should be a "¯\_(ツ)_/¯" (shrug)
> variant to this new option.
I actually think the current behaviour of Prosody (and I think
ejabberd? others?) is definitely desirable in some cases, and I
propose making it an explicit option ('discard-oldest'?) - in this
mode the node is effectively a cache of the most recent items.
> I have also added a disco feature for discoverability.
Good idea.
Regards,
Matthew
PS. I tried rendering HTML diffs, but my usual process failed (I think
because of the size of XEP-0060) and I don't have time to debug. If
someone has a process that works, that would be great to share :)
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
