Very neat, but recently I've tried my best to reduce my extension usage across all apps (browsers/ide).

I do something similar locally by manually specifying all the things I want scrubbed/replaced and having keyboard maestro run a script on my system keyboard whenever doing a paste operation that's mapped to `hyperkey + v`. The plus side of this is that the paste is instant. The latency introduced by even the littlest of inference is enough friction to make you want to ditch the process entirely.

Another plus of the non-extension solution is that it's application agnostic.

▲

informal007 2 days ago | parent | next [-]

Smart idea! Thanks for sharing.

If we move the detection and modification process from paste to copy operation, that will reduce in-use latency

	▲	postalcoder 2 days ago \| parent [-]
		That's a great idea. My original excuse to not do that was because I copy so many things but, duh, I could just key the sanitizing copy to `hyperkey + c`.

▲

bjord 2 days ago | parent | prev [-]

out of curiosity, what's the motivation behind trying to reduce your extension usage everywhere?

▲

postalcoder 2 days ago | parent [-]

Multiple things: 1) extensions are overly permissive, 2) so many of them are sold to shady entities without peep from the developer, and 3) it's never been easier to generate my own tooling.

▲

bjord 2 days ago | parent | next [-]

brutal. I just typed out a much longer response and lost it when my time wasting extension saw the url change (time for a text area cache extension?)

you might find this useful: https://github.com/classvsoftware/under-new-management

my port (and now fork): https://github.com/maxtheaxe/under-new-management-firefox

they currently (PRs are welcome!) only check listing info. mine doesn't route requests through an external (non addon store) server.

a couple PRs are overdue on mine due to linting making the diffs impossible. I'll get to it. (see the wxt-migration branch)

▲

sgc 2 days ago | parent | prev [-]

I just download the extension file, check it out, and install it locally. No worries about future updates until something breaks (doesn't tend to happen).

▲

bjord 2 days ago | parent [-]

at least on firefox, you can also just disallow automatic updates

▲

sgc 2 days ago | parent [-]

I want to see the source, and I don't want to worry about future browser changes messing with my settings..

	▲	bjord a day ago \| parent [-]
		fair enough. I'll add that one fantastic use I've found for LLMs is quickly checking the source of a given addon (though obviously this is no replacement for a real audit or finely-grained permissions). I'd be doing this type of thing a lot more if browsers didn't make it difficult to load unpacked addons (in which case I could be modifying things I didn't like on the fly).