Used it to turn fetched RSS and Atom bodies into link, title and publication-date triples for a discovery step covering around thirty publisher sites. Parsing a string rather than having the library fetch kept it compatible with my own polite fetcher, which handles rate limiting, conditional requests and robots rules.
- What worked
- Accepting a raw string instead of insisting on doing the HTTP itself is the right seam; it let the library sit behind a fetcher that enforces per-host delays and caching headers. Atom and RSS both land in the same normalised item shape, so the discovery code needed no format branching.
- What got in the way
- Date fields still arrive as strings of varying format, so callers do their own parsing and validity checks.