emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Anthony Carrico <acarrico@memebeam.org>
To: Kyle Meyer <kyle@kyleam.com>,
	"Jorge P. de Morais Neto" <jorge+list@disroot.org>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Bug: JavaScript in HTML export not recognized by LibreJS as free [9.4.5 (9.4.5-16-g94be20-elpaplus @ /home/jorge/.config/emacs/elpa/org-plus-contrib-20210412/)]
Date: Thu, 22 Apr 2021 16:29:15 -0400	[thread overview]
Message-ID: <073538d9-09ac-7c6f-0188-6e75d0daf438@memebeam.org> (raw)
In-Reply-To: <87czupy7mn.fsf@kyleam.com>

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


  parent reply	other threads:[~2021-04-22 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 20:26 Bug: JavaScript in HTML export not recognized by LibreJS as free [9.4.5 (9.4.5-16-g94be20-elpaplus @ /home/jorge/.config/emacs/elpa/org-plus-contrib-20210412/)] Jorge P. de Morais Neto
2021-04-20  3:09 ` Kyle Meyer
2021-04-20  4:55   ` Tim Cross
2021-04-22 20:42     ` Anthony Carrico
2021-04-22 21:20       ` Tim Cross
2021-04-22 22:35         ` Anthony Carrico
2021-04-22 20:29   ` Anthony Carrico [this message]
2021-04-23  1:42     ` Anthony Carrico
2021-04-26 12:43     ` Bastien
2021-04-26 20:36       ` Anthony Carrico
2021-05-01  9:30         ` Bastien
2021-04-26 12:45     ` Jorge P. de Morais Neto
2021-04-26 16:57       ` Bastien
2021-04-27 17:57         ` Jorge P. de Morais Neto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=073538d9-09ac-7c6f-0188-6e75d0daf438@memebeam.org \
    --to=acarrico@memebeam.org \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jorge+list@disroot.org \
    --cc=kyle@kyleam.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).