this post was submitted on 28 Jul 2023
296 points (100.0% liked)

Technology

37720 readers
319 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
 

cross-posted from: https://lemmy.ml/post/2546109

Read why "Web Environment Integrity" is terrible, and why we must vocally oppose it now. Google's latest maneuver, if we don't act to stop it, threatens our freedom to explore the Internet with browsers of our choice.

you are viewing a single comment's thread
view the rest of the comments
[–] salient_one@lemmy.villa-straylight.social 26 points 1 year ago (5 children)

That's a good question. Safari market share isn't as big as Chrome's (62.55% vs 20.5%, according to statcounter), but it's still the 2nd largest. Also note that the WEI proposal appeared around May but made the news only now.

[–] dan@upvote.au 13 points 1 year ago (4 children)

Safari's market share definitely isn't as big, that's a good point. However, it's got 100% market share on iPhones (Apple forbid other browser engines from running on iOS), so there's a lot of people that have no choice.

[–] kelvinjps@beehaw.org 6 points 1 year ago (3 children)

Really? Like you cannot use Firefox or chrome on IOS?

[–] zaplachi@lemmy.ca 16 points 1 year ago* (last edited 1 year ago)

You can use the WebKit (Safari’s engine) wrappers made by Firefox and Chrome - but can’t use truly independent browsers

load more comments (2 replies)
load more comments (2 replies)
load more comments (2 replies)