20,741
edits
Frequently asked questions: Difference between revisions
Jump to navigation
Jump to search
→Content Protection
m (→Content Protection: https://forum.flightgear.org/viewtopic.php?f=6&t=7351&hilit=drm&start=15) |
|||
| Line 240: | Line 240: | ||
FlightGear in its current form is a product of numerous people working voluntarily on a joint effort to create an open and extensible flight simulator platform. Your very idea of introducing DRM, is against all principles of open source in general. | FlightGear in its current form is a product of numerous people working voluntarily on a joint effort to create an open and extensible flight simulator platform. Your very idea of introducing DRM, is against all principles of open source in general. | ||
You're free to create a non-GPL plane for FG - that's data from the perspective of the sim and doesn't trigger the license. You can sell that without ever allowing to re-distribute the source code. You're required to stay clear of a few things (you can't use Generic instruments, Nasal libs,...) but that should be doable. You can charge license fees for such a plane, and nobody may legally re-distribute it.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35074186/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = May 9th, 2016 | |||
|added = May 9th, 2016 | |||
|script_version = 0.37 | |||
}}</ref> | |||
FG itself is OpenSource, so whatever protection scheme we may code in, anyone is free to remove (and that's quite legal). It'd be a no-brainer to generate a no-copyright-protection version of FG and distribute it on which your content just runs without the key (or whatever). Given that people usually succeed in cracking DRM schemes in the absence of an open source code, trying to do this with the source code open for anyone seems just a waste of time. Second, whatever format OSG reads, before it arrives at the renderer, it's bound to be an array of vertices. The renderer needs this, there's no decryption at the GLSL stage. So chances are that since we run on *Open*GL, again anyone who really wants can write out an unencrypted format.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35074186/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = May 9th, 2016 | |||
|added = May 9th, 2016 | |||
|script_version = 0.37 | |||
}}</ref> | |||
if you actually try to charge 100$ for a FG plane, you won't find too many customers... because FG is mainly popular in the OpenSource community. If you make it too cumbersome with DRM schemes, maybe someone will try to circumvent it just as a matter of principle (people do this for sport...) - but across multiple platforms, it's actually not easy to make this not an annoyance for the user.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35074186/ | |||
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared | |||
library, and what legislation issues would that ensue? </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = May 9th, 2016 | |||
|added = May 9th, 2016 | |||
|script_version = 0.37 | |||
}}</ref> | |||
Adding support for DRM to FlightGear is not going to happen - Nasal scripts are provided in plain text format by default (similar to JavaScript), while obfuscation is of course possible - it doesn't make any sense in the context of FlightGear as an open source project. | Adding support for DRM to FlightGear is not going to happen - Nasal scripts are provided in plain text format by default (similar to JavaScript), while obfuscation is of course possible - it doesn't make any sense in the context of FlightGear as an open source project. | ||