neemypeemy ❤
26 posts
Tesla vs GDP 💥📊 Why TSLA’s 2030 Price Target Just Exploded 🚀 x.com/i/broadcasts/1…
English
@Benemortasia666 @engineering @elonmusk @Support @X Great job @Benemortasia666! I hope you get the recognition you deserve.
English
neemypeemy ❤ retweetledi
Dear @engineering @elonmusk @Support @X
I would like to make a suggestion for implementing the following missing API functionality.
The use case: There are many crypto/finance related X accounts that have 30 to 400+(in rare cases) impersonators.
They are highly aware of that issue, receiving messages from people that got scammed by the impersonator accounts.
But the volume is simply too much for them to manually stay on top of the reporting, to do something about it.
Resulting in them realistically not making any reports.
What is missing: There currently is no API endpoint for making violation reports, other than Spam.
Any other violation is not possible to report by API, and can only be done by web/app users, manually.
Which takes people about 15seconds per report.
What do we need: A new endpoint to be able to report one or a bulk of accounts, for impersonating 1 specific account.
The single endpoint should accept a twitter_id for the account being impersonated, and the twitter_id of the impersonator.
The bulk endpoint should accept a twitter_id for the account being impersonated, and a list(dictionary) with impersonator twitter_id's.
Note: You could simply port the x.com/i/api/1.1/repo… endpoint with selective_choices "DeceptiveIdentitiesOption" being used on the website, to a V2 endpoint 🙏
English
@investanswers Tomorrow is going to be a great day for all of us. ❤️
English