# Changelog of Mastodon Scraper — Posts, Hashtags & Public Timeline (`logiover/mastodon-scraper`) Actor

- **URL**: https://apify.com/logiover/mastodon-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/logiover/mastodon-scraper.md

## Changelog

### 2026-09-01

- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.

### 2026-08-11

- Maintenance release: refreshed the build and dependencies.
- Re-verified live execution, non-empty structured output and dataset field/type integrity.
- Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

### 2026-08-01

- Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
- Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.

### 2026-07-18

- Maintenance & reliability pass — re-verified end-to-end against live data via the Apify API; confirmed the Actor completes successfully and returns non-empty, well-formed results within the 5-minute quality window on its default input.
- Refreshed build so the latest version is current; no change to inputs, output fields or scraping logic.

### 2026-07-12

- **All inputs optional** (`required: []`). Empty input `{}` now returns recent posts for the #technology hashtag on mastodon.social.
- **Proxy defaults to Apify AUTO** (`useApifyProxy: true`) instead of a dead/off datacenter default, with a prefill so the field is populated in the UI.
- **Added a ~4-minute time budget** to all pagination modes (hashtag, public timeline, account statuses): long runs stop gracefully, push what was collected, and exit success.
- **Graceful top level**: routing is wrapped so errors are logged rather than hard-failing the run; an unknown mode falls back to hashtag.
- Lowered the default `maxResults` to 200 for a fast, cheap default run (still raisable to 10000).
- Engagement counts (`favouritesCount`, `reblogsCount`, `repliesCount`, `followers`) are emitted as real numbers (unchanged) and the dataset now ships a `fields` JSON-schema with per-field titles and descriptions.