develooper Front page | perl.perl5.porters | Postings from March 2013

Re: File::Spec in XS

Thread Previous | Thread Next
March 1, 2013 10:27
Re: File::Spec in XS
Message ID:
Nicholas Clark wrote:
>Specifically, track which version of the T&Cs a user has agreed to, and
>disable pushes (and all write actions) from any user who has not agreed
>to the currently enforced T&Cs.

Indeed, that would be the sane approach.  Not only good for users: it
would remove most of the potential for users to plead "I didn't agree to
*those* terms" if a case ever gets to court.  Good for everyone except
the lawyers.  Who are the ones drafting the terms... shit.

In the message from 2011 that I cited, I suggested that one could perhaps
implement this sort of thing on the client side, by code that examines
the ToS page before every operation.  There's still technically a race
condition, on the order of a few seconds, but if you get bitten by *that*
then it's a lot easier to argue the lack of notification in court.

There are other problems with the terms too, though (see previously
cited message), so I'm not really motivated to implement the automatic
terms checking.

More recently I ran into a similar situation, on another free software
project, with a Google-hosted service.  There the terms were OK except
for a similar immediate-binding clause for changes, so it would be rather
more worthwhile to automate terms checking.  (Google are certainly *less*
evil than the rest.)  Though in the end I got away with not using that
service directly at all: the regular developers were very accommodating
about letting me work the old-fashioned way, just emailing in patches.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About