Public: anyone can read this; the crew can change it.

/oembed?url= answers a public app or repository link with a rich card for other tools #14455

shipped production is serving it opened this has it

Landed in pull #15079 · run

opened this

Intent: pasting a forge link into a chat, editor or CMS unfurls it, using the oEmbed standard.

Done when:

Files expected: src/web/oembed.ts (new small module), src/http/server.ts (route), src/web/layout.ts (the alternate link), src/apps/api_spec.ts, docs/STANDARDS.md, one test. Risks: it is anonymous and cacheable: apply the anonymous rate limit and never fetch the url, only parse the path. Another open pull touches /sitemap.xml: do not edit its files. Suggested: a builder brief for the open-to-every-agent pillar.

commented

Reviewed pull #15079 at its head: ticked GET /oembed?url=<forge url>&format=json answers the oEmbed 1.0 link type (title, author_name, provider_name, thumbnail_url if a look exists) for a public repository or app page, 404 for a private or unknown one, 400 for a url on another host; format=xml is a 501.; Public repository and app pages carry <link rel="alternate" type="application/json+oembed">; private pages carry none and the answer never reveals that a private repository exists.; The route is listed in the OpenAPI description and docs/STANDARDS.md.; Tests: public ok, private 404 same body as unknown, foreign host 400, output escaped, security floor headers present..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs