Red Hat Bugzilla – Bug 982415
Please remove porn extractor
Last modified: 2013-07-18 17:55:52 EDT
Description of problem:
Pornography is considered offending in many cultures and it is not
compatible an enterprise class operating system. Please remove the
following extractor for adult content web site:
(maybe there are others, I just listed those with an explicit name).
I'm investigating it, please wait.
thank you for sharing your concern. I don't believe it should be acted upon
though. Thus, please do _NOT_ remove the adult content extractors.
Please let me explain:
1.) The code in question does not carry any pornographic content.
It merely is able to download content. Last time I checked Firefox browser (and
other user agents shipped with Fedora) was able to browse adult content without
any limitation. I'm sure you don't want those to be removed.
2.) The code is actually useful to users and being actively used
I'm sure you won't like the idea of removing software you use just because it
offends someone else. There is a rather large amount of software engineers
offended by presence of Maven or Java platform itself. It just happens when the
user base is big enough and used by diverse communities. If every potentially
offending piece of software was removed, there probably won't be much left in
The packaging mechanism makes it possible to easily uninstall the software or
even can be configured to ignore the packages (see exclude= in yum.conf(5)).
(If you find the rest of youtube-dl useful and can't afford to install adult
content extractors, maybe they can be split into a subpackage?)
2.) The code does not violate Fedora policy on forbidden items
Please have a look at https://fedoraproject.org/wiki/Forbidden_items
Actually, the reverse is true -- it is preferable for Fedora to ship unmodified
software packages as provided by respective upstreams.
as long as the package does not ship pornographic contents, it is not against any current Fedora policy. There has been a Fedora board decision about a similar package to allow it:
Also EPEL is not strictly for enterprise users:
I suggest that you enforce your policy by blocking access to the respective web sites directly for example in a firewall, which will work independently of the client used to access the web site.