<!--#include virtual="/server/html5-header.html" -->
<!-- Parent-Version: 1.95 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<title>Write site-specific extensions to replace sites' JavaScript code
- GNU Project - Free Software Foundation</title>
 <!--#include virtual="/help/po/help-javascript.translist" -->
<!--#include virtual="/server/banner.html" -->
<div class="reduced-width">
<h2>Write site-specific extensions to replace sites' JavaScript code</h2>
<div class="thin"></div>

<p><em>Many websites damage users' freedom by sending <a 
href="/philosophy/javascript-trap.html">nonfree JavaScript programs</a> 
to the user's browser. We invite volunteers to develop free browser 
extensions to replace for the JavaScript sent by particular sites 
(see the lists below).</em></p>

<p>Our first response to the problem of nonfree JS code was to develop
<a href="/software/librejs/">LibreJS</a>, which enables Firefox-based 
browsers to detect and block that code. That protects us from running 
a site's nonfree JS programs, but does not make the site actually 
function. Writing an extension for it, as we propose here, would achieve 
that. It would also avoid the risk inherent in running software straight 
off someone else's website.</p>

<p>We could also solve the problem by convincing the webmasters to
correct their sites to function without the JavaScript code, but
convincing them proves to be very difficult, since mostly they don't
understand the issue, let alone care about it. Maybe recommending use
of these extensions for their sites will convince them to pay
attention to supporting non-JavaScript access.</p>

<p>Therefore we invite volunteers to pick a site and write a browser
extension to make that site function, assuming that LibreJS blocks the
nonfree JavaScript sent by the site.
To get an idea of how to do it, you can check <a
href="https://jahoti.tilde.team/browser-extensions/index.html">examples
of site extensions</a> that already exist.</p>

<p>The first thing to do is to look briefly at the licenses of the
JavaScript files on the site. Some of them might actually be free
software. If some of the JS code sent by the site is free, you can
include it in your extension, changing it as needed.</p>

<p>Next, check whether the site has published an API. If so, it is best
to communicate using the API, if that can do the job. Otherwise, you
need to use the browser debugging facilities to figure out what data
and commands the JavaScript code sends to the server—in
effect, its undocumented API.</p>

<p>The way to avoid infringing copyright on the site's own JavaScript
code is not to study the code. Not any part of it, not even once.
If you did not read the code, it follows that you did not copy any of
it. Look only at the licenses.</p>

<p>These extensions should be honest—they should not
“cheat.” If the site's JavaScript asks the user for
information and sends it, the extension should ask the user for that
information and send it. If the site asks per (<a href="#ft1">1</a>)
to check a box to agree to XYZ, the extension should ask per to check a
box to agree to XYZ. The extension should faithfully pass on whatever
responses the user enters. If the site sends a cookie, the extension
should let it be handled according to the browser settings for cookies.</p>

<p>It is impossible to implement real security via JS code sent to the
user, but whatever the site does to try to implement something
resembling security, the extension should carry out faithfully. In
particular, if the site asks the user to answer questions to prove
perself not to be a robot, the extension should show per the same
questions, get the answers, and send them in—thus enabling per
to demonstrate that perse is human.</p>

<p><a href="https://github.com/JeffCarpenter/librecaptcha"> href="https://gothub.projectsegfau.lt/JeffCarpenter/librecaptcha/">
Jeff Carpenter's librecaptcha</a> might be useful if the
site sends a captcha. We will start a project to convert it to JS,
and we will need volunteers for that, so please write to me if you are
interested in helping.</p>

<p>Meanwhile, if the site's JS code gathers information surreptitiously,
it is admirable to thwart that snooping. One idea is to ask the user
what answer to return—for example, “The site is trying to find
out your location. What do you want to tell it?” But it would be
good to avoid asking the user frequently or repeatedly.</p>

<p>When you have an extension working, please mail a copy to the GNU
Project at <a
href="mailto:js-extensions@gnu.org"><js-extensions@gnu.org></a>.
You can also register it in Firefox's extensions list, if you can stomach
running the nonfree software to do that.</p>

<p>We have set up a mailing list, <a
href="https://lists.gnu.org/mailman/listinfo/js-extensions-discussion">
js-extensions-discussion</a> where
you can talk with others who are developing extensions.</p>

<p>Once things are going, we would like to set up a savannah.gnu.org repo
where we will put the extensions that are working. To do that, we
need a volunteer or two to manage it. We expect this task not to be a
lot of work; the reason to have two is for redundancy.</p>

<p>We could also have a Savannah project which you could (if you wish)
use for developing an extension; that too would require volunteers to
take care of it.</p>

<p>Here are some suggestions for sites to write extensions for.  (Some
are commercial and some are not—that distinction is not
significant for this issue.)  However, if some other site interests
you more, by all means go where your interests take you.</p>

<h3>Sites for accessing information and publications</h3>

<p>The initial goal is to handle anonymous access.
To handle logging in, and logged-in access,
is going beyond the short-term call of duty.</p>

<ul>
<li>accuweather.com
(for looking at its weather info)</li>

<li>pubmed.ncbi.nlm.nih.gov
(for downloading papers)</li>

<li>groups.google.com
(for finding and viewing postings on groups)</li>

<li>tripadvisor.com
(at least to show a restaurant's full menu)</li>

<li>blogger.com
(to view the blogs)</li>

<li>
britishmuseum.org/collection (to view the collection)</li>

<li>pdr.net
(to view the information on the medicines)</li>

<li>reiseauskunft.bahn.de
(to view train schedules, at least)</li>

<li>
rgs.org/about/our-collections/online-exhibitions
(to view the exhibitions)</li>

<li>worldcat.org
(to look up books)
<p style="margin-left: 3%">As an example, see <a
href="https://www.worldcat.org/title/gnu-emacs-manual/oclc/232354882">
this entry for the GNU Emacs manual</a>. Please note on the page the
heading “Find a copy in the library.”
Without running the proprietary JavaScript, the only content under that
heading is a loading spinner GIF and the text “Finding libraries
that hold this item…” The actual library availability
information for the given book is absent.</p>
</li>

<li>scribd.com
(to read texts)</li>

<li>soundcloud.com
(to listen to audios)</li>

<li>documentcloud.org
(to view documents)</li>

<li>bandcamp.com
(to listen to or download music)</li>

<li>manualslib.com
(to download manuals)</li>

<li>npr.com
(to listen—try using its API)</li>

<li>nasa.gov
(to look at the publications, including photos and videos)</li>

<li>reddit.com
(for reading, at least).  At present, you can do this
by using <a href="https://old.reddit.com">old.reddit.com</a>.</li>
</ul>

<h3>Petition-signing sites (to let the user sign)</h3>

<ul>
<li>freedomunited.org
(appears to “succeed” but no confirmation comes back)</li>

<li>sumofus.org
(the old extension from years ago no longer works)</li>

<li>change.org
(warning, this site's JS is very complex)</li>

<li>afsc.org</li>

<li>act.ran.org</li>

<li>coworker.org</li>

<li>defenders.org</li>

<li>earthjustice.org</li>

<li>amazonwatch.org</li>

<li>signherenow.org</li>

<li>moveon.org</li>

<li>publiccitizen.salsalabs.org</li>

<li>action.splcenter.org</li>

<li>secure.everyaction.com</li>

<li>amnesty.org</li>

<li>addup.sierraclub.org</li>

<li>ucsusa.org</li>

<li>engage.drugpolicy.org</li>

<li>engage.us.greenpeace.org</li>
<!-- Redirects to https://www.greenpeace.org/usa/ -->
</ul>

<h3>Other kinds of sites</h3>

<ul>
<li>house.gov
(for viewinng pages and sending mail to representatives)</li>

<li>whitehouse.gov
(for communicating with the White House and with the webmasters)</li>

<li>Disqus comments,
found in various websites (for posting a comment)</li>

<li>regulations.gov
(for commenting on proposed US regulations)</li>

<li>surveymonkey.com
(for answering surveys)</li>

<li>coworker.org/start-a-petition (for starting a petition)</li>

<li>wetransfer.com
(ideally for upload and download, but just downloading would be a good
first step)</li>

<li>stripe.com
(for entering payments for other sites)</li>
</ul>

<h3>Sites that people have handled in this way</h3>

<ul>
<li>docs.google.com
(for downloading documents)</li>

<li>pay.gov
(for registering a DMCA contact)</li>

<li>rsf.org (for signing petitions)</li>

<li>theonion.com
(for looking at images and audio)</li>

<li>goteo.org (for payments)</li>
</ul>

<div class="infobox">
<hr />
<h3>Footnote</h3>
<ol>
  <li id="ft1">The author uses the gender-neutral third person singular
pronouns and possessive adjective “perse,” “per,”
 “perself,” and “pers.”</li>
</ol>
</div>
</div>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">

<p>Please send general FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF.  Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">
        <web-translators@gnu.org></a>.</p>

        <p>For information on coordinating and contributing translations of
        our web pages, see <a
        href="/server/standards/README.translations.html">Translations
        README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations
README</a> for information on coordinating and contributing translations
of this article.</p>
</div>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 4.0.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->

<p>Copyright © 2021 2021, 2024 Free Software Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivatives 4.0 International License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->

<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2024/11/06 10:43:09 $
<!-- timestamp end -->
</p>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>