Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Mmmm....okay, but the parent comment I was responding to does have a point in that there are some benefits to blocking Javascript above and beyond just trying to deal with tracking. Like, if you're on a laptop, there are sites that will burn a lot of CPU time -- and hence battery life -- doing nothing useful. Or, on an older machine, it can speed up page loading.
My issue is just that unless you're going to turn it on yourself on a site-by-site basis, killing off Javascript breaks too much of the Web today. It was a viable option to just have on back when there was a meaningful portion of the world that didn't have Javascript available and web developers designed pages to deal reasonably with its absence and you were willing to deal with flipping it off on specific sites to deal with the occasional breakage...but today, it's a huge portion of the Web that doesn't work without Javascript.
No don't get me wrong. uBO doesn't block all JavaScript. It has lists with individual scripts that are known to be used for ads or tracking, and these get blocked. All the other scripts load as usual. This already improves website load times and probably also battery life. Another interesting solution for reducing CPU load may be DNS based blocking. That way, the CPU is not impacted at all, the browser tries to load the script but it just silently fails, because the DNS records for the tracking and advertisement servers won't be provided.