help-librejs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Native messaging


From: Yuchen Pei
Subject: Native messaging
Date: Mon, 30 Oct 2023 22:59:30 +1100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)

Hello,

Native messaging[1] allows a web extension to communicate with arbitrary
programs on the local system. This opens many possibilities as we are no
longer restricted to the firefox environment which is far less
customisable than GNU/Linux itself, including the (local) logging of
librejs reports for webpages that could help with the following:

- build a database of (fully or partially) librejs-compliant websites,
  as well as free but non-compliant ones.
- gain insights of the type of free scripts that librejs could not
  recognise. What are they like and what are the most common ways they
  are labelled? Is there a way to recognise most of them without
  introducing false negatives?

[1] 
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging

I pushed a PoC implementation of such a logger in the
native-messaging-app branch[2], as per the commit message, it works as
follows:

- run ./build.sh
- install the built librejs.xpi as a temporary extension[3]
- check the librejs version is 7.21.2
- load some sites e.g. <https://fsf.org>, <https://archive.org>, and
  the reports should be logged into /tmp/librejs.log

[2] https://git.savannah.gnu.org/cgit/librejs.git/log/?h=native-messaging-app
[3] 
https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/

Best,
Yuchen

--
Timezone: UTC+11
PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
          <https://ypei.org/assets/ypei-pubkey.txt>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]