- cross-posted to:
- programming@programming.dev
- privacy@lemmy.ml
- cross-posted to:
- programming@programming.dev
- privacy@lemmy.ml
The much maligned “Trusted Computing” idea requires that the party you are supposed to trust deserves to be trusted, and Google is DEFINITELY NOT worthy of being trusted, this is a naked power grab to destroy the open web for Google’s ad profits no matter the consequences, this would put heavy surveillance in Google’s hands, this would eliminate ad-blocking, this would break any and all accessibility features, this would obliterate any competing platform, this is very much opposed to what the web is.
Note of amusement: The GitHub issues tracker for that proposal got swamped with tickets either mocking this crap or denouncing it for what it is, this morning the person who seems to be the head of the project closed all those tickets and published this blog post, in essence saying “Shut up with your ethical considerations, give us a hand in putting up this electric fence around the web”. Of course that didn’t stop it.
Also somebody pointed out this gem in the proposal, quoted here:
6.2. Privacy considerations
Todo
Quick edit: This comment on one of the closed tickets points out the contact information of the Antitrust authorities of both US and EU, i think i’m gonna drop the EU folks a note
Edit: And they disabled commenting on the issues tracker
[Don’t assume consensus nor finished state]
Often a proposal is just that - someone trying to solve a problem by proposing technical means to address it. Having a proposal sent out to public forums doesn’t necessarily imply that the sender’s employer is determined on pushing that proposal as is.
It also doesn’t mean that the proposal is “done” and the proposal authors won’t appreciate constructive suggestions for improvement.
[Be the signal, not the noise]
In cases where controversial browser proposals (or lack of adoption for features folks want, which is a related, but different, subject), it’s not uncommon to see issues with dozens or even hundreds of comments from presumably well-intentioned folks, trying to influence the team working on the feature to change their minds.
In the many years I’ve been working on the web platform, I’ve yet to see this work. Not even once.
…?
What is this, “Good vibes only?”“Good vibes only” seems to be embedded in the culture of web development today. Influential devs’ Twitter accounts have strong Instagram vibes: constantly promoting and congratulating each other, never sharing substantive criticisms. Hustle hustle.
People with deep, valid criticisms of popular frameworks like React seem to be ostracized as cranks.
It’s all very vapid and depressing.
Do you have an article about react? I’d love to read it. And yes tech is chock full of egos and fakers.
Alex Russell is a good read on React. His position gives him a broad view of its impacts and has kept him from being sidelined. This Changelog podcast is a decent distillation of his criticisms – it was recorded earlier this year, a few days after his Market For Lemons blog post.
(Sorry for the late reply! I’ve been a bit swamped lately and away from kbin.)
THIS IS NOT (just) ABOUT GOOGLE
Currently, attestation and “trusted computing” are already a thing, the main “sources of trust” are:
- Microsoft
- Apple
- Smartphone manufacturers
- Third party attestators
This is already going on, you need a Microsoft signed stub to boot anything other than Windows on a PC, you need Apple’s blessing to boot anything on a Mac, your smartphone manufacturer decides whether you can unlock it and lose attestation, all of Microsoft, Apple and Google run app attestation through their app stores, several governments and companies run attestation software on their company hardware, and so on.
This is the next logical step, to add “web app” attestation, since the previous ones had barely any pushback, and even fanboys of walled gardens cheering them up.
PS: Somewhat ironically, Google’s Play Store attestation is one of the weaker ones, just look at Apple’s and the list of stuff they collect from the user’s device to “attest” it for any app.
I started looking at Mac’s for my next computer. Due to this amazing project. https://asahilinux.org/
It’s time for Alphabet to be broken up into separate letters.
This is why we need Firefox.
And Firefox needs to be a market that can’t be ignored.
@TheYang Exactly! Came here to say this. Everybody actively using chromium based browsers is a part of the problem.
Stop with this excuse and stop Insulting people. I’ve been on Firefox for nearly 20 years, but Mozilla has ruined it for me little by little. The last straw has been the horrible UI redesign. So I switched to a Chromium browser. Tell Mozilla to make a better browser and to listen to their community, instead of blaming people for using what serves them best.
What does your UI gripe have to do with this biased tabloid piece you shared?
Firefox is fine and works even better than it ever has. If you cared about the UI so much you’d have tried any of its forks that use different and older designs.