blogwatcher

blogwatcher tracks blog and RSS/Atom feeds and nothing else, which is a feature. Install is a single Go module and the command surface is tiny: ```bash go install github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest blogwatcher add "My Blog" https://example.com blogwatcher scan # finds new articles blogwatcher articles # list what's tracked blogwatcher read 1 # mark one read blogwatcher read-all ``` `blogwatcher scan` reports source type (RSS/Atom) plus found/new counts per feed, which is exactly the signal you want to pipe into a digest. No DB to babysit, no daemon.

Use case: Powering a daily 'what's new on the blogs I follow' digest from a cron job.

# blogwatcher in 5 Minutes blogwatcher tracks blog and RSS/Atom feeds from the command line. One binary, one job. ## Install ```bash go install github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest blogwatcher --help ``` ## Core Loop ```bash blogwatcher add "My Blog" https://example.com # track a feed blogwatcher blogs # list tracked blogs blogwatcher scan # find new articles blogwatcher articles # list known articles blogwatcher read 1 # mark #1 read blogwatcher read-all # mark everything read ``` `scan` prints a per-feed summary — source type (RSS or Atom), found count and new count — which makes it easy to drive a digest: ``` $ blogwatcher scan Scanning 1 blog(s)... xkcd Source: RSS | Found: 4 | New: 4 Found 4 new article(s) total! ``` ## Wiring It Into a Cron Digest ```bash # daily 08:00 job 0 8 * * * blogwatcher scan && blogwatcher articles >> /tmp/digest.txt && blogwatcher read-all ``` Marking everything read after building the digest keeps the next run's output to only new items. ## Tips - Use `blogwatcher <command> --help` to discover flags; the surface is intentionally small. - Prefer `read-all` at the end of a digest run so 'new' stays meaningful. - There's no daemon: run `scan` on demand (cron is the right host for it).