5 Commits

Author	SHA1	Message	Date
zipair-bot	36e9be3651	chore: update last_seen to [297, 298, 300, 307, 308, 309, 313, 316, 317, 318, 319, 320, 321, 327, 329, 330, 335, 336, 340, 344, 345, 346, 349, 350, 352, 355, 356, 357, 359, 360, 361, 362, 364, 365, 369, 371, 372, 375, 377, 379, 381, 387, 390, 391, 392, 393, 395, 397, 399, 400, 404, 405]	2026-06-09 03:00:58 +00:00
zipair-bot	c0909e276d	chore: update last_seen to [297, 298, 300, 307, 308, 309, 313, 316, 317, 318, 319, 320, 321, 327, 329, 330, 335, 336, 340, 344, 345, 346, 349, 350, 352, 355, 356, 357, 359, 360, 361, 362, 364, 365, 369, 371, 372, 375, 377, 379, 381, 387, 390, 391, 392, 393, 395, 397, 399, 400, 404]	2026-06-04 02:01:02 +00:00
isky	2ce66aba10	feat: switch to BFF JSON API for notification discovery ... Replace HTML scraping with a direct call to bff.zipair.net/v1/information via FlareSolverr. The BFF returns clean JSON (id, title, category, publishedAt) — no regex parsing of rendered pages. Also adds first-run seeding to avoid alerting on all historical notifications. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-17 19:41:13 +08:00
isky	7487b5f630	feat: switch to FlareSolverr + slug-based notification tracking ... - All ZIPAIR fetches now go through FlareSolverr at 192.168.10.76:8191 - Dropped sitemap/probe approach; scrape EN notification listing directly - State file now stores JSON list of seen slugs instead of last integer ID - Matches keywords against slug and full page content Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-17 16:41:15 +08:00
isky	889da03dc8	feat: initial ZIPAIR Singapore sale monitor ... Polls ZIPAIR sitemap every 10 min via Gitea Actions, detects new Singapore/winter notifications, and fires an ntfy push alert. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-17 15:57:00 +08:00