Closed lacyg4 closed 3 weeks ago
We may want to think about renaming the /data/twitter/tweets/recent
endpoint to /data/twitter/tweets
@teslashibe updated the advance search option from Twitter and the acceptance criteria, please review the list of advance search options and let me know if this looks correct or we should remove some.
@giovaroma this looks fantastic - let move forward with this.
I have added this to a release in the roadmap here: https://github.com/masa-finance/roadmap/issues/2 (cc @mudler @H34D @Luka-Loncar)
I changed this to "In review" on product board added this to no-status in the protocol board and it can be groomed on Monday
Wonderful, moving tickets down the pipeline @teslashibe
potentially a duplicate of https://github.com/masa-finance/masa-oracle/issues/362 ?
Exact match documentation depends on #351
Exact match and advanced search should be tested first. @nolanjacobson
This has been done and QA'd, follow-up https://github.com/masa-finance/masa-oracle/issues/459
Problem
Users of the Twitter endpoint want more granular search capabilities. Our API supports advanced search this but its not documented. Advanced search queries can be constructed here: https://x.com/search-advanced?lang=en
We currently do not document examples of advanced search in the swagger documentation or developer documentation so people understand the full functionality of the twitter search API.
Here are some examples of advanced search queries:
These developer documentation can be found here: https://help.x.com/en/using-x/x-advanced-search
Customer feedback
https://masafinance.slack.com/archives/C078JCDS81E/p1719870998918199 https://masafinance.slack.com/archives/C073K1YP8CR/p1717494858189539
Acceptance criteria:
Documentation Structure:
Search Type Documentation:
Testing:
Advance search to support:
Possible solutions