Closed
Description
I suspect there is a migration happening over at Twitter, all URLs seem to redirect to x.com.
But I also see a form like this as the final destination of the redirects, not sure what that is about.
I put some debug code somewhere to see the response body.
If I submit the form I just end up at x.com...
<!DOCTYPE html>
<head>
<title>x.com</title>
<meta http-equiv="refresh" content="5; url = https://twitter.com?mx=1" />
</head>
<form action="https://x.com/x/migrate" method="post" name="f">
<input type="hidden" name="tok"
value="[SEEMS LIKE A JWT TOKEN]" />
<input type="hidden" name="data"
value="[SOME LONG DATA]" />
</form>
<script type="text/javascript" charset="utf-8"
nonce="[NONCE]">document.forms.f.submit()</script>
</body>
</html>
Posting here in case others find the same issue, maybe we figure it out or maybe it again changes along the way.
Metadata
Metadata
Assignees
Labels
No labels
Activity
JanMisker commentedon May 17, 2024
Maybe the oembed API can be utilized?
https://developer.x.com/en/docs/twitter-for-websites/oembed-api
oscarotero commentedon May 18, 2024
It's already using it.
Screenshot from my local:
JanMisker commentedon May 18, 2024
Ah of course. Sorry I didn't do much digging yet.
But still, the data collecting fails, I think because first there is an attempt to load the actual url, and only after that the oembed is fetched.
Vitorinox commentedon Oct 31, 2026
Hi @JanMisker, PR #589 should fix this: twitter.com and x.com URLs now always use the oEmbed from publish.twitter.com with the original URL, so redirects to the login wall no longer break the result.
You can test it with
composer require embed/embed:dev-fix/4.5.5. We will leave the PR open for a few days before releasing 4.5.5, so any feedback is very welcome!Fixes for 4.6.1 (#589)