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.
I just had to change my domain name because Google wouldn’t stop blocking my personal server webpage for being a “phishing” website, there was no way it could be interpreted in that way at all and it didn’t matter, my personal server apps were basically blocked on 80% of browsers.
Certs only prevent others from making it look like it was you, they don’t stop someone from exploiting a vulnerable webapp you might be hosting, or using a misconfigured mail server as a relay.
If you have anything open to the public, then you either have to keep it read only, or stay on it to make sure it’s updated, secured, sanitized, and so on.
Personally, I’ve switched to using client side certificates, so everything is effectively “not public”.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
I just had to change my domain name because Google wouldn’t stop blocking my personal server webpage for being a “phishing” website, there was no way it could be interpreted in that way at all and it didn’t matter, my personal server apps were basically blocked on 80% of browsers.
If you hosted a compromised app once, or ever messed up the setup of your mail server… that’s what happens.
I was only flagged as phishing, with full SSL certs etc
Certs only prevent others from making it look like it was you, they don’t stop someone from exploiting a vulnerable webapp you might be hosting, or using a misconfigured mail server as a relay.
If you have anything open to the public, then you either have to keep it read only, or stay on it to make sure it’s updated, secured, sanitized, and so on.
Personally, I’ve switched to using client side certificates, so everything is effectively “not public”.
Does CloudFlares HTTPS resolve that issue?