tridactyl VS policy-templates

View on GitHub

You can achieve this with native messaging [0] in tridactyl [1]:

https://github.com/tridactyl/tridactyl/blob/850acdf2ca11018e...

It's really cool, I've added an option to open these windows in floating mode automatically in my sway config through another application name iirc. Ans then I press a simple shortcut, and it opens my editor (Helix) with the already entered text and once I close it, it'll transfer the text from that temporary file which was open in your editor to the the input field/textare again.

[0] https://github.com/tridactyl/native_messenger

as a pentadactly widow, i would recommend to anyone that is coming back to firefox tridactyl https://github.com/tridactyl/tridactyl

is it the same? no.

but is it close? hell yeah. it really helps me with productivity!

> I can't even edit the code that is taking focus and hijacking shortcuts!

You can remove the shortcuts pretty easily with a userscript, see lines ~410-440 here for inspiration: https://github.com/tridactyl/tridactyl/blob/2eaba7e4ceec6de5...

Wait until you find out about Tridactyl [0], which, among a plethora of other features, can activate a command line where you can perform all these searches (for example, `:tabopen` will list and activate fuzzy search of all opened tabs).

[0] https://github.com/tridactyl/tridactyl

You might be interested in using a browser plugin like Tridactyl instead, I’ve been using it for months now absolutely no complaints, no need to “simulate” the mouse anymore just use page hints to click exactly the html element you want to https://github.com/tridactyl/tridactyl

Nearly everything on reddit uses reddit-flavored markdown. Backticks for inline code, as you discovered, but indent code blocks with four spaces. I use a browser extension so that I can edit all my comments in Vim, so manipulating this markup, especially code blocks, is easy.

I use tridactyl but the limitation of firefox API prevents addon to even change the built-in shortcuts: https://github.com/tridactyl/tridactyl/issues/1428.

There is no such thing as a "known trusted extension" ever since they killed sideloading extensions and forced auto-updates. 10 years ago not force updating extensions was also a thing they moved behind a flag, and then just dropped.

Also - if you want to blacklist certain extensions from certain sites, you abso-freaking-lutely can already... see: https://github.com/mozilla/policy-templates/blob/master/READ...

you want the `restricted_domains` field.

It gets worse - Mozilla is the fucking worst at checking submitted extensions. They tried to the play into the whole "app store" thing that Google/Apple were doing, but those are justifiable cost centers at those two companies in a way that just doesn't work for a player like Mozilla.

Mozilla's store checks for extensions are fairly pathetic. You can submit a near empty shell with excessive permissions, get approved the first time, then auto-update to a new release (which will deploy to users immediately thanks to auto-updates). That new version has to pass a battery of useless automatic SAST checks, which will happily highlight all sorts of things it doesn't like (it flags words like "hello" because it contains a curse word) but which won't do shit to check if you're hoovering up credentials, browsing data, tracking users, etc.

If you're unlucky, at some point in the next 24 months you'll trigger a real review from Mozilla and get caught.

To be blunt - I have 15 years experience writing extensions. I don't like Google. If you think Mozilla is better you're wrong.

You can do that with policy templates. Use the Discussion tab at the top of the GitHub page if you need help setting them up.

Policy Templates for Firefox

They very well could do this for a a company that requires really strict privacy and security, but unfortunately in its current state Firefox doesn't have nearly the corporate sysadmin-friendly tooling that Chrome and especially Edge do.

When I was tasked with implementing CIS browser hardening policies at a previous job a few years ago, this was just a matter of enabling some Group Policy template settings for Chrome and Edge, but for Firefox this involved distributing a prefs.js file to all the workstations. In any corporate environment it's very likely going to be point and click Windows admins that are implementing browser standards, who tend to be allergic to anything resembling code and are already used to using GPOs for just about everything.

Yes, Firefox does have GPO templates but it's not nearly as rich as Chrome and Edge. Edge has even more GPO templates than does Chrome iirc, Chrome already had a lot to begin with and then Microsoft added even more of their own on top of that.

https://github.com/mozilla/policy-templates/blob/v4.11/READM...

https://learn.microsoft.com/en-us/deployedge/configure-micro...

That alone already puts Firefox at a huge disadvantage for corporate deployment, the other thing that makes it even less attractive, even to companies where privacy/security is a huge requirement (like my previous job) is that Edge is already bundled with the OS, and is one less thing that needs to be manually patched. In high security corporate environments, just keeping things patched is always a huge task so it's very hard to convince someone that they need to put in more work to keep an extra piece of software patched (which is already very difficult considering how frequently browsers are updated). To make things even worse, just about all vendors will only support Chromium-based browsers for whatever SaaS they sell you, so Firefox is a nonstarter for getting support, even if it will work just fine 99.9% of the time.

For all these reasons, I lost the battle to keep Firefox around, which is a huge shame because of how much I love it and wanted to fight the Chromium monoculture. So I guess for a corporation to support Firefox despite how corporate-friendliness the alternatives are, they'd have to reaaaally want to.

You can see the relevant JSON code in the changelog. As I said, you can post a comment on this page to remind Mike to update the documentation for policy templates.

This GitHub repository has a Discussions tab where you can ask questions about deploying Firefox: Policy Templates for Firefox.

Check out the official documentation here: Policy Templates for Firefox. You can use the Discussions tab if you have any questions.