Topic: Chrome Browser

5 chapters across the catalog

Smart Wall
Episode 1106 56:37 - 1:02:19

1106: Smart Wall

Google Chrome Extension API, Pi-hole Ad Blocking

Google announced changes to its extension API that will effectively disable many third-party ad blockers in the Chrome browser. In response, users are turning to hardware-based solutions like Pi-hole, a network-wide ad blocker running on Raspberry Pi. The move is seen as Google protecting its core advertising business as Microsoft Edge also transitions to the Chromium engine.

Without Evidence
Episode 1054 1:21:18 - 1:25:25

1054: Without Evidence

Pi-hole Ad Blocking, Brave Browser and Data Indicators

Technical advice is given on using a Pi-hole (Raspberry Pi) to block ads at the network level. The Brave browser is also discussed as a tool for privacy, though its business model involving "indicators" and cryptocurrency is viewed with some skepticism. The segment mentions the controversy surrounding Brave's founder and his departure from Firefox.

Poop Particle
Episode 1024 56:22 - 1:00:23

1024: Poop Particle

Brave Browser and Ad-Blocking Proxy Technology

The hosts discuss the merits of the Brave browser, which uses a proxy method to block ads without alerting publishers. They compare it to Firefox and Chrome, arguing that users have a responsibility to use tools that prevent data leakage to advertisers.

Born This Way
Episode 963 2:50:00 - 2:50:55

963: Born This Way

Google HTTPS Deadline, Website Security Requirements

Google has set a deadline for websites to transition to HTTPS, warning that the Chrome browser will soon flag non-secure sites with prominent warnings. The hosts discuss the technical hurdles of updating older websites and Amazon S3 buckets to meet these new security standards. They express frustration with being forced into these changes by Google's dominant market position.

Hats of State
Episode 367 5:45 - 7:15

367: Hats of State

Google Chrome Rendering Issues, No Agenda Website Glitches

The No Agenda Show website reportedly failed to load correctly in the Google Chrome browser, appearing as a nearly empty page. This behavior is contrasted with the site's stable performance in Firefox, leading to theories about "Google washing" or aggressive JavaScript handling in new Chrome updates. The site utilizes a standard Squarespace template, suggesting the issue may lie with browser-specific rendering of common web platforms.