Live data from Hacker News

Chromium: Permit blocking of view-source: with URLBlocklist

chromium-review.googlesource.com

131–136 of 136 posts

Re: Chromium: Permit blocking of view-source: with URLBlocklist

#131
post #83
post #58

Earlier quoted context omitted.

Here's the link to vote, no registration required: https://www.mozilla.org/en-US/firefox/new/

~3/4 out of Firefox users have their analytics disabled if you're invisible your vote doesn't count anywhere ....

Do you have source for that?

Re: Chromium: Permit blocking of view-source: with URLBlocklist

#132

I have no idea what everyone’s problem is with this: - Active Directory/Group Policy/Managed Devices have hundreds of thousands of ways to lock machines down based on the IT staff’s needs (eg disabling USB ports, disabling devtools, etc) - You will not be affected by this in ANY way if you don’t have a managed machine - The feature is already there, just broken If you’re mad about this, get mad at your IT staff?

Speaking for myself, the problem is in the proposed solution to the issue that brought up this PR. It is to limit/change the way a fundamental browser feature works (view source), instead of simply fixing Google Forms website so that it does not expose answers in plain HTML code.

Extrapolate this mindset into the future and you have removal/alternation of other browser features because someone can not code a website properly.

Browser is supposed to be the 'user agent', the 'unstoppable force', and it has been that since the dawn of the web and it should stay that way.

Re: Chromium: Permit blocking of view-source: with URLBlocklist

#133
post #46

To answer a few questions here: 1. I landed this fix because there was a policy that did not work properly. We could instead document that the URLBlocklist policy works for every scheme but one, or we could fix it. Fixing it makes more sense. 2. This policy only can be set on managed machines. 3. This policy, in isolation, is trivially circumvented. Managed environments block many things, including many of the propos…

>2. This policy only can be set on managed machines.

What about kids in school? So only the poor kids who don't have access to their own hardware will be subject to these rules that prevent them from viewing source? Sounds pretty insane.

What's truly absurd is the apparent lack of critical thought that went into this decision.

Keep patting yourself on the back though, Eric. You're obviously totally 100% right on this one /s

Re: Chromium: Permit blocking of view-source: with URLBlocklist

#134
post #26

Earlier quoted context omitted.

Students will not get by in life by viewing the source code when confronted with any problem.

As a DevOps engineer, I had multiple encounters with undocumented software just in the past month. Viewing the source code certainly helped.

I was trying to speak figuratively, not literally. Any programmer will need to look at source code to solve problems, but that's not what I was getting at.

When you're taking a math quiz, the goal is to learn how to solve math problems, not bypassing the quiz.

What I really should have said is that in life, shortcuts aren't always appropriate. If you're an engineer confronted with the task of calculating the load the bridge can take, you're supposed to do the hard slog of calculating how much the bridge will take. Let's suppose that engineer didn't understand math, but simply cheated their way through University and took a guess - will you be stepping foot on the bridge?

Teaching kids it's okay to take inappropriate shortcuts is bad, because in the real world, inappropriate shortcuts can have nasty consequences.

Re: Chromium: Permit blocking of view-source: with URLBlocklist

#135
post #46

To answer a few questions here: 1. I landed this fix because there was a policy that did not work properly. We could instead document that the URLBlocklist policy works for every scheme but one, or we could fix it. Fixing it makes more sense. 2. This policy only can be set on managed machines. 3. This policy, in isolation, is trivially circumvented. Managed environments block many things, including many of the propos…

I don't know how to phrase this without it sounding like an attack which I absolutely do not mean it to sound like. But when considering if I would like to receive this same message, I would be more discouraged if someone didn't try to respond because they were afraid to upset me, than if they said something I (or wy ego) didn't want to hear. This preamble is only to make it clear that I'm not trying to be mean, for whatever small value that may be.

I've responded here https://news.ycombinator.com/item?id=29213370 I'd bet it's pretty obvious the internet thinks this was a mistake (and we all know how sound and reasonable the internet always is :D ) but I thought the why it's so infuriating was important to point out too.

Re: Chromium: Permit blocking of view-source: with URLBlocklist

#136

Earlier quoted context omitted.

And since the student taking the quiz very frequently has no choice over whether or not they have to be there or take the quiz, their desires and goals are entirely irrelevant. Edit: are you intentionally or unintentionally trying to justify any and all cheating as a means to get the highest grade possible?

Since the student has no choice over whether or not they take the quiz, what incentive do they have to maintain testing integrity?

ok so you are trying to justify cheating, thanks for clarifying
Post reply on HN