On 3 October 2017 at 12:24, Kevin Smith <[email protected]> wrote: > On 29 Aug 2017, at 13:27, Kim Alvefur <[email protected]> wrote: >> >> On Mon, Aug 28, 2017 at 12:03:37PM +0200, Daniel Gultsch wrote: >>> Now that the PR regarding publish-options has been merged into >>> XEP-0060 I want to bump this thread and ask if anyone objects to that >>> proposal (making persistent-items, node-config and publish-options >>> mandatory). Otherwise I would go ahead and create a PR for that and >>> let council vote on this next Wednesday. >> >> I'm sceptical. I would rather see an even smaller mandated feature set. >> Preferably exactly as much as required for extended presence (user tune >> etc) and *nothing* else. These features you want to make mandatory ought >> to be in XEP-0222 or XEP-0223 instead. Or perhaps a new XEP, the >> full-blown-pubsub-on-your-jid XEP you always dreamed about. > > Do we a need a pubsub-on-your-jid XEP? Isn’t that just 60? > > Personally, while I’m not keen on adding new requirements to 163, I am keen > on a note that says “Look, 163’s profile was good to get things rolling, but > really everyone should be doing full pubsub on a JID now”.
I agree with that. I don't really care where the note is. Clearly PEP has proven a success, and it seems fine that people want to grow and extend that with more features so we can grow and extend XMPP. But mandating these features in XEP-0163 is not a sensible solution. There are many use cases that are served quite comfortably by the original scope of PEP. The additional features we are talking about are not necessarily possible in certain environments, and there's no reason to make it "all or nothing". That's why we have feature discovery! But again, I'm not opposed to a newly-defined PEP profile that requires these features. Define a new feature, put it in the compliance suite XEPs, etc. I'm fine with that. I think it makes sense, because many modern protocols are depending on them. Finally, I feel it's an elephant in the mailing list that the main reason we're having this discussion is because Prosody happens to not support these features currently. So I just want to add that whether XEP-0163 begins mandating these additional features or not is going to have no effect on how soon we complete support for them. We're already working on it, and now 0.10 is out of the way it will be one of our main priorities. Regards, Matthew _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
