this post was submitted on 03 Nov 2023
382 points (100.0% liked)
Technology
37713 readers
526 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a much less broad, though. That's a win right?
I don't trust Google's word that they will keep it that way. Besides, would you have accepted this proposal if WEI wasn't proposed first? It's a form of manipulation.
Sites inside webviews can already communicate with the app running them, I don't see how this proposal in this form causes any additional problems
The same can be said about WEI on browsers. Just wait till it becomes a problem - only problem is that you won't be able to escape it at that point.
Except websites can't just communicate directly with the OS like they can in webviews