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.
Why do people have a problem with this? It explicitly says browser extensions, like ad blockers, will still work. It says cross site tracking won’t be allowed. It all sounds pretty good.
It sounds like most are not liking it because of some potential future abuses rather than what it actually is?
Alright, I'm kinda slow today, so tell me if I got it right: We, the users, will be "kindly asked" to get one thingamabob signature/identifier of "integrity", so websites "know" whether we're good or bad guys?
Can someone explain to me how this is different to the trust system used by SSL Certificates?
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
Ugh. DRM. I freaking hate DRM. I "buy" a book from Amazon and it's all DRMed. I like the Kindle app so I keep buying there. But when I can I buy physical books at a LBS