Hi all. Thanks for the note. I took a look at the LibreJS docs to try to
understand the problem. My analysis:
LibreJS is a web filtering plugin. Users are making a decision to block
content which is not explicitly licensed in the LibreJS syntax,
including public domain works marked in that syntax. Apparently LibreJS
is working as designed. I don't think we should attempt to work around a
user's web filtering software.
My understanding is that authors who want to get through the web filter
should include an approved LibreJS license notice at the top of their
page, and a separate license in a <script> when it conflicts with their
chosen license.
Practically speaking, the script included by org-mode is in the public
domain, so it could never conflict with whatever license the author
chooses. Therefore, we should remove the LibreJS tag from the <script>,
perhaps leaving behind the public domain notice in the <script> comment.
With that tag removed, the LibreJS web filter should respect whatever
LibreJS license the document's author includes, if any.
--
Anthony Carrico
