Chronotope’s avatarChronotope’s Twitter Archive—№ 105,767

      1. Soooo Chrome's Manifest V3 change, pegged as potentially disabling a number of ad blocking tools, has gone through some real torturous contortions. Early this year Google declared the change needed for performance reasons. That was then disproven... zdnet.com/article/google-backtracks-on-chrome-modifications-that-would-have-crippled-ad-blockers/
        OpenGraph image for zdnet.com/article/google-backtracks-on-chrome-modifications-that-would-have-crippled-ad-blockers/
        Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 4 Retweets ❤️ 2 Favorites Mood -2 🙁
    1. …in reply to @Chronotope
      And now here we are today! Manifest V3 now has a different rationale! Now it is 'user privacy'. And the changes are back on, using an entirely different justification. cnet.com/news/google-says-chrome-isnt-killing-ad-blockers-its-making-them-safer/
      OpenGraph image for cnet.com/news/google-says-chrome-isnt-killing-ad-blockers-its-making-them-safer/
      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets ❤️ 1 Favorite Mood 0
  1. …in reply to @Chronotope
    I don't know about you, but as someone who writes code, I usually am creating a solution to a problem. But it sure looks like here that Chrome is trying to find a problem to justify a solution. Seems... sketchy to me.
    On twitter.com Twitter logo Chronotope’s avatar ❤️ 4 Favorites Mood 0

Search tweets' text