TwitterWebViewer has been permanently discontinued
This topic is genuinely contested — read the individual model responses for different perspectives.
Models agree on
- ✓TwitterWebViewer has been permanently discontinued as of June 2024
- ✓The endpoint `/i/web/status/:id` now returns HTTP 410 Gone
- ✓Migration to official Twitter widget, OEmbed endpoint, or Twitter API v2 is required
- ✓Compliance with Twitter's Display Requirements is necessary for API-driven renders
- ✓Immediate actions include auditing codebases and updating documentation
TwitterWebViewer, a lightweight web-based tool that allowed users to view tweets without signing in or loading the full Twitter UI, has been permanently discontinued as of June 2024. This discontinuation affects various use-cases, including embedding tweets on blogs, intranets, or legacy apps, quick preview links for non-authenticated users, and automated screenshots for reporting. The endpoint /i/web/status/:id now returns HTTP 410 Gone, and all existing embed codes using https://platform.twitter.com/widgets/webview/… are broken. Users and developers must now migrate to supported alternatives like the official Twitter widget, the OEmbed endpoint (https://publish.twitter.com/oembed?url=https://twitter.com/user/status/ID), or the Twitter API v2 (/2/tweets/:id). For those needing a bare-bones view, pulling tweet data via the API and rendering it yourself is an option, but compliance with Twitter's Display Requirements (attribution, link back, etc.) is mandatory. Immediate actions include auditing codebases for /webview/ URLs, updating CMS plugins, and documenting changes. Performance and rate-limit considerations must also be addressed when switching to the API or OEmbed services.
Follow-ups
You just saw open-source models answer
Want GPT-5, Claude, Gemini & more on the same question?
Sign in free to run any question against frontier models — side by side, same synthesis, honest comparison.