Please disable JavaScript to view this site • Hacker News Board

Re: Please disable JavaScript to view this site

#271

Post by err4nt » Tue, Dec 01, 2020, 1:01 AM UTC

Arnavion wrote: post #255

err4nt wrote: post #249

Earlier quoted context omitted.

Abusing HTML form inputs as a way to store application state in DOM is hostile to usability and accessibility - please don't do this for any sites humans need to use. HTML does have progressive disclosure elements built in with ` ` and ` ` which work without JS (I was hoping the demo was showing that or something like it)

Those HTML elements are radio buttons being used to choose between options of OS, mail server, etc. Each radio button is associated with a label that contains the correct text. Selecting a radio button unambiguously makes a `display:none` element no longer be that. What part of it do you think is bad for usability or accessibility?

Everything you just said - these form inputs aren't related to a form, and assistive technology won't have any clue about the clever CSS selector hacks and what their effects are.

If you want to build something that's nice for humans and machines, look up best practices for this sort of thing - plenty of information is widely available on how to build things in usable and accessible ways (and it's simpler to do it correctly than to use these 'hack'-like workarounds anyway!)

Re: Please disable JavaScript to view this site

#272

Post by jachee » Tue, Dec 01, 2020, 3:06 AM UTC

XCSme wrote: post #253

jachee wrote: post #182

Earlier quoted context omitted.

My understanding is that JavaScript is the primary mechanism used in browser fingerprinting and cross-site user tracking/"analytics". Isn't that a rather large privacy and (personal, if not specifically "cyber") security risk?

Actually, the main and most used mechanism of cross-site user tracking and "fingerprinting" are cookies, which do not require any JS to work.

How does cross-site user tracking do its thing?

Re: Please disable JavaScript to view this site

#273

Post by XCSme » Tue, Dec 01, 2020, 9:31 AM UTC

jachee wrote: post #272

XCSme wrote: post #253

Earlier quoted context omitted.

Actually, the main and most used mechanism of cross-site user tracking and "fingerprinting" are cookies, which do not require any JS to work.

How does cross-site user tracking do its thing?

Set a cookie using HTTP headers.

Use a tracking pixel (eg. image) to make further requests and cookie will be included in the request.

Re: Please disable JavaScript to view this site

#274

Post by account42 » Tue, Dec 01, 2020, 11:18 AM UTC

derefr wrote: post #251

dreamcompiler wrote: post #167

Earlier quoted context omitted.

On a great many web sites I have to spend the first 60 seconds on the site clicking on "X" boxes in popups to make them go away. In many cases there are actually several layers of popups obscuring the content, and some are delayed so they only pop up after you start reading the content. No I do not want to subscribe to your mailing list. No I don't want to take your survey. No I do not want to "chat" with your bot-pr…

That may have been true whenever you last evaluated your choice, but I find that today, on-load modals are mostly burned into the HTML. With Javascript disabled, rather than not being there, they're instead always there, impossible to get rid of.

> With Javascript disabled, rather than not being there, they're instead always there, impossible to get rid of.

Inspect element -> remove

Browsers should really add "remove element" directly to the context menu.

Re: Please disable JavaScript to view this site

#275

Post by jorgelgbtq » Tue, Dec 01, 2020, 2:05 PM UTC

Arnavion wrote: post #151

mikedilger wrote: post #127

Wow, something is wrong with uMatrix. I have uMatrix with 1st party javascript disabled by default. Yet this site says "Please disable JavaScript to view this site." To be sure, I curled the source and hosted it elsewhere, and my browser (firefox 84.0b4 on linux with uMatrix) still runs the JavaScript.

The JS is inline. Neither uM nor uBO static rules block that. The only way to block it is a uBO dynamic rule `no-scripting: $hostname true`, which you'll also need to be able to render the ` ` content anyway. BTW, you probably want to move off of uM given gorhill has abandoned it in favor of uBO. (I converted all my rules to a mix of uBO dynamic rules for JS and static rules for everything else, except for cookies wh…

LOL just because uM was abandoned by Gorhill doesn't mean the extension stops working. Gorhill is a moron of the nth degree but his software is great.

Re: Please disable JavaScript to view this site

#276

Post by jorgelgbtq » Tue, Dec 01, 2020, 2:06 PM UTC

pugworthy wrote: post #187

dreamcompiler wrote: post #167

Earlier quoted context omitted.

On a great many web sites I have to spend the first 60 seconds on the site clicking on "X" boxes in popups to make them go away. In many cases there are actually several layers of popups obscuring the content, and some are delayed so they only pop up after you start reading the content. No I do not want to subscribe to your mailing list. No I don't want to take your survey. No I do not want to "chat" with your bot-pr…

I personally visit "a great many websites" daily, and rarely have this problem. Maybe it's uBlock doing it's job, or maybe it's the kind of site you go to?

You sound like a cunt, I bet you're an ace to work / live with. LMFAO

Re: Please disable JavaScript to view this site

#277

Post by jorgelgbtq » Tue, Dec 01, 2020, 2:08 PM UTC

square_usual wrote: post #190

judge2020 wrote: post #177

Earlier quoted context omitted.

In case the OP wanted to know exactly how Brave's adblock is different from uBlock Origin instead of a link to the marketing page with links to other things like cryptocurrencies: Brave's browser claims a speedup over AdBlock plus, but was inspired by UBO, so the performance is fairly similar, but is baked into the browser instead of being an extension. > We therefore rebuilt our ad-blocker taking inspiration from uB…

It's also written in Rust for performance.

LMFAO, it is written in Rust for memory safety, not performance. RING RING, the clue phone is for you.

Re: Please disable JavaScript to view this site

#278

Post by jorgelgbtq » Tue, Dec 01, 2020, 2:08 PM UTC

scaladev wrote: post #222

sam0x17 wrote: post #220

Earlier quoted context omitted.

With uBlock origin you're at the whim of the changes Google pushes through to chrome/chromium to nerf it.

What are you talking about? uBlock Origin is not tied to Chromium, and is not controlled by Google (unlike Brave which is just a fork of Chromium). Jesus, why does everyone these days automatically assumes that everyone else is using Chrome or Chromium? It's almost as crazy as calling Windows a "PC".

Sounds like you could use some anger management classes.

Re: Please disable JavaScript to view this site

#279

Post by jorgelgbtq » Tue, Dec 01, 2020, 2:13 PM UTC

Arnavion wrote: post #195

wuuza wrote: post #193

Earlier quoted context omitted.

Is there a guide for moving from uMatrix to uBO? uMatrix works exactly how I want/expect... BTW, the site works as expected with my Linux/Firefox/uMatrix setup... the inline scripts are disabled by default and I see the page content. I'm not sure why GP had issues.

For a uM rule like: foo.com bar.com css allow which means "allow foo.com to fetch css from bar.com", the corresponding uBO static rule is: @@||bar.com^$domain=foo.com,css,allow The full list of things that can be allow/block'd by uBO is at https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#... I have a "block everything by default" rule at the top that's: *$css,font,frame,media,object,ping,script,websocket,x…

I bet you're scared of your own shadow too LMFAO

Re: Please disable JavaScript to view this site

#280

Post by sam0x17 » Wed, Dec 02, 2020, 2:24 AM UTC

scaladev wrote: post #222

sam0x17 wrote: post #220

Earlier quoted context omitted.

With uBlock origin you're at the whim of the changes Google pushes through to chrome/chromium to nerf it.

What are you talking about? uBlock Origin is not tied to Chromium, and is not controlled by Google (unlike Brave which is just a fork of Chromium). Jesus, why does everyone these days automatically assumes that everyone else is using Chrome or Chromium? It's almost as crazy as calling Windows a "PC".

Google controls the frontend APIs uBlock origin is allowed to use, and they have pushed changes numerous times in the past (covered on HN) to intentionally nerf uBlock origin because it hurts their bottom line.