3 ms·
> I assume the post is suggesting the Twitter api has been "removed" in relation to the reader apps being blocked. Your assumption is right, that’s what I was
by mrzool 4y ago
> I assume the post is suggesting the Twitter api has been "removed" in relation to the reader apps being blocked.
Your assumption is right, that’s what I was hinting at. I might be wrong but I strongly suspect this is all intentional.
> Anyone got more context on what the "missing" page was?
I don’t know exactly, I assume some sort of landing page with links to your aforementioned resources.
EDIT: Here’s the Web Archive link:
https://web.archive.org/web/20221119170753/https://developer.twitter.com/apitools/ https://web.archive.org/web/20221119170753/https://developer...
- samwillis 4y agoAh, looking at the archived page, I remember someone in the earlier related threads saying that Twitters own "API Explorer" was down and seemed to be be experiencing the same issue as the blocked apps. I think this must have been that?!
- eecc 4y ago[flagged]
- CommitSyn 4y ago> strongly suspect this was intentional Considering the 404 of that page > This page is down > I scream. You scream. We all scream... for us to fix this page. We’ll stop making jokes and get things up and running soon. vs the 404 of other developer.twitter/error pages > You've washed ashore on null island > Sadly, the party is over. Head back to the mainland. Or, if you're up for some exploring, try the search bar above. I'd say it's quite likely rub-it-in-your-face intentional.
- Nullabillity 4y agoThat looks more like a 500 error to me.
- devilcius 4y agoIn fact the server returns a 503 Service Unavailable