https://wiki.xmpp.org/web/index.php?title=XEP_ideas/Terms_of_Services&feed=atom&action=historyXEP ideas/Terms of Services - Revision history2024-03-29T14:42:14ZRevision history for this page on the wikiMediaWiki 1.37.1https://wiki.xmpp.org/web/index.php?title=XEP_ideas/Terms_of_Services&diff=12960&oldid=prevPep.: Created page with "{{specs}} Following the GDPR work that was done within the XSF in 2018, some work around a XEP to serve Terms of Services and related documents inbound was started. Unfor..."2020-04-17T20:39:35Z<p>Created page with "{{specs}} Following the <a href="/web/GDPR" title="GDPR">GDPR</a> work that was done within the XSF in 2018, some work around a XEP to serve Terms of Services and related documents inbound was started. Unfor..."</p>
<p><b>New page</b></p><div>{{specs}}<br />
<br />
Following the [[GDPR]] work that was done within the XSF in 2018, some work around a XEP to serve Terms of Services and related documents inbound was started. Unfortunately it met some resistance and got dropped.<br />
<br />
* ProtoXEP: [https://mail.jabber.org/pipermail/standards/2018-May/034969.html announce], [https://xmpp.org/extensions/inbox/tos.html inbox]<br />
* Council votes: [https://mail.jabber.org/pipermail/standards/2018-May/035015.html here], and [https://mail.jabber.org/pipermail/standards/2018-June/035124.html here].<br />
<br />
== General feedback ==<br />
<br />
TODO.<br />
<br />
The XEP was [https://mail.jabber.org/pipermail/standards/2018-June/035126.html vetoed] for the following reasons:<br />
it seems to me that it would fit very well as part of extensible IBR and/or SASL2.<br />
<br />
== Requirements ==<br />
<br />
It seems to me it might also be missing a way to expose ToS for s2s. Some services have expressed put into place measures to require users to accept ToS the first time they talk to a MUC component or the like.</div>Pep.