A wrong "closed" never comes back: measuring a job-posting liveness checker on real pages

Описание и применение

Исправления в проекте career-ops устранили ложные пометки вакансий как закрытых из‑за блокировки трекеров DNS‑фильтрами и из‑за сбоев загрузки страниц, улучшив точность проверки живости объявлений.

Задача

The career-ops liveness checker incorrectly marked job postings as permanently closed when DNS filters blocked trackers or when a single page load failure interrupted subsequent checks, causing live jobs to disappear from search results.

Результат

The fixes reduced false positives from DNS filtering and prevented cascading failures from single load errors, improving the accuracy of job‑posting liveness checks.

Рабочий процесс

• 1. Run scan --verify on real postings. 2. Detect disagreements between expected and actual status. 3. Measure impact of DNS filters by comparing results with AdGuard DNS, Control D, and no filter. 4. Apply PR #5015 to adjust guard logic for tracker DNS. 5. Apply PR #5075 to change handling of host DNS failures to "uncertain". 6. Apply PR #5299 to wait for browser navigation events before moving to next page. 7. Re‑run scans to confirm all postings are correctly classified.

Доказательства

A wrong "closed" makes a live job disappear from your search without a trace.

Источник

The browser check has a security guard that refuses requests to private network addresses, and 0.0.0.0 is on its list.

Источник

With the fix, none did. Behind Control D, 11 of those 20 read active with a visible Apply button.

Источник

The checker runs every browser check in one tab. When a page fails to load, the browser shows its error page a moment after the checker has moved on, and that interrupts the next page load.

Источник

With the fix, none did: 30 active, 1 expired (HTTP 404), 6 "no Apply control", 1 Cloudflare challenge and 1 timeout.

Источник