zlacker

[return to "What will a Chromium-only Web look like?"]
1. HWR_14+L4[view] [source] 2022-06-22 09:55:45
>>dochtm+(OP)
"Hi, you seem to be browsing without being signed into Google with your government verified identity. Please do so to continue seeing the ads, I mean the internet"
◧◩
2. encryp+vq[view] [source] 2022-06-22 12:32:19
>>HWR_14+L4
Chromium is open source. You're confusing Chromium with Chrome.
◧◩◪
3. rcMgD2+zs[view] [source] 2022-06-22 12:44:22
>>encryp+vq
It's like confusing "open-source" Android, AOSP and Play Services: https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on...

>While Android is open, it's more of a "look but don't touch" kind of open. You're allowed to contribute to Android and allowed to use it for little hobbies, but in nearly every area, the deck is stacked against anyone trying to use Android without Google's blessing. The second you try to take Android and do something that Google doesn't approve of, it will bring the world crashing down upon you.

◧◩◪◨
4. jacoop+Jt[view] [source] 2022-06-22 12:51:50
>>rcMgD2+zs
The difference is, AOSP on its own is unusable, but Chromium Is.
◧◩◪◨⬒
5. gspr+JB[view] [source] 2022-06-22 13:45:36
>>jacoop+Jt
It's pretty close to being unusable as an open source code base. Look at Debian's struggles with maintaining security fixes for Chromium.

Sure, the license is open, and Chromium is therefore technically open. But it's dangerously close to not being usable in any real practical meaning of "open source".

The way things are, we do indeed stand on the precipice of a Chromium-only web with—for all practical intents and purpose—no open browser. Firefox is the last thing that stands between us and that reality. It's just a shame that they seem to be wasting hundreds of millions on admin and management instead of just throwing it all at their developers.

◧◩◪◨⬒⬓
6. jacoop+GT1[view] [source] 2022-06-22 19:40:23
>>gspr+JB
Its a Debian problem, there is a flatpak version and its working fine.
[go to top]