Closed uadnan closed 3 years ago
Your PR has been merged and site has been updated, thanks.
Using the central registry is highly discouraged - you should instead use the discovery mechanism to allows services to consume OEmbed resources: https://oembed.com/#section4
Hi @iamcal! 👋 We have been using the discovery mechanism via the Link
header, but have not noticed it being used by oEmbed consumers. These are the headers for the example URL:
$ curl -I https://app.minervaknows.com/recipes/1d44cafd-946c-4607-b571-26220fd437ee/follow
HTTP/2 200
content-type: text/html
content-length: 2315
x-amz-id-2: bq/pXAwVxcIsf+NzhRQ7uKhqUAMIDfI8GiVzLI/aIuskZ6P2Dt0I8/cnmj73YLQvxDTRQM7TH18=
x-amz-request-id: 4VM0M5FCAR7X4QEC
date: Thu, 18 Mar 2021 14:08:49 GMT
last-modified: Tue, 16 Mar 2021 11:35:43 GMT
etag: "1c2f003f0adec5435f4e5f1057850440"
cache-control: no-cache
accept-ranges: bytes
server: AmazonS3
link: <https://oembed.minervaknows.com?url=https%3A%2F%2Fapp.minervaknows.com%2Frecipes%2F1d44cafd-946c-4607-b571-26220fd437ee%2Ffollow&format=json>; rel="alternate"; type="application/json+oembed"; title="Minerva"
x-cache: Miss from cloudfront
via: 1.1 4d95e17a6f22c6bea5ad0f9769f73450.cloudfront.net (CloudFront)
x-amz-cf-pop: EWR52-C4
x-amz-cf-id: dFobV3Fu6UGoTYKr9UawfaRhwDKS1qdX4PVel22lVJCQnZoHCaH2Ng==
We've had that in-place for a few weeks now with no preference being given to the Link
header from common consumers (Slack, Twitter). If you can provide some insight, that would be greatly appreciated.
That said, the oEmbed Link Viewer now uses the oEmbed information. Anyhow, thanks for merging! 🙌
I don't know about Twitter, but Slack does not actually support OEmbed for generic domains.
This PR will register Minerva as provider