observer

joined 1 year ago
[–] [email protected] 3 points 1 year ago

This is only my opinion, but basically you cannot trust no one. Having that said, certificate providers make their money by ensuring you will get the page from the server you asked for, and also for the encryption. Ignoring the certificate is possible, since it is the browser's choice. My point is, SSL providers have a lot to lose by exploiting the certificates for malicious intents(such as modifying the data, or changing to a different host etc) while the DRM of google is by design meant to allow us less freedom with how we use the web.

So i think that you can choose who is less trust worthy by figuring out what they will gain

[–] [email protected] 5 points 1 year ago (2 children)

I think that the main difference is that with SSL you only encrypt the data, and then you can modify at will(as in making changes to every page your browser renders - ad block, grease monkey like extensions etc. With DRM, you won't be able to modify the pages at all

[–] [email protected] 3 points 1 year ago

I've been a developer for over a decade and I can say for sure I'm tech lazy. Not 'normies'(wetf that means) nor anyone else should waste their time on tasks that could've been automated.

If you came here, it is not because you are interested in the underlying protocol, you came here since it is a social media.

[–] [email protected] -5 points 1 year ago (1 children)

Then go 'act' instead of complaining about other comments online

[–] [email protected] 2 points 1 year ago

Just don't aim

[–] [email protected] 4 points 1 year ago (4 children)

That sounds like drivers

[–] [email protected] 28 points 1 year ago (1 children)

Could some please paste the post here? 🙏