Advanced X OAuth and verification

Advanced X Verification uses X OAuth 2.0 so CollabOS can identify the connected X account and perform required tasks only after the applicant explicitly presses the matching action button.

Stored X information

After a successful connection, CollabOS stores:

• X user ID
• X username
• X display name
• X profile image URL
• connected date
• encrypted access token
• encrypted refresh token when provided
• token expiry

Display rule

CollabOS uses the stored profile data for application, leaderboard, voter, and vouch UI. It should not call X again just to render a name or avatar.

Action timing and API cost control

CollabOS should:

• show separate Follow, Like, and Repost buttons
• perform an action only after the applicant clicks that exact button
• make one X write request for that action
• store the successful result and timestamp immediately
• return an already-completed task without making another X request
• prevent duplicate in-flight requests and limit retries after failures
• make final submission check the database only
• avoid list scans, polling, and scheduled verification
• cache required X account and post IDs

Failure messages

When required actions are incomplete, submission is blocked and the applicant should see the exact missing actions, for example:

You still need to complete:

• Follow @project
• Like the required post
• Repost the required post

OAuth sessions are short-lived. A user who returns with an expired or already-used authorization session must start Connect X again from the application page.