I guess so, it would still be a problem. Once one extension is caught, it should be simpler to catch the rest.

It’s harder to quickly switch stuff up when you need to send the devs new code to put in

Don’t extensions get reviewed by the various stores? I’d imagine an automated check could catch malicious integrations like that.

Maybe not right away, but once they catch wind of one shady extension they could just search the store for any other ones.

You’re welcome, hope it helps!

The basic features should work with Lemmy and Kbin, but some of the new ones are unique to Lemmy for now, such as the error page replacement. I’ve found Kbin a little harder to work with because while it’s more flexible, it’s harder to make sure I’m avoiding unintended actions.

I don’t think there are any limitations with behaw, at least with the current features.

I tested with mobile Firefox on an older version and it did work. However since you have to jump through hoops to install the extension in the first place, I haven’t looked into it much more. If you try to install it from the store on mobile, it should say that it isn’t compatible. :)