Data source

Follow Checker uses X’s official OAuth 2.0 authorization flow and X API v2. It requests only tweet.read, users.read, and follows.read. It does not request permission to post, follow, unfollow, read direct messages, obtain email, or remain connected through offline access.

Activity-date calculation

  1. The connected user authorizes read-only access on X.
  2. The scanner requests one page of accounts the user follows.
  3. X may supply a most_recent_tweet_id for each profile.
  4. X documents that Snowflake IDs encode a creation timestamp. The scanner derives that timestamp and compares it with the current date.
  5. The interface labels the resulting date as approximate.

Follow Checker does not retrieve the text, media, likes, or engagement of that Post for the inactivity calculation.

Unknown does not mean inactive

A missing recent Post ID is reported as unknown. It may represent an account that never posted, deleted content, became protected, was limited, or could not be represented by the returned API data. The scanner does not invent a date or automatically recommend unfollowing.

Temporary processing

The access token is encrypted inside an HTTP-only browser cookie, expires within two hours, and is removed when the user ends the session. Scan results remain in the current browser page; the current design has no profile database. CSV files are assembled locally in the browser.

Spending control

Results are requested in small pages. A user must explicitly request each additional page. The interface displays an estimate based on published X rates, while the X Developer Console remains the billing authority.

Primary technical references