gazouilloire
gazouilloire copied to clipboard
Prepare the future dropout of API v1.1
https://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888
Argh?
Ils vont ouvrir une autre route remplaçante, et y aura 6 mois de période de recouvrement où les deux routes marchent, mais jusqu'ici leurs nouvelles routes renvoient des données dans un format très différent, donc il va falloir recoder certains bouts. Et l'accès aux nouvelles routes est un peu plus pénible en termes de clés d'API (les clés existantes ne permettent pas directement de taper dessus, il faut faire une demande spécifique en plus pour chaque jeu de clé...)
Still no date for the dropout, but things are advancing https://blog.twitter.com/developer/en_us/topics/tools/2020/introducing_new_twitter_api.html
https://twittercommunity.com/t/announcing-early-access-to-the-next-generation-of-the-twitter-api/139612
A few more info https://twittercommunity.com/t/the-academic-research-take-on-early-access-to-the-new-twitter-api/139697
New fields to grab https://twittercommunity.com/t/conversation-reply-settings-tweet-field/147169
extra features in v2 reserved to academic accounts for improved stream quality: https://twittercommunity.com/t/new-reliability-and-recovery-functionality-available-for-twitter-api-v2-streaming-endpoints/156244
New alt_text field should include image description when available https://twittercommunity.com/t/media-alt-text-field-now-available-in-twitter-api-v2/157939
La fin approche... Toujours pas de date, donc a priori plus d'un an, mais plus beaucoup plus https://twittercommunity.com/t/ushering-in-a-new-era-for-the-twitter-developer-platform-with-the-twitter-api-v2/162087 https://blog.twitter.com/developer/en_us/topics/tools/2021/build-whats-next-with-the-new-twitter-developer-platform
It's getting closer https://twittercommunity.com/t/deprecation-announcement-removing-compliance-messages-from-statuses-filter-and-retiring-statuses-sample-from-the-twitter-api-v1-1/170500
As of now, gazouilloire v1's streaming part will only keep working with preexisting API v1 keys since new apps won't be able to use the stream v1.
"we are announcing the deprecation of the v1.1 streaming statuses/filter endpoint, with a formal deprecation date of March 9, 2023."
Nooooooooooooooooooo
They're 6 days late but here it is, the v1.1 stream now returns the following :(
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Error 403 Please use V2 filtered and sample volume stream as alternatives</title>
</head>
<body>
<h2>HTTP ERROR: 403</h2>
<p>Problem accessing '/1.1/statuses/filter.json'. Reason:
<pre>Please use V2 filtered and sample volume stream as alternatives</pre>
</body>
</html>
(and yes, the </p>
is missing...)
As discussed earlier, we should probably now release a new version that does not even try to connect to the stream as it generates a lot of undesired and repetitive logs while trying to connect in loop.