According to the following spec, an entity with a publisher affiliation should be able to delete an item, regardless of whether or not the publisher was the original publisher of the item.
Please see the following:
"A service may allow any publisher to delete / purge any item once it has been published to that node instead of allowing only the original publisher to remove it."
Is this an optional implementation? I'm using 2.1.0 and this doesn't seem to be the case. I can delete the item if I am the original publisher; however, I can't remove it when logged in as another publisher. I have a use case where I need to remove an item after a subscriber receives it, so that they don't receive it again. The owner of the published item is an single entity associated with my web application and I don't want the subscribers or publishers having the same permissions.
Hope that makes since. If not, please let me know and I'd be more than happy to elaborate.
Best Regards,
Ken
The XEP-0060 says: "Note: A
The XEP-0060 says:
"Note: A service MAY allow any publisher to delete / purge any item once it has been published to that node instead of allowing only the original publisher to remove it."
As you can see, the "MAY" is in capital letters. That term is described in
"5. MAY: This word, or the adjective "OPTIONAL", mean that an item is truly optional."
> Is this an optional implementation?
Yes, and from what you say, it seems ejabberd doesn't implement it.