Skip to content

Add opt-in Xquik posting backend#3

Open
kriptoburak wants to merge 1 commit into
lewispour:mainfrom
kriptoburak:codex/add-xquik-backend
Open

Add opt-in Xquik posting backend#3
kriptoburak wants to merge 1 commit into
lewispour:mainfrom
kriptoburak:codex/add-xquik-backend

Conversation

@kriptoburak

Copy link
Copy Markdown

Summary

  • add TWITTER_BACKEND=xquik as an optional posting backend
  • keep Tweepy as the default backend for CLI, web UI, and direct scripts
  • add unit tests for Xquik configuration and accepted writes

Validation

  • python3 -m unittest -v tests/test_xquik_client.py
  • python3 -m compileall cli.py web.py src tests
  • git diff --check

@lewispour

lewispour commented Jun 23, 2026

Copy link
Copy Markdown
Owner

Xquik appears to be a subscription based API with paid pricing, I cannot test the functionality without a paid account.

@kriptoburak

Copy link
Copy Markdown
Author

Thanks for checking. You do not need Xquik credentials to verify the unchanged default flow: Tweepy remains the default backend, and the Xquik path is covered by mocked unit tests. It is opt-in only for users who set TWITTER_BACKEND=xquik with their own connected account. Happy to keep it out if you prefer this project to stay limited to direct X credentials.

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.

2 participants