Alternative discovery mechanism
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names providers/manifest.yml and proposes a root-level oembed.json; start by reading the current registry and per-site link-tag discovery approaches, then review the nine-comment discussion. Done means the extension's location, response format, and CORS behavior are specified clearly enough for implementation.
Written by the indexing model from the issue text.
Description
Hi there,
I much appreciate the spec! Now I am wondering (and do let me know if this is an old discussion), if there is interest in an extension which would allow for a site-wide discovery mechanism. I.e. from what I can tell currently a provider can either
- list themselves in the registry or
- put a link-tag on the specific site which should be embeded.
Now for my use case both are not feasible paths, because
- I am looking at a federated roaster of domains which rotate a lot, so registering them is too manual of a process.
- I want to know about embed-ability from a CORS-secured context, where I can not request (and for size reasons, also don't want to) it on a per-URL basis.
So I was wondering if there would be interest in a spec extension for exposing sth similar to the providers/manifest.yml on a top-level (in a possibly CORS friendly way)?
I'm not entirely sure yet how it'd look like, I guess the simplest version would be to serve a oembed.json on the root. I understand this is not the most backwards-compatible way, since it also infringes on web developers freedom to use all their routes to their liking.
Then again with sitemap.xml or robots.txt, there is some precedence for hardcoded files, so it might actually be fine?
- Dominant language
- PHP
- Stars
- 1.4k
- Forks
- 773
- Avg merge
- 11h 21m
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from iamcal/oembed
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
iamcal/oembed#843 · 2 comments ·
Maintainers usually reply within 1 day
-
stale
Difficulty 1/5 Under an hour Newbie friendliness 72/100
iamcal/oembed#801 · 1 comment ·
Maintainers usually reply within 1 day
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
iamcal/oembed#803 · 1 comment ·
Maintainers usually reply within 1 day
-
stale
Difficulty 5/5 Over a week Newbie friendliness 35/100
iamcal/oembed#686 · 4 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
stale
Difficulty 5/5 Over a week Newbie friendliness 20/100
iamcal/oembed#614 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Yoast/wordpress-seo#23658 ·
Maintainers usually reply within 3 days
-
fixed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
firefly-iii/firefly-iii#12934 · 2 comments ·
Maintainers usually reply within 1 day