Dav2d

Original Article ↗ Hacker News Discussion ↗

Project and Codec Overview

  • dav2d is introduced as a highly optimized, small, portable, and very fast software decoder for the upcoming AV2 video codec.
  • AV2 is described (via AOMedia material) as the successor to AV1, aiming for better compression efficiency for streaming, broadcasting, and real-time communication.
  • One comment cites prior discussion claiming AV2 targets ~30% lower bitrate than AV1 at equivalent quality, but notes AV1 itself is still not broadly supported in many consumer setups.

Adoption, Ecosystem, and Naming

  • Some are excited about early availability of a fast decoder, expecting it to accelerate AV2 adoption similarly to how dav1d did for AV1.
  • Others are cautious: AV2 spec is not final, no ffmpeg encoder exists yet, and hardware support will lag.
  • There is desire for “one” dominant codec standard, with some seeing AV2 as potentially winning over competing H.26x codecs.
  • Naming (dav1d → dav2d) is generally seen as a natural progression, with a few comments about confusion with similarly named public figures.

Patents and Legal Concerns

  • Strong criticism is directed at patent pools and “patent troll” entities targeting AV1/AV2, with claims that this is thinly veiled extortion.
  • Some argue the Alliance for Open Media’s combined legal strength makes broad enforcement risky for patent pools, but others note the real pressure often falls on smaller downstream users.
  • There is recurring sentiment that software patents—especially for codecs—are overbroad and harmful, and calls to reform or abolish them.

Implementation Language and Safety

  • One view: security-sensitive media codecs should not be written in memory-unsafe languages; using C for new decoders is seen as negligent.
  • Counterpoints:
    • Performance-critical codec cores often rely on hand-written assembly and strict patterns (no recursion, limited allocations), so memory-safe languages add little in those hotspots.
    • Encoding is considered less risky than decoding; parsers/containers are prime candidates for memory-safe languages.
    • Examples are given of a Rust-based AV1 decoder being slightly slower and less actively improved than C/assembly counterparts.

AI Scraping and Access Friction

  • Several comments discuss the site’s bot-protection interstitials (e.g., “checking you’re human”) as a response to heavy AI scraper and DDoS-like traffic.
  • Operators describe AI bots as unthrottled, numerous, and often hitting expensive dynamic paths (e.g., Git forges, archives), with up to ~99% of traffic being bots in some cases.
  • Some users find these protections frustrating, slow, and hostile to automation; others argue small volunteer projects lack resources to implement more nuanced defenses.
  • Suggested mitigations include rate-limiting by IP, fingerprinting bots, hidden trap links, static sites where possible, and login requirements for costly operations—but feasibility is debated.

Broader Internet Concerns

  • The discussion generalizes to frustration with today’s web: pervasive bot checks, cookie banners, and CDNs are seen as degrading usability.
  • There is debate over whether this is a “tragedy of the commons,” a problem of corporate enclosure and extraction, or primarily a consequence of malicious/bad-faith actors (including AI scrapers).