InformAction Forums

If I search "noscript" in about:config, I get no results.

Where the NoScript preferences are stored now?

…\profile\storage-sync.sqlite
…\profile\browser-extension-data\{73a6fe31-595d-460b-a920-fcc0f8843232}\storage.js

Click "Export" -> noscript_data.txt

storage-sync.sqlite

Mh. And what if I want to change manually I NoScript option? Can I edit storage.js or must I edit the sqlite db?

This is due to the Firefox update?

> Can I edit storage.js…
Yes
… or must I edit the sqlite db?
After editing storage-sync.sqlite in Notepad++ — UNTRUSTED and CUSTOM are missing.
After editing storage-sync.sqlite in SQLiteDatabaseBrowserPortable — everything is fine.

It is better to edit noscript_data.txt and click "Export".
UPD: "Import", sorry.

fatboy wrote: ↑Sun May 19, 2019 10:31 am …\profile\browser-extension-data\{73a6fe31-595d-460b-a920-fcc0f8843232}\storage.js

I have no storage.js, but a storage.js.migrated. I think I could create a storage.js but it seems to me not safe.

fatboy wrote: ↑Sun May 19, 2019 10:31 am …\profile\storage-sync.sqlite

Editing a sqlite db only to change preferences? Absurd. This is a choice of Maone of a choice of Firefox?

fatboy wrote: ↑Sun May 19, 2019 10:31 am Click "Export" -> noscript_data.txt

This seems to me the simpler option, even if I'm forced to trust the developer that he exports all the settings.

Anyway, I remember that NoScript had a lot of hidden features, really interesting. Where they are gone?

fatboy wrote: ↑Sun May 19, 2019 12:16 pm After editing storage-sync.sqlite in Notepad++ — UNTRUSTED and CUSTOM are missing.

Well, you're lucky...

Offtopic: I suggest you Atom instead of Notepad++ and DBeaver instead of SQLiteDatabaseBrowserPortable

…\profile\browser-extension-data\{73a6fe31-595d-460b-a920-fcc0f8843232}\storage.js

So what, that is only a "backup" of pre-existing NoScript 5 data (if it existed at all), that is used, once (or maybe after a NoScript Reset?), to import into NoScript 10 ?
And after that, it's essentially immaterial?

choice of Maone of a choice of Firefox?

Well the fact that extensions cannot store their prefs in prefs.js, is Mozilla.
So then you have to work with the constructs that Mozilla (Quantum) allows.
I imagine that there may be several methods to accomplish that (?), but which, would be chosen by Maone.

Editing a sqlite db only to change preferences? Absurd.

I believe the "expected" way to do that would be through:
NoScript | Options -> Advanced --> Debug (ugly)
(The expected way, Mozilla way, is that you can't do that!)

NoScript 10 stores its data through chrome.storage.sync API, which uses storage-sync.sqlite as its backend.

The storage.js was the old backend of chrome.storage.local, which IIRC NoScript falls back to if chrome.storage.sync is not available. Starting with Firefox 66, chrome.storage.local is migrated to an IndexedDB-based backend - viewtopic.php?f=18&t=25102

Lucas Malor wrote: ↑Sun May 19, 2019 1:46 pm I remember that NoScript had a lot of hidden features, really interesting. Where they are gone?

Not implemented yet.

barbaz wrote: ↑Sun May 19, 2019 2:49 pmStarting with Firefox 66, chrome.storage.local is migrated to an IndexedDB-based backend - viewtopic.php?f=18&t=25102

Oh my god... this is a nonsense. "Improved startup time"? For few lines of JSON? So why Linux continues to use plain old text files for preferences, mh?

Firefox is SLOW because it's also written in Javascript in some of its core parts. Chromium is fast because is primarily written in C++. Until Mozilla Devs will not show the tragic truth, and will start to rewrite the bottlenecks in Rust, they can play with extensions and make the life difficult to everyone, users and extension developers, but they will never reach the speed of Chromium.

The ONLY reason I don't switched to Chromium is NoScript and the fact you can disable CSS files on-the-fly. But there will be the time someone will write NoScript for Chromium...

The ONLY reason I don't switched to Chromium is NoScript and

NoScript now also works in Chromium...

Oh. But I remember Maone wrotes that there was some big problems with the Chromium APIs, and a true blocking of JS was not possible. Something is changed in the meanwhile? NoScript on Chrome is effective as NoScript on Firefox?

They should be equally effective. NoScript for Chromium just has fewer features, e.g. missing XSS filter, because Chromium has more limited WebExtensions APIs than Firefox.

Mmmrf... I'll check any NoScript update to see if Chromium devs has added an API for XSS. For now I'll remain with Fx. For now...

Lucas Malor wrote: ↑Sun May 19, 2019 3:44 pm But there will be the time someone will write NoScript for Chromium...

The time has already come. The guy who wrote NoScript for Chromium is Giorgio Maone and the Chrome version can be found here.

The Chrome version misses XSS protection, though.

No XSS, no Chromium