We have two new posts out today addressing the confusion and misinformation surrounding what Chrome is doing with extensions. This first one gives context on the broader security, privacy and abuse considerations we're addressing.https://security.googleblog.com/2019/06/improving-security-and-privacy-for.html …
-
-
May I ask you to address this thread on HN? https://news.ycombinator.com/item?id=20167719 … Is it true that webRequest will remain available to extensions but only the "blocking capabilities" of webRequest will be restricted? (If so, how would that help with the malware problem?)
-
Yes, but network requests won't be observable without permission on the relevant hosts. And host permissions are changing significantly in Mv3 (e.g. they can't be granted as blanket install time permissions).
- Još 1 odgovor
Novi razgovor -
-
-
The new API sounds similar to what Apple introduced to iOS to allow ad blocking there? My perception is that ad blockers for iOS have been quite popular and successful. To me it sounds like you're making a very sensible change
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
What percentage, if any, of those malicious extensions are content/ad blocking extensions?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.