HN
Today

Vivaldi 8.3 for Desktop: make bad ads sad

The much-anticipated Vivaldi 8.3 desktop release, touting improved ad-blocking, was unfortunately lost to the digital void, presenting users with a Cloudflare 522 error. This technical hiccup inadvertently spurred a wide-ranging Hacker News discussion. Commenters debated Vivaldi's partially closed-source nature and ad-blocking efficacy, alongside a broader philosophical dive into the economics of web content, ads, and alternative payment models.

29
Score
28
Comments
#10
Highest Rank
2h
on Front Page
First Seen
Nov 5, 2:00 PM
Last Seen
Nov 5, 3:00 PM
Rank Over Time
1010

The Lowdown

The anticipated announcement of Vivaldi 8.3 for Desktop, which promised to "make bad ads sad," was inaccessible to readers due to a Cloudflare 522 "Connection timed out" error. This meant that the details of the new browser version, its features, and specific improvements to its ad-blocking capabilities could not be retrieved from the Vivaldi blog.

While the specific details of the release remain unknown due to the server error, based on the title, the update likely focused on:

  • Enhanced Ad Blocking: The tagline "make bad ads sad" strongly suggests improvements to Vivaldi's built-in ad and tracker blocker.
  • Browser Performance and Stability: As with most browser updates, general improvements to speed, stability, and security would be expected.
  • User Interface Refinements: Vivaldi often introduces tweaks and new customization options.

Ultimately, the story became less about the software update itself and more about the discussion it sparked, underscoring the irony of a browser update focused on web experience being thwarted by a web server issue.

The Gossip

Vivaldi's Virtues and Vices

Commenters explored Vivaldi's standing in the browser landscape, discussing its partially closed-source nature and the implications for user trust. While some praised Vivaldi for its user-centric incentives and unique features, others raised concerns about its ad-blocking effectiveness compared to tools like uBlock Origin, noted stability issues on Linux, and questioned why one wouldn't simply use a fully open-source alternative like Firefox. The debate highlighted the tension between customizability, privacy, and open-source principles.

Ad-Blocking Alternatives and Avenues

A significant portion of the discussion pivoted to the broader topic of ad-blocking and content monetization. One commenter proposed an ISP-mediated payment system to creators for an ad-free web, sparking a lively debate. Skeptics pointed out issues with ISP privacy, payment processing complexities, and past failures of similar models (like Brave's BAT). Others argued that users often don't want to pay, or that even paid services reintroduce ads, leading to a sense that the battle against ads is a losing one, with piracy sometimes offering a superior user experience.