[wp-trac] [WordPress Trac] #50861: Remove Facebook and Instagram as an oEmbed Source

[WordPress Trac]

#50861: Remove Facebook and Instagram as an oEmbed Source
--------------------------------------+-----------------------
 Reporter:  whyisjake                 |       Owner:  (none)
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  5.5.1
Component:  Embeds                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+-----------------------

Comment (by davisshaver):

 Does WordPress.org have any institutional relationship with Facebook?
 Given the scope of this change I wonder if a channel could be created to
 discuss issues of mutual interest.

 Reconsideration or postponement would both be nice outcomes given the
 potential issues here, but even if those aren't options, Facebook could
 provide guidance or support which may assist the community in implementing
 a transition strategy.

 From a journalistic perspective these oEmbed links are often material to
 reporting/storytelling. In the event that oEmbed links revert to raw
 links, readers may not understand that they need to click the link to view
 the supporting material, and story flow/comprehension may be impacted as a
 result. It would be unfortunate for this regression to occur at all, but
 especially at the end of October when American media will be in the final
 countdown to a presidential election.

 Even better than a postponement would be some means of allowing open
 access for editorial purposes. My understanding is that the "o" in
 "oEmbed" stands for open. While the oEmbed spec doesn't appear to directly
 comment on this, at the least requiring authorization for oEmbed endpoints
 seems to be unusual. Embedly is one major provider that does this, but
 they also serve a different use case in the oEmbed landscape than most
 services. Facebook may ultimately still need to restrict the endpoint but
 there could be relevant considerations of oEmbed's design intent that may
 cause them to reconsider.

 Lastly, if authorization does become necessary, I wonder if major hosting
 providers like WordPress.com, WordPress VIP, and other managed platforms
 could provide this feature for clients using specially designated app
 access tokens. Given the ubiquity of WordPress and Facebook we have an
 opportunity to benefit a large percentage of overall sites on the internet
 if we convene a small number of companies to address this at a systems
 level.

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