zlacker

[parent] [thread] 3 comments
1. cayley+(OP)[view] [source] 2023-07-26 19:00:45
Blocking Chromium altogether isn't as big of a deal as it seems, either (unless you're a truly huge website). It's so easy to switch to Firefox these days. Probably takes a few minutes. For technical blogs with useful content on them I suspect people's desire to see the content will override the inertia of switching browsers.
replies(2): >>helloj+4B >>hightr+vi1
2. helloj+4B[view] [source] 2023-07-26 21:33:40
>>cayley+(OP)
Does not blocking Chromium devolve in behavior to a comparable level as WEI? Seems like the same problem is introduced: breaking the web.
replies(1): >>cesarb+7Q
◧◩
3. cesarb+7Q[view] [source] [discussion] 2023-07-26 22:59:11
>>helloj+4B
> Does not blocking Chromium devolve in behavior to a comparable level as WEI? Seems like the same problem is introduced: breaking the web.

Not really, for two reasons.

First, is that it can be bypassed, for instance with an extension which hides the relevant JS property and/or switches the user agent, or even on-the-fly edits the site's Javascript. The whole point of WEI is that it cannot be bypassed.

Second, is that just blocking Chromium does not prevent the development and use of new web browsers and/or operating systems, while a predictable consequence of WEI is making them non-viable in practice (they'd have to first convince Google that both the browser and operating system is DRM-ed enough that the user does not have enough control over the browser to make it do everything the user wants, and only then the browser would be allowed to access WEI-walled content).

4. hightr+vi1[view] [source] 2023-07-27 02:18:19
>>cayley+(OP)
It absolutely takes just a few minutes. I did it today on my work laptop, installed Firefox, import from chrome, and I was back to work in less than 5
[go to top]