Lookup x.com urls using publish.twitter.com #537
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that Twitter is forcing more front-end urls to x.com, embedding x.com urls https:/x.com/API/status/1050118621198921728 can still use the https://publish.twitter.com/oembed endpoint.
Added x.com url matching to
resources/oembed.php
under'https://publish.twitter.com/oembed'
.Also works equally well under its own x.com key. This strategy might be a little more future-proof if they ever fully move the developer tools over to x.com, but currently publish.x.com/oembed is just a redirect back to publish.twitter.com/oembed.