Hi, As far as I can see, you are actually try to kill a mosquito with an atomic bomb. Personally I would just state the TOS simple. Like the pool is in no way liable for any kind of accuracy of time, or time measurement, therefore the pool should not be used for any kind of system where time is critical. And users (not end user, that is someone totally different. Someone you have usually no interaction with, and you can't have an agreement that involves third parties who are not part of the original relation, between you and the systems operator), should configure their system, in such a way, that it will not cause any malfunction of the pool. And that you reserve the right to deny clients access to the pool.
Basically, keep it as simple as possible. You most certainly do not want the users, and contributors, to enter in a legal binding agreement, with all the implications of that. Moreover, we are users and contributors. You take the role of forcing the contributors to abide by the ToS, but do not grant us the same legal protection you give yourself. I understand what you want to accomplish, but if you do it this way, I feel I should withdraw all my servers, and never, ever use the pool. And that will escalate, since I feel the need to advice my customers, to quit using, or contributing to the pool. Please reconsider what you want to accomplish, be aware that the pool is used voluntarily, and free ( as in free beer ). There is no transaction involved, you have not a supplier customer relationship with users. You are already immune, on this basis, by the DMCA. But it will not hurt to explicitly state that the pool, nor its contributors, are not responsible for any damage that is a result from using the pool. That will not make us immune for everything, such as with malintent and criminally tinker with the system. Do not use legalise language more than needed, but if you do, make sure it also protects the contributors. And that is an international bunch. Not automatically bound by US law. Just my 2cents. Jasper Kips, Always waiting for the ricochet Op 30 aug. 2013 om 10:08 heeft Ask Bjørn Hansen <[email protected]> het volgende geschreven: > Hi everyone, > > The website now has a terms of service document for how to use the NTP Pool -- > > http://www.ntppool.org/tos.html > > The main points are about not configuring syncing in a dumb way (top of the > hour, too frequent, etc) and that the service is provided as-is -- don't use > it for anything where correct time is business- or life-critical. > > > Ask > > > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
