[Question] X tool

[AbdulShahzeb]

G'day @cmac86

I’m currently working on a tool to integrate with X, and progress is going smoothly so far.

I wanted to get your thoughts on whether the tool should support interacting with existing tweets (e.g. reply, quote, like, retweet), versus focusing purely on content creation and discovery. The main consideration is that interacting with existing tweets requires a URL (or ID), which isn’t particularly practical for a voice assistant-driven workflow.

Given that constraint, one option would be to shelve tweet interaction functionality for now, and instead focus on:

• creating original tweets
• sending DMs
• searching tweets and users by keyword

That said, if you’d prefer to keep tweet interaction functionality available for text or transcript-based usage, I’m happy to leave it in. From my perspective, those flows feel less ergonomic for most users compared to direct interaction on X website/app, as they require copying and supplying a tweet URL or ID, but I’m open to your thoughts on whether the added coverage is still worthwhile.

Also, please let me know if opening an issue is the best place for questions like this, or if there’s a better channel you’d prefer for discussion.

Cheers,
Abdul

[cmac86]

Hey Abdul, thanks for the thoughtful question - and great instincts here.

PR #62 looks good as-is. Focusing on create, DM, and search is the right call for a voice-first tool. Tweet interaction (reply, like, retweet) requires passing URLs or IDs which doesn't translate well to a voice workflow - users are better off doing that natively in the app.

For future questions like this, let's use the https://github.com/CoreWorxLab/CAAL/discussions - I'll add a Tool Development category there so tool builders have a central place for design questions, feedback, and ideas. Going to close this issue out but the conversation continues there.

Cheers
cmac