On 1 June 2017 at 12:51, Georg Lukas <[email protected]> wrote: >> Requiring servers to implement particular delivery rules: >> https://github.com/xsf/xeps/commit/9c388a51c61541507c599832038b6562f3d01841 >> >> I don’t think this is right, I think we want to allow servers to make >> their own judgements on what needs carbonsing. This was the consensus >> compromise we made previously (after considerable effort) to remove >> the objections to 280 going to Draft. > > I have to disagree. The current wording is inadequate for a network > protocol specification: it does not provide any consistency between > implementations, leading to subtle differences in observed behavior and > to user confusion. > > Carbons is now over seven years old, so all server implementations > should have figured out their rules by now, or at least a set of rules > which we can make mandatory. I can see how creating such a mandatory > rule set might have been an issue back at the inception of the XEP, but > right now, we should have the accumulated knowledge to nail it, finally.
It would be very useful if server developers implementing Carbons could take a look at these proposed rules and see how well (or badly) they match reality. That would be extremely beneficial, I think, in obtaining a clear idea of whether these rules are right or not. Dave. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
