Skip to content

fix(twitter): restore hardened reply flow - #10

Merged
kannch8765 merged 1 commit into
mainfrom
fix/restore-twitter-reply
Sep 9, 2026
Merged

kannch8765 merged 1 commit into
mainfrom
fix/restore-twitter-reply

Conversation

@kannch8765

Copy link
Copy Markdown
Owner

Restore the Twitter reply adapter from the previously tested fix/twitter-upstream-sync / upstream PR nashsu#65 state.

Why:

  • The reader recovery restored notifications/followers/following, but reply hardening from the same Aug 30 sync never entered fork main.
  • Current OpenCLI clis/twitter/reply.js has had no commits since 2026-08-30, so the old AutoCLI port is still based on the current upstream reply behavior.

Restored behavior:

  • use X's dedicated compose/post?in_reply_to= composer
  • parse/validate status URLs from a known-safe X page rather than direct arbitrary navigation
  • tolerate the positional ordering seen in the wrapper path
  • verify inserted Draft.js text
  • support both tweetButton and tweetButtonInline
  • require fresh success/failure toast evidence instead of click-implies-success
  • return an explicit unconfirmed failure if submission cannot be verified

Validation:

  • restored reply.yaml blob is byte-for-byte identical to the final old tested branch (0cde6b185fe3a0366e8cf8b32a44ae6eece1c0ae)
  • YAML parse passes
  • both embedded evaluate snippets pass node --check after template substitution
  • no live reply was sent during validation

@kannch8765
kannch8765 merged commit 8a51124 into main Sep 9, 2026
@kannch8765
kannch8765 deleted the fix/restore-twitter-reply branch September 9, 2026 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant