On Mon, 23 Sept 2024 at 08:27, Schimon Jehudah <sch@fedora.email> wrote:
I suggest to enable PEP nodes for MUC JIDs too.
Technically this wouldn't be PEP, just "Pubsub on a MUC JID". We've previously called such things MEP, but never specified them fully. That said, they're not exactly unspecified either - if all you wanted was PubSub on a MUC JID, that's pretty much a one-liner. If you do want the rest of PEP - the same smart defaults, and presence-based autosubscriptions - you'd need to specify how those worked.
I suggest to change the approach "One publisher per node.". See https://xmpp.org/extensions/xep-0163.html#approach-publisher
There is no need for multiple publishers to a PEP service, since by definition the service generates information associated with only one entity. The owner-publisher for every node is the bare JID of the account owner.
On this, PEP is a minimal profile of PubSub. I think most modern servers now just implement full pubsub on a personal Jid - which, being a proper superset of PEP's profile, is sufficient. This has been referred to before as "Pubsub-onna-Jid". POJ, anyone? (Please no). Anyway, PEP doesn't mandate only one publisher per node; it just says there's no need for anything else. But... PEP gives the minimum profile needed - and indeed early PEP support was a bespoke system on servers, which implemented just that minimum (and sometimes even less - I seem to recall servers that wouldn't allow multiple items). It also gives smart defaults and the presence-autosubscribe. I suspect it's not unreasonable to just require full PubSub (or at the very least much more than PEP) in a new XEP. And I suspect what you want to do here is just write a XEP for what SlixFeed does (and/or what it wants to do). Dave.