to be fair, the way this is being rolled out (and the way web audio was butchered) creates the appearance of 'who do you appeal to' being 'no one, unless you pay google money for enterprise support, and the chrome team still ignores you for their own agenda'
-
-
-
the answer of 'maybe/probably' to 'will ublock work' is great as a starting point but killing ublock before the answer is 'yes, once it's updated' is also a great way to convince people not to trust you. and the chrome team has done that multiple times (flash, unity, etc)
- 2 more replies
New conversation -
-
-
I'm not saying people shouldn't trust Google but there's definitely been a change in public opinion here. Google can't assume consumer trust anymore. How are the Chrome team going to win trust back?
-
I'm not asking anyone to trust us; I'm suggesting that if you have concrete API feedback, leading with innuendo, aspersion, but no data is a fast way to gain a smaller audience. The team is listening and iterating; watch what they do, not what others say they intend.
End of conversation
New conversation -
-
-
In this case, I don’t think anyone should be framing it as declarative vs. imperative debate. This is instead a question of “what are other legitimate ways to protect user privacy and performance while not also nerfing trusted ad blockers?”
-
If the first pass answer is “less powerful APIs for all (except enterprise users)” instead of “could we tweak the permissions model here instead”, folks are going to rightfully assume that the latter approach wasn’t exhaustively considered first. And they’ll assume reasons why.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.