the problem is who owns the handshake, even if the slicer is under the agpl license i think this could cause a rewrite because this is a service level tivoizati

the problem is who owns the handshake, even if the slicer is under the agpl license i think this could cause a rewrite because this is a service level tivoization you cant use the software without the handshake, gplv1 allowed software based tivoization, gplv2 allowed hardware based tivoization, gplv3/agpl allows service based tivoization which mean theres a loophole looking to be closed all over again because if i use agpl web app from a public site, i have the right to get the code if i want to fork that code i have to violate the handshake