Live Updates: COVID-19 Cases
  • World 13,739,632
    World
    Confirmed: 13,739,632
    Active: 4,962,501
    Recovered: 8,189,211
    Death: 587,920
  • USA 3,619,663
    USA
    Confirmed: 3,619,663
    Active: 1,832,765
    Recovered: 1,646,698
    Death: 140,200
  • Brazil 1,972,072
    Brazil
    Confirmed: 1,972,072
    Active: 529,729
    Recovered: 1,366,775
    Death: 75,568
  • India 979,719
    India
    Confirmed: 979,719
    Active: 335,425
    Recovered: 619,193
    Death: 25,101
  • Russia 752,797
    Russia
    Confirmed: 752,797
    Active: 209,168
    Recovered: 531,692
    Death: 11,937
  • Peru 337,724
    Peru
    Confirmed: 337,724
    Active: 98,907
    Recovered: 226,400
    Death: 12,417
  • Chile 321,205
    Chile
    Confirmed: 321,205
    Active: 21,934
    Recovered: 292,085
    Death: 7,186
  • Mexico 317,635
    Mexico
    Confirmed: 317,635
    Active: 81,600
    Recovered: 199,129
    Death: 36,906
  • South Africa 311,049
    South Africa
    Confirmed: 311,049
    Active: 145,903
    Recovered: 160,693
    Death: 4,453
  • Spain 304,574
    Spain
    Confirmed: 304,574
    Active: 276,161
    Recovered: ?
    Death: 28,413
  • UK 291,911
    UK
    Confirmed: 291,911
    Active: 246,858
    Recovered: ?
    Death: 45,053
  • Iran 267,061
    Iran
    Confirmed: 267,061
    Active: 22,845
    Recovered: 230,608
    Death: 13,608
  • Pakistan 257,914
    Pakistan
    Confirmed: 257,914
    Active: 73,751
    Recovered: 178,737
    Death: 5,426
  • Italy 243,506
    Italy
    Confirmed: 243,506
    Active: 12,493
    Recovered: 196,016
    Death: 34,997
  • Saudi Arabia 243,238
    Saudi Arabia
    Confirmed: 243,238
    Active: 53,246
    Recovered: 187,622
    Death: 2,370
  • Turkey 215,940
    Turkey
    Confirmed: 215,940
    Active: 12,788
    Recovered: 197,733
    Death: 5,419
  • Germany 201,281
    Germany
    Confirmed: 201,281
    Active: 5,733
    Recovered: 186,400
    Death: 9,148
  • Bangladesh 196,323
    Bangladesh
    Confirmed: 196,323
    Active: 86,864
    Recovered: 106,963
    Death: 2,496
  • France 173,304
    France
    Confirmed: 173,304
    Active: 64,364
    Recovered: 78,820
    Death: 30,120
  • Canada 108,829
    Canada
    Confirmed: 108,829
    Active: 27,534
    Recovered: 72,485
    Death: 8,810
  • China 83,612
    China
    Confirmed: 83,612
    Active: 259
    Recovered: 78,719
    Death: 4,634
  • Netherlands 51,351
    Netherlands
    Confirmed: 51,351
    Active: 45,214
    Recovered: ?
    Death: 6,137
  • S. Korea 13,612
    S. Korea
    Confirmed: 13,612
    Active: 925
    Recovered: 12,396
    Death: 291
  • Australia 10,810
    Australia
    Confirmed: 10,810
    Active: 2,662
    Recovered: 8,035
    Death: 113
  • New Zealand 1,548
    New Zealand
    Confirmed: 1,548
    Active: 27
    Recovered: 1,499
    Death: 22

Google would block third-party ad blockers in Chrome for security, privacy and speed

Author at TechGenyz Google
Google Ad Block
Google Chrome would now block certain ad blockers and destroy content-blocking extensions as per the changes to the open-source Chromium browser proposed by Google engineers for the sake of speed and safety. It seems like Adblock Plus would be an exception to this change, though similar third-party plugins would be affected. The drafted changes would also restrict the capabilities available to developers of extensions. Content blockers aid users to control the processes of presentation and interaction of their browser with remote resources. Manifest v3, in a bid to improve security, privacy, performance and even enhance user control, comprises a specification for browser extension manifest files enumerating resources and capabilities available to browser extensions. The design document Stated: "Users should have increased control over their extensions… A user should be able to determine what information is available to an extension, and be able to control that privilege." To reach these goals, Google plans to replace the webRequest API with the new declarativeNetRequest API. The webRequest API allows the interception of network requests by browser extensions so as to block, modify or redirect them, and this delays web page loading. So, this API will now be able to only read, and not modify, network requests. The declarativeNetRequest API would allow the Chrome browser itself to handle network requests, but risks removing a possible source of bottlenecks and a potentially useful mechanism for changing browser behavior.
The declarativeNetRequest API provides better privacy to users because extensions can't actually read the network requests made on the user's behalf - Google’s API document
Raymond Hill, the developer behind uBlock Origin and uMatrix posted on the Chromium bug tracker that changes suggested by the Manifest v3 proposal would wreck his ad and content block extensions while simultaneously restricting content control by users. In the case of the user preferring to allow a third-party developer to filter network requests in place of Google, these drafted changes would interfere with webpage functionality. Hill adds that "If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin and uMatrix, can no longer exist." While the proposed changes would reduce the efficacy of content blocking and blocking extensions, all ad blocking would not be necessarily knocked out. Google and other internet advertising networks allegedly pay Adblock Plus to whitelist their online advertisements, and thus their preference for this particular plug-in. However, in comparison to Adblock Plus, uBlock Origin and uMatrix offer much more wide-ranging controls without bothering about placating publishers through ad whitelisting. Furthermore, there are other facilities such as blocking media elements larger than a specified size, disabling JavaScript execution by injecting Content-Security-Policy directives, and removing the outgoing Cookie headers, that would no longer be available under the new declarativeNetRequest API. Apparently, Hill is awaiting a response from the Google software engineer overseeing this issue.
I understand the point of a declarativeNetRequest API, and I am not against such API. However I don't understand why the blocking ability of the webRequest API - which has existed for over seven years - would be removed (as the design document proposes). I don't see what is to be gained from doing this - Raymond Hill, the developer behind uBlock Origin and uMatrix
He argues against the utility of Chromium should these changes come into being:  "Extensions act on behalf of users, they add capabilities to a 'user agent', and deprecating the blocking ability of the webRequest API will essentially decrease the level of user agency in Chromium, to the benefit of websites which obviously would be happy to have the last word in what resources their pages can fetch/execute/render… With such a limited declarativeNetRequest API and the depreciation of blocking the ability of the webRequest API, I am skeptical 'user agent' will still be a proper category to classify Chromium." Several other extension developers have conveyed dismay over the drafted changes, some even surmising that Google’s policy is to use privacy as a pretext for boosting its ad business. Google has not finalized the changes yet and may be willing to address the concerns of extension developers. As per the email of a Google spokesperson to The Register, "Things are subject to change and we will share updates as available."
We Are Hiring

Subscribe