Support for auto-discovery mechanism

[PaulKiddle]

The oEmbed spec supports a discovery mechanism that allows sites to advertise their oEmbed settings through the Link header. This is particularly useful for decentralised services like PeerTube that can be run at multiple different domains.

Would you be open to the inclusion of a discovery extractor into this codebase? It could be opt-in to allay any security concerns.

Due to the complexity of parsing the Link header, it would probably require an external dependency for this task, such as the https://github.com/kelunik/link-header-rfc5988/ library.

[KaneCohen]

Hi, thanks for the suggestion, I'll look into it, but I'm a bit reluctant about adding such functionality. This as you note would most likely require extra dependencies which I would prefer to avoid.

[KaneCohen]

You mean ability pass in the JSON from the third party Oembed output in order to use it as a data to make the final media? Best, Kane

…

On Wed, Dec 3, 2025 at 16:30 Paul Kiddle ***@***.***> wrote: *PaulKiddle* left a comment (KaneCohen/oembed#13) <#13 (comment)> Understandable, as a workaround perhaps the ability to pass in a custom extractor during runtime so that this functionality can be added as an extension? — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAENHF4IA3VBQKIWYWDYSYT372UUXAVCNFSM6AAAAACNOZO3W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBVHA4TQMRWGM> . You are receiving this because you commented.Message ID: ***@***.***>

[PaulKiddle]

I deleted my post - I realised I was basically just asking for the ability to extend the getExtractor function to return a custom extractor, which is already possible.