Good day!
I am the developer of Slixfeed news bot, which is a syndication
feed reader (Atom/RDF/RSS).
This matter is also related to Morbot.
See
https://codeberg.org/TheCoffeMaker/Morbot/issues/13
Concern
-------
I have to attempted experiment with PEP nodes, and my attempt has
failed due to:
XEP-0045
service-unavailable
The feature requested is not supported by the conference
XEP-0163
forbidden
You're not allowed to create nodes
Proposal
--------
I suggest to enable PEP nodes for MUC JIDs too.
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.
In order to allow a secondary "channel" interface for people and group
chats, and also for other reasons (see further), it would be useful to:
1) Allow multiple publishers.
2) Allow PEP for MUC JIDs.
By a "channel" interface, I mean, that should a news bot be included
for a group chat, the updates would be sent to a PEP node of the group
chat JID instead to the chat itself, which would keep the chat view
cleaner.
Example use cases:
Number #3 represents the use of Morbot and Slixfeed, and is useful for
forwarding of news journals.
1) Use : Inbox
Affiliation : Publish-Only
Publishers : JIDs which Presence is shared with or in Roster
2) Use : Collaboration (e.g. Pad, Whiteboard etc.)
Affiliation : Publisher
Publishers : Determined manually
3) Use : Updates
Affiliation : Publish-Only
Publishers : Determined manually
Note
----
Slixfeed can use its own PEP nodes named after its subscribers
respectively, albeit that would be more demanding on the server of
which Slixfeed is operated on, than publishing to PEP nodes of other
JIDs, and yet it would not be practical for group chat JIDs, which the
bot also supports.
Please advise.
Kind regards,
Schimon