Libredirect is a manifest v2 extension (can’t be published on chrome store) and has permissions for all_urls, predirect is a manifest v3 extension and only has permissions for necessary domains
No, yes, It depends- for my simple use case of redirecting embeds and links, it is probably faster by using declarativenetapi instead of heavier webrequestblocking api
The sites to be redirected shouldn’t be already pre-selected by the extension. E.g I am logged in to Twitter on my browser and installing this extension will unintentionally redirect me to some instance.
And also, maybe the sites for redirection should be added by the user instead of the extension making assumptions. With libredirect I can click more options and add the site to Chrome’s handler.
It has a reasonable default of reliable privacy frontends but I may add an onboarding step(already in firefox due to more restrictions in their manifest v3 than chrome) for selecting sites
While at the same time closing all PRs indiscriminately, even the ones that are just trying to update the repo from its decades old JavaScript syntax (and get support in the comments)
I hate adware and nagware, but I respect it here. From the get-go you know this is a space where this person gets paid. This is just an extension of that.
I’ve used it for a few documents and loved it. There’s a learning curve, but I’m glad they’re not carrying the technical debt latex has, so it’s definitely worth the effort IMO.
github.com
Oldest