The source URL provided for this item, a GitHub-style issue page on FFmpeg’s code hosting site, was not accessible for review. Instead of issue content, the page returned a notice from Anubis, a proof-of-work based anti-scraping tool.
According to the text displayed on the page, the site administrator has installed Anubis to protect the server from what the notice describes as aggressive scraping by AI companies. The notice states that this kind of scraping can cause downtime, making the site’s resources inaccessible to everyone.
The page explains that Anubis uses a proof-of-work scheme similar to Hashcash, a system originally proposed as a method for reducing email spam. Per the notice, the underlying idea is that requiring a small computational task per visitor has a negligible effect on individual users but becomes costly at the scale used by mass scrapers, making large-scale scraping more expensive to carry out.
The notice also describes Anubis as a temporary or placeholder measure. According to the text, the intention is to eventually shift effort toward fingerprinting and identifying headless browsers — for example, by analyzing how they render fonts — so that the proof-of-work challenge page would not need to be shown to visitors who are more likely to be legitimate human users rather than bots.
Additionally, the notice warns that Anubis depends on modern JavaScript features, and that browser privacy plugins such as JShelter can interfere with those features. The page instructs users to disable JShelter or similar plugins for the domain in order to pass the check.
Because the actual issue page — which reportedly concerns a division-by-zero bug discovered in FFmpeg using a fuzzer described as “vibecoded” — was not visible past this verification screen, no details about the bug itself, its cause, its severity, or any fix could be confirmed from the available source material. No information about the fuzzer’s design, its methodology, or who reported the issue was accessible either.
As a result, this brief is limited to describing the access barrier encountered rather than the technical content of the reported bug. Readers seeking details on the FFmpeg division-by-zero issue would need to access the linked page directly, potentially after completing the site’s verification challenge, to view the original report.
Key facts
- The provided source URL returned an Anubis anti-bot verification page instead of the FFmpeg issue content
- Anubis is described as a proof-of-work system similar to Hashcash, intended to raise the cost of mass scraping
- The notice states Anubis is a placeholder until better headless-browser fingerprinting (e.g., via font rendering) is developed
- The page states that browser privacy plugins like JShelter must be disabled for the verification to work
- No details of the actual FFmpeg division-by-zero bug or the fuzzer were accessible in the retrieved source text