Technology

37739 readers

757 users here now

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.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

Los@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

932

Google is working on essentially putting DRM on the web (github.com)

submitted 1 year ago by jherazob@beehaw.org to c/technology@beehaw.org

271 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] jarfil@beehaw.org 1 points 1 year ago (1 children)

If you hosted a compromised app once, or ever messed up the setup of your mail server... that's what happens.

[–] briongloid@aussie.zone 1 points 1 year ago (1 children)

I was only flagged as phishing, with full SSL certs etc

[–] jarfil@beehaw.org 2 points 1 year ago (1 children)

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".

[–] briongloid@aussie.zone 1 points 1 year ago

Does CloudFlares HTTPS resolve that issue?