I think that websites do, legally, have the right to refuse you service if you run NoScript and some websites go through crazy hoop to exercise that right. I _suspect_ that using NoScript to alter the page is actually illegal under current intent since that usage could cause the software to misperform and potentially cause damages and it violates the agreed upon usage contract on that site. That said, it's _mostly_ unenforceable on a technical level (usually it's at least not cost effective to do) and I personally think it's unethical to force people to run malware to view your content - it needs a clearer definition in the law though, all this stuff is stupid hazy.
Yet some would say the pages get altered by the scripts that stuff in the awful ads
In any case, you don't need an add-in to disable scripting. Hell, use curl to fetch the damned page. That's about as "pure" a way of fetching one as you can get.
The day they rule that curl is illegally blocking ads is the day I become a monk.
IMHO, ad-driven business model is OK, but implementation matters. If site will _serve_ me with ads, I will use it. If site will try to abuse me with ads, then I will try to shield me from this abuse.
I have ideas how to solve Spotify problems, but it looks like Spotify employee are downvoting opponent comments to death, so they will have my f*ck instead of hint.
Do we have an obligation to allow script in our browsers? >90% of my "news reading" on the internet is done with NoScript running; from my point of view it's all good, no ads, no GDPR pop-ups, pages load quickly, fewer worries about tracking.
It's probably not what publishers want, though.