search

xdevplatform / open-evolution

Open evolution proposals for the Twitter API
https://twittercommunity.com/t/introducing-twitter-open-evolution/158770
41 stars 15 forks source link

Create 000-retweets.md #4

Closed igorbrigadir closed 3 years ago

igorbrigadir commented 3 years ago

Add a proposal to modify the retweets API https://developer.twitter.com/en/docs/twitter-api/tweets/retweets/api-reference/get-tweets-id-retweeted_by

github-actions[bot] commented 3 years ago

CLA Assistant Lite bot All contributors have signed the Developer Agreement. If the commit check is not passing, a maintainer must go the Checks tab of this PR and rerun the GitHub Action.

igorbrigadir commented 3 years ago

I have read and agree to the Twitter Developer Agreement and Policy

igorbrigadir commented 3 years ago

recheck

igorbrigadir commented 3 years ago

Any response to this or any of the other proposals?

bhalsey commented 3 years ago

Thank you for your contribution! Our engineering team is reviewing your proposal and will provide feedback in a couple weeks.

igorbrigadir commented 3 years ago

Thanks! Let me know if there's anything else you'd like me to add - this feature (knowing the exact retweet id) is essential for studying spread of information

bhalsey commented 3 years ago

Thank you for your submission. The review team is moving this proposal to a Revision needed status. This means there are a few changes we’d like you to make before we can accept the proposal.

-Adding an endpoint with the URL path of /2/tweets/:id/retweets would make it clearer this returns tweets and mitigates the id confusion mentioned.

-Can you expand on the metadata of the retweet you are interested in?

-Under Alternatives Considered, can you add mention of a couple of other products: -The Account Activity API (AAA - available for Enterprise and Premium customers) provides retweet information for followed users. But this does not provide historical information, and event delivery is pushed via webhooks. -We also support retweets_of_status_id: in PowerTrack (not available in v2 filtered stream). Just like AAA, it only returns real time results. This is also available via Historical PowerTrack, but it is only available to enterprise users and managed customers.

Once those changes are committed, we will accept the proposal. Please let us know as soon as your changes are made so we can accept them quickly.

As a reminder, note that an approval does not guarantee an implementation; it means we agree in principle with the proposed changes and we will consider implementing. There are circumstances that may prevent implementation (for example, further privacy and security review, a change in roadmap or priorities, or a scheduled release of functionality that supersedes this proposal).

igorbrigadir commented 3 years ago

@bhalsey thanks! Updated! I also added a better example of the expected output.

bhalsey commented 3 years ago

Thank you for incorporating our feedback. Good news: the review team has approved your proposal!

Note that an approval does not guarantee an implementation; it means we agree in principle with the proposed changes and we will consider implementing. There are circumstances that may prevent implementation (for example, further privacy and security review, a change in roadmap or priorities, or a scheduled release of functionality that supersedes this proposal).

We’re very happy to see your contribution shaping the Twitter API, and we are grateful for the time and effort you put in authoring a proposal.

Thank you!

igorbrigadir commented 3 years ago

Awesome! Thanks!