News for hackers. Stuff that matters.
Re:Developers are your users too – a defence of 'View Source' by zeta0134 on Saturday June 13, 2020 @08:24PM (#23514044)
I think one of the strongest arguments against view source has got to be advertising. For example, I like to hide distracting elements of web pages so I can focus on the text. Here is the (current) uBlock rule to block the sticky clappy hands thing that only logged-in Medium users can use anyway:

> ##.iq.n.ip

Those class names will change next week when they push an update, breaking the rule and making me dig out the eyedropper again. This isn't that effective against ads of course; any page with an obnoxious ad that defeats my filter gets closed, and the community-run filters pick up the new rule changes basically same day. All it really does is harm the usability of the site for those users who need the accessibility tweaks.

Re:Developers are your users too – a defence of 'View Source' by RickS on Saturday June 13, 2020 @09:47PM (#23514462)
Amen. I wish more developers realized that without deliberate effort, minification == obfuscation.

I've written small custom scripts to reformat and enhance redfin's data when I was househunting, to declutter (read: adblock) pinterest, etc etc.

Navigating markup is a nightmare when each node has 10 minified classes with no obvious meaning, and such frequent overlap that it's difficult to infer from usage alone. And that's before the weekly rotation.

---

aside: I wonder if there's appetite for a tool that takes snapshots of markups/css and tries to automatically update old -> new classes.

Re:Developers are your users too – a defence of 'View Source' by gfxgirl on Saturday June 13, 2020 @10:57PM (#23514737)
You get around this by shaming them into adding aria tags for the accessibility. The tags have to be meaningful to be useful which you can then use as your selector