20,741
edits
Frequently asked questions: Difference between revisions
Jump to navigation
Jump to search
m
→Content Protection: https://forum.flightgear.org/viewtopic.php?f=6&t=7351&p=70032&hilit=drm#p70032
m (→Content Protection: https://forum.flightgear.org/viewtopic.php?f=6&t=7351&p=70032&hilit=drm#p70032) |
|||
| Line 238: | Line 238: | ||
|script_version = 0.37 | |script_version = 0.37 | ||
}}</ref> | }}</ref> | ||
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. | |||
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. | |||
Also, scripts can be easily shared and run by users just by exchanging or copying them. | |||
Even if you were to dump intermediate Nasal bytecode to an object file and execute this using the Nasal VM, there would be no way of enforcing DRM. | |||
Of course, FlightGear being open source, you could also just add support for DSOs/plugins to a fork of FlightGear and base all your work on this fork - on the other hand, your modifications would still need to be made available. | |||