How does that solve anything? Can't you just open the developer tools and read the source anyway?
Chromium: Permit blocking of view-source: with URLBlocklist
61–70 of 136 posts
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#62To 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…
You guys are giving administrators way too much power without any good reasons.
I realize that if they really wanted, they could give up on Chrome and use something else, but for many of them, they will simply lock everything down out of laziness and probably wouldn't without a convenient way of doing so.
An example out of many: why give admins a simple way to disable the built-in password manager? This just enables dumb and archaic password policies for no good reason.
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#63Earlier 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!
I got a crash course in running proxy servers and various VPNs when I was in school, due to the school blocking stuff. I don't recall what sites I was even trying to get to (pre-facebook) nor do I remember really caring about them, but just working around the blocks was particularly fun.
I remember I had to learn how to evade the school proxy in order to get to the Sun Java documentation.
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#64To 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…
You guys are giving administrators way too much power without any good reasons. I realize that if they really wanted, they could give up on Chrome and use something else, but for many of them, they will simply lock everything down out of laziness and probably wouldn't without a convenient way of doing so. An example out of many: why give admins a simple way to disable the built-in password manager? This just enables…
As to your last question, many organizations have a central password management system that lets them audit who uses which password and when. Having the passwords stored in a secondary system makes the audits useless.
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#65Why do I feel like everyone will do this in the quest for "protecting ad money" and will once again have the case of that man charged with hacking for doing CTRL+u
It's a computer level browser policy rather than something the website can request the browser to honour.
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#66Earlier quoted context omitted.
You think you should get to vote against other people's local policies? Just you, or do we each get a vote? Where do I get my list of your policies in case I need to vote against some of them?
That's a rather aggressive way of answering my question. I meant "who decided to let chromium disable view-source, and if this decision is unpopular, can it be reconsidered?". Your local policy is yours, but in much the same way that I don't think it's a good idea for an OS provider to provide a single, easy-to-use button saying "spy on this user who I pinky-swear is a member of my family under 18 and tell me everyth…
Isn't it closing the hole that allowed you to bypass the blocklist by using source viewer rather than adding a way to block viewing the source altogether?
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#67Some more context at https://bugs.chromium.org/p/chromium/issues/detail?id=895462 : > With Schools using Google Forms as a testing platform, students are able to use this shortcut to search through the source of the page, and determine the correct answers.
Has anyone reached out to the Governor of Missouri for his opinion on this? Instead of changing chromium we could just prosecute the students.
https://news.ycombinator.com/item?id=28867562
https://arstechnica.com/tech-policy/2021/10/viewing-website-...
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#68To 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 closed and proprietary and restricted, they never even try to look behind the curtain.
We call ourselves software engineers, then we also need to take on the ethical responsibility of our actions just like engineers do.
If you contribute to this culture of closed technology, you are just as well at fault as developers of DRM tech or Android SafetyNet.
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#69Earlier quoted context omitted.
Is this a euphemistic way of saying cheating?
If solving a problem in an unconventional or novel way (assuming legal) has a business value, that will absolutely get someone by in life. I don't understand what the term "cheating" means in a post-school context.
I think it’s easy to imagine cheating in a post-school context: copying code from a project your employer doesn’t own into one it does. And that has huge legal ramifications. So students do need to learn about those kinds of restrictions via analogues.
Re: Chromium: Permit blocking of view-source: with URLBlocklist
#70Earlier quoted context omitted.
That's a rather aggressive way of answering my question. I meant "who decided to let chromium disable view-source, and if this decision is unpopular, can it be reconsidered?". Your local policy is yours, but in much the same way that I don't think it's a good idea for an OS provider to provide a single, easy-to-use button saying "spy on this user who I pinky-swear is a member of my family under 18 and tell me everyth…
Isn't it closing the hole that allowed you to bypass the blocklist by using source viewer rather than adding a way to block viewing the source altogether?
I would argue that any client side blocking is pointless at best, and points to extreme lack of actual security at worst.