Closed fabcard closed 2 years ago
Hey there. Thanks for using BetterFox!
Can you go to about:config
and search for network.preload
. Toggle that preference to true
, then try visiting the site again.
The user.js enforces the prefs inside it every time you restart Firefox, so if this is a site you go to often, you can:
user.js
MY OVERRIDES
user_pref("network.preload", true);
This is the second site that breaks when this pref is false
. I'm unsure whether it is bad site design or a bug on Mozilla's end.
Edit: I have filed a bug report with Mozilla. https://bugzilla.mozilla.org/show_bug.cgi?id=1754264
Hello @yokoffing Thank you for your reply. Yes, that did fix the problem. Also, thank you for sending to Mozilla the bug report. So, is that an issue with Firefox or with the site? Is that command (network.preload) set to false very important? I use that site quite often. Again, thank you for your help and awesome work on BetterFox.
So, is that an issue with Firefox or with the site?
I'm unsure. Since another site had an issue related to this pref as well, I opened a bug report with Mozilla so they can determine the source of the issue.
Is that command (network.preload) set to false very important?
Read this. Out of all the prefs under Speculative Connections
, this is one pref I'd always leave disabled since:
// A browser is required to download the resource specified in
<link rel="preload">
. With other tags described here, // a browser is free to skip preloading the resource if it decides to (e.g. if the network is slow). // [WARNING] Leaving this enabled will interfere with content blocking, especially with cosmetic filters.
In other words, network.preload
will always download resources tagged with this; they will always be fetched. Unfortunately, a lot of things linked with network.preload
are resources you may not want (ads, pop ups, tracking scripts, etc.). Definitely best to leave it disabled, but if you use that site a lot, I can see why you'd want to leave it enabled.
You could manually change it to true
before you visit the site in about:config
without changing your user.js
, but if you visit the site everyday, that would be annoying. Another suggestion is that you could also use a different browser for that site.
I noticed that a Firefox add-on that I use is no longer working. Here is the link for it:
https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/
I downloaded the extension and translated the page successfully from Spanish to English on https:/elpais.com/
. It is working for me, so I don't suspect that this is a user.js
issue.
sometimes getting this error: MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE
What's more safe?
Your trading additional security (however, most anti-virus programs are garbage!) for less privacy (it's inspecting your web traffic).
If you feel like you safer allowing your anti-virus program to inspect your web traffic, then you can add user_pref("security.cert_pinning.enforcement_level", 1);
to the MY OVERRIDES
section in the user.js.
which of the above options you recommend me to take, please?
My opinion is that you don't need to pay for any anti-virus software in 2022. Windows Security (which includes anti-virus protection), Microsoft Update (regularly updating your operating system with the latest security patches), using a content blocker like uBlock Origin and/or DNS-filtering like NextDNS, and not clicking on random, suspicious sites — is all you need for security.
You must decide what you're most comfortable with.
will be the NextDNS free version enough?
Depends on your use case and how many people are using one profile. Free is good for up to 300k queries/month. It's not bad to pay the $2/month or $20/year to have your cell phone + desktop + family devices all protected. https://nextdns.io/pricing
Will I need all those filters from
https://github.com/yokoffing/filterlists#recommended-filters-for-ublock-origin
When you are just starting out learning about these things, it's best to keep it simple so that you do not have to troubleshoot site breakage. I'd recommend you do something like this for now:
You can add on more filter lists once you've had time to become familiar with these kinds of tools, if desired.
if I use NextDNS
You need to use uBlock Origin despite whether or not you use DNS-level blocking (e.g. NextDNS, Pihole, AdGuard Home): "Since [DNS-level blocking] cannot block youtube ads, hide ad-placeholders, or ads being served from the same domain as the wanted content, a browser add-on ad-blocker (Eg. uBlock Origin or the AdGuard Browser extension) is recommended." source
uBlock Origin blocks trackers before they make it to the DNS-level, so that's yet another advantage to using a content blocker on top of DNS-blocking.
BEFORE YOU BEGIN
I have attempted the following troubleshooting suggestions:
REPORT
Describe the bug The website https://www.mg.superesportes.com.br keeps loading and shows nothing on screen. I tried all the suggestions above, but no luck. Site was working fine before using your user.js. I restored the backup from my old profile and all works fine.
To Reproduce Steps to reproduce the behavior:
Expected behavior Site opening normally.
Desktop (please complete the following information):
Additional context It's my first time using a "custom" user.js. and I don't know much about the commands inside it. If you could let me know which command is causing the issue, please let me know, so I can change it. Thanks in advance.