googleimagesrestored VS pixiebrix-extension

i very much care about supporting firefox users. for example, i maintain a separate, mozilla-signed, manifest v2 version of an XPI of an extension i made [0] just so firefox users can keep using it. i do so even though this compromises my own ideals about not wanting to use 2FA out of principle.

[0] https://github.com/fanfare/googleimagesrestored/releases

if you use ublock origin, you can permanently remove pinterest results in google images with the following filter:

www.google.com##.isv-r:has-text(/pinterest.com/)

shameless plug: i've been maintaining a browser extension for a couple of years called 'google images restored' [0] which reverts google images to how it was before 2019. that extension, mixed with the ublock origin filter removing unwanted domains (pinterest, alamy, 123rf, etc), makes google images enjoyable again for me.

[0] https://github.com/fanfare/googleimagesrestored

Not an answer, but for context, the author removed the extension from AMO to avoid the requirement to use multi-factor authentication on their Firefox account: https://github.com/fanfare/googleimagesrestored/commit/8e77eb0e4314df9a64c8d3df2eb04c9868795085

If you don't want to actually write the code and deal with the browser webstores, you can also use an "extension builder" tool like https://www.pixiebrix.com/ to call APIs, move data around, and build simple UIs.

We have some logic here for parsing tables to JSON: https://github.com/pixiebrix/pixiebrix-extension/blob/main/src/utils/parseDomTable.ts (code is AGPL). Given a table, it can detect the table orientation and parse most table structures.