# Changelog of Scraper for Truth Social — User Posts, Replies & Engagement (`logiover/truth-social-posts-scraper`) Actor

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

## Changelog

### 2026-10-18

- Truth Social's Cloudflare started refusing most datacenter IPs in mid-October (measured from the platform: 3–4 of 16 requests passed, against 16 of 16 from US residential IPs). The scraper now chooses its own exits — US residential first, other residential and datacenter as fallbacks, a new IP on every refusal — so runs no longer lose handles or end empty. Residential traffic is included in the price per result.
- A run that hits its "Max cost per run" now stops at the right number of results; previously every result was counted twice towards that limit.
- Posts are saved one page at a time (faster), each request has a 40-second ceiling across all its retries, and a run that reaches its time limit ends with the posts it has and says so.
- The example input uses accounts with public timelines (the NASA account has none).
- The run now leaves a SUMMARY record (posts per account, skipped accounts and why, proxy route statistics).

### 2026-10-15

- A request that stalls is now abandoned after 20 seconds and retried at most four times on fresh IPs, instead of holding a handle for minutes; together with a deadline taken from the run's own timeout, a short run now ends inside it with the posts it has.
- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.