[wp-trac] [WordPress Trac] #59142: X/Twitter posts cannot be embedded

[WordPress Trac]

#59142: X/Twitter posts cannot be embedded
-------------------------+-----------------------
 Reporter:  aphandersen  |       Owner:  (none)
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.7
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------

Comment (by peterwilsoncc):

 I've repeated my once-per-release tests of Xitter's responses:

 `https://publish.x.com/oembed\?url\=https://x.com/WordPress/status/1819377181035745510`
 Redirects to
 `https://publish.twitter.com/oembed?url=https://x.com/WordPress/status/1819377181035745510`
 Which embeds the URL
 `https://platform.twitter.com/embed/Tweet.html...[snipped]`

 The embedded iframe links the source tweet as
 `https://twitter.com/WordPress/status/1818791285894844581?...[snipped
 query string]`
 which redirects to
 `https://x.com/WordPress/status/1818791285894844581?...[snipped query
 string]`

 tl;dr: X (formally Twitter) is still returning a mix of x.com (formally
 twitter.com) and twitter.com (now x.com) domains in their embed responses.

 This makes it difficult to know what will happen in the future and how it
 will affect embeds created while their servers are in this state.

 @swissspidy I can't decided:

 a) whether these changes should go in or wait until X (formally Twitter)
 stabilizes their server responses to the new domain?
 b) if the changes go in, is it best to refer to publish.x.com or
 publish.twitter.com?

 What do you think?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59142#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform