Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chromium: Permit blocking of view-source: with URLBlocklist

chromium-review.googlesource.com

Post reply on HN
Print view View original

121–130 of 136 posts

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

#121

Post by rubyist5eva »

kuschku wrote: post #68
ericlaw wrote: 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…

Many of the best people in IT are there today, because they got curious about how stuff worked, experimented with it, broke the rules, and learned from that. This curiosity needs to be encouraged, not stopped. The young generation in IT already has issues because many of them don’t understand files, and many of them can’t even use a computer anymore. They grow up with tech all around them, but because all of it is cl…

This is why my son's first computer was a raspberry pi.

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

#122

Post by 2Gkashmiri »

ericlaw wrote: post #118
2Gkashmiri wrote: post #102

Earlier quoted context omitted.

who says this isnt normalized in regular chrome as a security feature and later into firefox because "industry"

The many many upstart browsers (including mine) that are eager for Chrome to do something so foolish so we can collect all of their irate users?

not sure if you forgot about floc?

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

#123

Post by robin_reala »

YPPH wrote: post #49
goda90 wrote: post #37

Earlier quoted context omitted.

Students will not learn to experiment with technology if they are blocked on every attempt.

Time and place. Taking a math quiz is the wrong time to experiment with bypassing quizzes.

Like any organisation would turn this on for a quiz and off again afterwards. This would be a blanket and permanent change for the entire school.

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

#124

Post by selfhoster11 »

YPPH wrote: post #26
kyleee wrote: post #21

Earlier quoted context omitted.

This is also the type of thing that plants the seed of interest for a career or hobby of computing, which is another reason it's stupid. Reward people's curiousity instead of punishing it, especially in a schooling situation!

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.

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

#125

Post by selfhoster11 »

YPPH wrote: post #50
atomicnumber3 wrote: post #38

Earlier quoted context omitted.

But perhaps they will get by in life by finding clever solutions that circumvent common expectations through curiosity and familiarity with technology.

Is this a euphemistic way of saying cheating?

No, this is a way of saying "hacking", in the old sense of the word.

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

#126

Post by selfhoster11 »

charcircuit wrote: post #80
kuschku wrote: post #68

Earlier quoted context omitted.

Many of the best people in IT are there today, because they got curious about how stuff worked, experimented with it, broke the rules, and learned from that. This curiosity needs to be encouraged, not stopped. The young generation in IT already has issues because many of them don’t understand files, and many of them can’t even use a computer anymore. They grow up with tech all around them, but because all of it is cl…

These people can do that at home. Also not understanding files can be a benefit. Files are a legacy computing abstraction. Not knowing legally cruft can give you an open mind.

Just because it's legacy, doesn't mean it's not a powerful tool.

Files have multiple advantages over other approaches, such as being independent from the application that created them (even if the company subsequently goes under), being editable with a different application from the one that created them (though imperfectly sometimes), and being self-contained bundles of data that need no infrastructure to support them other than a local application (compared to other approaches, where a large cloud infrastructure is basically mandatory and you're SOL if it goes away for you).

Recency bias is a thing. Try to work counter to it.

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

#128

Post by harry-wood »

selfhoster11 wrote: post #124
YPPH wrote: 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.

Yeah. There's bizarre situations where 'view source' shouldn't really be necessary/beneficial and yet somehow it's a handy life skill. I remember doing it while booking a flight on RyanAir (Very bad website. I knew the option to not pay for extra insurance had to be on the page somewhere!)

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

#129

Post by BeFlatXIII »

anoonmoose wrote: post #85
BeFlatXIII wrote: post #82

Earlier quoted context omitted.

And the goal of the student taking that quiz is to get the highest grade by any means necessary. Learning is entirely irrelevant.

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?

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

#130

Post by nightpool »

ericlaw wrote: 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 would like to quote from the W3C TAG comments on the Managed Device Web API:

https://github.com/w3ctag/design-reviews/issues/606#issuecom...

> > "NOTE: [RFC7258] treats pervasive monitoring as an attack, but it doesn’t apply to managed devices."

> We don't think this is adequate. Given the power dynamics at play in an employer-employee relationship, the UA should still be working in the best interests of the end-user (the employee) even if the device being used is managed by an administrator. That is to say, pervasive monitoring is never a feature.

Chrome may not consider it part of the "web-exposed platform", since the code doesn't live in blink/, but the same logic applies to view-source. The needs of the users are more important than the security theatre you wish to put on for their teacher's benefit.

Post reply on HN