The thing I’m going to complain about is a shame. I know that being rude doesn’t help to resolve an issue. But here, it’s not a bug, it’s a recurring bad behavior. Twitter dev platform shows again its incapacity of fulfilling basic good practice. I hope that this topic will help you folks to improve yourselves; or at least the quality of the API/docs.
Webhook retries count changed recently, and silently.
It was enjoyable to have 7 retries in AAA webhooks, mostly because it was done among a 4 hours window; allowing few hours of downtime without missing data irremediably (archive: [http://web.archive.org/web/20181227225655/https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/guides/activity-retries]).
New version: 3 retries among 5 minutes, you (co-devs) better not have a 5+ minutes downtime in your infrastructure, because it would cost you to lose data without being able to recover it.
BTW: you forgot to adapt the
If you do not confirm validation within these eight attempts, sentence.
No trace of this change in the changelogs, that’s a pity.
About “Client must use other Twitter endpoints to recover data.”
It is currently impossible to retrieve any (a n y) like of a tweet. Many devs requested that feature among the past, the only way of doing it was to use the AAA. But if the p a i d p r e m i u m v e r s i o n of the AAA cannot propose good retries, what can we do in the case of a 10m downtime? Nothing. Data is lost, forever.
So, intelligent people working for Twitter, please:
- be communicative
- be empathic & good-willing
- propose good & exhaustive third-party endpoints
The “get likes” endpoint exists for Twitter Official (Overly Premium) clients. It is (for example) the
/statuses/:id/activity/summary.json endpoint, reserved to old apps, new ones probably now use the version
2 of the API. Some tutorials & gists out there encourage to use these endpoints with [illegitimately obtained] official tokens.
My question is: why don’t you do something to ease our life using your API? Is it because of third apps not displaying your ads? You already slayed them enough by shutting down the user stream.
Thanks for your sense of comprehension.