Closed adrien-chinour closed 9 months ago
Your PR has been merged and site has been updated, thanks.
Using the central registry via HTTP is highly discouraged - you should instead use the discovery mechanism to allows services to consume OEmbed resources: https://oembed.com/#section4
If you need to consume the registry data, please use the NPM package as detailed in the README.
Adding x.com as provider due to twitter rebranding.
It's the same oEmbed api but with domain x.com.
Using same provider but with x.com content not working (404) :
Using oEmbed api on platform.x.com working (302->200) :
710