ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #twitter
Twitter generates unique 64-bit IDs locally using a timestamp, worker ID and sequence counter, enabling approximate time ordering without a central sequencer.
Learn how to use Twitter API v2's next_token for reliable cursor‑based pagination, see a Python example that handles rate limits, and understand the trade‑offs involved.
Learn how to solve the 'Celebrity Problem' in real-time feeds by implementing a hybrid Fan-out-on-Write and Fan-out-on-Load architecture to balance latency and write amplification.
Learn how the fan-out pattern solves the read-latency problem in social feeds and why a hybrid push/pull model is necessary to handle celebrity accounts and write amplification.
A minimal yet robust architecture for a Twitter‑style timeline: decouple ingestion, use a fan‑out cache, enforce data boundaries, and monitor key metrics to keep latency low and privacy intact.
Pagination Window Stability in Recent Search When building an archival or monitoring workflow around the X API v2 recent search endpoint, the practical concern is whether repeated calls with next_token traverse a fixed snapshot or a continuously shifting index. The endpoint is documented to return Tweets from roughly the last seven days, but it is backed by
Explore how Twitter transitioned from a Ruby monolith to a JVM-based microservices architecture to solve the 'celebrity problem' using a hybrid fan-out strategy.
Reducing operational costs for low-traffic applications often involves migrating from the Elevated tier to the Essential (free) tier. While the Essential tier provides a monthly quota of 500k tweets and a 500 request-second limit, it removes access to premium features such as full-archive search. To further optimize bandwidth and request volume, developers c
Problem Overview The new Twitter API v2 introduces an opaque next_token cursor for all list endpoints. While the token must be passed unchanged to retrieve subsequent pages, the specification does not clarify whether each use of the same token counts as a distinct request for rate‑limit purposes. Goal Determine how repeated or delayed use of an identical nex
scala