this post was submitted on 07 Aug 2024
179 points (99.4% liked)
Asklemmy
43965 readers
1428 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
“Sponsor Block” is a game changer as well
I thought HTTPS everywhere was baked into browsers now and didn't need to be installed anymore? Is that not correct?
Yes i think firefox will do it if configured correctly
Yeah HTTPS-everwhere was important 10+ years ago, but now the main browsers all do this by default.
Isn’t NoScript redundant if you run UBO in medium mode?
If you go in ublock origin settings, scroll all the way down, you can toggle a setting that disables JS by default. On each site you can whitelist it by clicking ubo and enable JS.
I wasn't aware of this feature in UBO, but it doesn't seem to be quite the same. As best I can tell (with a quick test), UBO lets me turn all scripts on or off for a site. I don't see any sort of granular controls for selecting which domains to load scripts from (and I might just be missing it). For example, I may want to allow first party scripts to run on a site and maybe third party scripts from one or two domains. But, I don't want scripts from other third party domains to execute. It's very much a fine grained, least privileged style of script management. It's a lot more work, as you often have to spend a few minutes sussing out which domains need to be whitelisted to allow a site to reach minimum functionality; but, you are not often caught offguard by a site doing strange things on your system.
If you check "I'm an advanced user" in the settings, then hit the "More" button in the dropdown a few times it'll show the more advanced interface that lets you choose which third party domains to allow. It doesn't work quite the same since it blocks both content and scripts per site, but I find it good enough for my usage.
edit: You can technically block just scripts per 3rd party site, but it involves manually editing the content type for your rules in the settings. It's not part of the main interface, so I never bother using it.
Ah ok. I might give that a whirl then.
I don't understand your edit, how is more things doing the same thing better? It adds complexity, attack surface while taking resources.
Wow, you are really confused. The argument about the functionality being already implemented by Firefox was about https everywhere. This has nothing to do with adblocking and it does break some sites (the one still not using https) but you can still access them with a click.
Ah, that makes sense. Fair enough, I guess Incan disable that plugin now.