![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Don’t know myself as I have no use case for that setup, but it is a well known setup since several years. If teh performance was bad it wouldn’t be recommended as an alternative as often.
Don’t know myself as I have no use case for that setup, but it is a well known setup since several years. If teh performance was bad it wouldn’t be recommended as an alternative as often.
JBOD via mergerfs and snapraid on top for parity is a possible solution.
Relevant part from the blog post:
What are we doing differently in Firefox? WebRequest
One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.
Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.
Same here, started about the same time. Sadly the crashes aren’t catched and logged…other crashes appear under settings > about Firefox> crashes.
It’s not even site related - after restarting firefox the sites load as expected.
Interesting! I experience this bug on my windows machine every now and then but wasn’t bothered too much with it. Nice to get some background info on that.
Ah, nice, will try that out. I guess the success rate depends on the way the sites filte email addresses.
Thanks for the reply!
That’s something I’m doing too. I wish there was a nicer way though.
Thanks for the reply!
So, a lot of websites filter out known trash mail domains and won’t allow any of their email addresses for sign up. I don’t see that Simplelogin or Addy can circumvent that (beside using a custom domain which however will be linked to your name via the registrar).
How do you manage websites with such restrictions?
Have been using it for years, it never failed me. Quality software.
Still using the pwa, I feel no need to switch to the app. Will test later anyways.
Wefwef/Voyager still feels superior to me. Will still test sync for a bit but I couldn’t find any unique selling point yet.
It’s awesome! I’m running this since years without any problems.