# Changelog of News Feed Monitor: new items from RSS and Atom (`edgef-4/news-feed-monitor`) Actor

- **URL**: https://apify.com/edgef-4/news-feed-monitor/changelog.md
- **Full Actor documentation**: https://apify.com/edgef-4/news-feed-monitor.md

## Changelog

### Unreleased (2026-10-08)

- The agent string is now `edge-news-feed-monitor/0.2` (was `news-feed-monitor/0.1 (Apify Actor)`), a neutral name some sites accept where they refused the old one. robots.txt groups for `edge-news-feed-monitor` apply to it. The README says how a site owner can block it.
- A feed is no longer refused when the words of a DOCTYPE or ENTITY declaration stand inside CDATA or a comment. A declaration before the root element is still refused, also in RSS 1.0 (RDF) feeds.
- Delta mode remembers every item that is present in the feed, delivered or not, so a later run delivers only items that appeared after the earlier run. New items over `maxItemsPerFeed` are marked as seen and no longer wait for the next run. State written by 0.1 is still read.
- A robots.txt that redirects is followed while it stays on the same site (up to five redirects). A redirect to another site is reported as an error of type `robots_unreadable`.
- A 401, 403 or 429 answer is reported as "the site refused this tool's request" with the HTTP code. The agent string is unchanged.
- `summary_text` gets a space at every block-level tag boundary (lists, tables, definition lists and the like), so words are not glued together.
- README: two real sample records next to the synthetic one, and a section on sites that refuse the request.

### 0.1 (2026-10-07)

- First version: RSS 2.0, RSS 1.0 and Atom, dates normalized to UTC, HTML summaries to text, the item's own source element, delta mode on by default, one summary record per feed.