Linked by Thom Holwerda on Sat 29th Sep 2007 21:24 UTC, submitted by Kishe
Permalink for comment 275309
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2007-08-01
"Of a more interesting subject of discussion, I remember there was an interesting point made over machine-specific code through encryption (tivoisation) used in the context of casino gaming, voter machines, etc. There may be cases in which the GPL3's freedoms are not ideal, and one would want to restrict in what ways it can be used or redistributed by choosing a more restrictive OSS license."
The prohibition against tivoisation only applies to "consumer devices." Neither of those cases involve a consumer device as defined in Gpl3, and neither of them would invoke the anti-tivoisation language anyway. The GPL3 only provides that the *owner* of the device in question should have the freedom to modify it. Gamblers don't own slot machines, nor do voters own voting machines. Supposed weakness like this one are produced in abundance by people who don't bother to read and understand the license before commenting.