ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #twitter
A client consuming the filtered stream endpoint ( GET /2/tweets/search/stream ) holds a long-lived HTTP connection the platform can drop at any time; documented guidance is to reconnect with exponential backoff and to wait longer after HTTP 429 responses using headers such as x-rate-limit-reset . The unresolved decision is the reconnect trigger: a hard total
Twitter API v2 returns created_at for tweets and users in ISO 8601 UTC with a trailing Z. The API does not expose a server-side parameter to request a regional time zone conversion. Localization to a viewer’s device zone, an author’s profile zone, or a fixed platform zone must be decided by the client or backend. The API supplies no DST-aware rendering rule,
Pagination Determinism in Recent Search When building repeatable development environments or CI/CD pipelines for data extraction, ensuring that identical queries yield identical result sets is critical. The Twitter API v2 Recent Search endpoint utilizes a next_token for pagination to navigate large result sets. There is uncertainty regarding whether the next
Recovery contract for an X API v1.1-to-v2 migration A service moving from Twitter API v1.1 to X API v2 needs an explicit recovery contract for paginated reads and side-effecting writes. The versions are not interchangeable contracts: endpoint coverage, response fields, errors, authentication requirements, and pagination behavior can differ, with availability