Pull the actual gif rather than the page about it: a retrieval pattern for tenor, giphy, and imgur #1190

New issue

Open

opened 2026-08-22 22:15:16 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-22 22:15:16 +00:00

Member

Moved from coilyco-gaming/sirens-echo#996 by Darren (director seat), 2026-08-22, on Kai's decision. She commented there twice on 2026-08-19, "I think this might belong in aos" and then "almost certainly belongs in aos", and confirmed the move today. That issue is closed as moved and points here.

What it asks for

A way to pull an actual gif rather than a page about one. The flow as originally written:

search the site and view the result page
pull a gif id out of that page
construct the direct media URL from the id

Why it belongs here rather than in a lane repo

Nothing about it is specific to the Echo runtime. It is generic web tooling: fetch a page, extract an identifier, build a URL to the asset itself. Any agent with a fetch tool wants the same thing, and putting it in one Discord harness makes it reachable from exactly one agent.

The sibling work already split this way. coilyco-gaming/sirens-echo#1029 asked for a curated web-culture pack and its knowledge half shipped as a skill, sirens-deep-web-culture, carrying references for memes, gif culture, and comics. That half is reading and citing. This half is retrieving, and retrieval is the part with no lane in it.

What is deliberately not in scope

Sending a gif into Discord is a different issue and stays in the lane repo, at coilyco-gaming/sirens-echo#996's siblings #201 and #1031. This is only about getting the asset URL for something that has already been found.

The shape worth having

Tenor and giphy are the same shape: a landing page a human browses, plus a direct media host whose URL returns the bytes. Imgur is a third of the same. So the useful unit is not a tenor-specific helper but a small documented pattern for media hosts of that shape, with the per-site specifics as data rather than code.

Two things that will bite whoever builds it, both known:

Egress. The five hosts in the web-culture set were handed to DevOps as a fetch grant and never filed until today, now tracked at coilyco-bridge/deploy#772. A retrieval tool that cannot reach the host is indistinguishable from one that is broken, which is coilyco-gaming/sirens-echo#1088 exactly.
The direct media hosts differ from the landing host. Tenor serves assets from media1.tenor.com and c.tenor.com, so an allowlist naming only tenor.com grants the page and not the thing.

coilyco-gaming/sirens-echo#996 - the original, closed as moved
coilyco-gaming/sirens-echo#1029 - the web-culture pack, whose reading half shipped
coilyco-bridge/deploy#772 - the egress grant this depends on

**Moved from `coilyco-gaming/sirens-echo#996` by Darren (director seat), 2026-08-22, on Kai's decision.** She commented there twice on 2026-08-19, "I think this might belong in aos" and then "almost certainly belongs in aos", and confirmed the move today. That issue is closed as moved and points here. ## What it asks for A way to pull an actual gif rather than a page about one. The flow as originally written: * search the site and view the result page * pull a gif id out of that page * construct the direct media URL from the id ## Why it belongs here rather than in a lane repo Nothing about it is specific to the Echo runtime. It is generic web tooling: fetch a page, extract an identifier, build a URL to the asset itself. Any agent with a fetch tool wants the same thing, and putting it in one Discord harness makes it reachable from exactly one agent. The sibling work already split this way. `coilyco-gaming/sirens-echo#1029` asked for a curated web-culture pack and its knowledge half shipped as a skill, `sirens-deep-web-culture`, carrying references for memes, gif culture, and comics. **That half is reading and citing. This half is retrieving**, and retrieval is the part with no lane in it. ## What is deliberately not in scope **Sending a gif into Discord is a different issue and stays in the lane repo**, at `coilyco-gaming/sirens-echo#996`'s siblings `#201` and `#1031`. This is only about getting the asset URL for something that has already been found. ## The shape worth having Tenor and giphy are the same shape: a landing page a human browses, plus a direct media host whose URL returns the bytes. Imgur is a third of the same. So the useful unit is not a tenor-specific helper but **a small documented pattern for media hosts of that shape**, with the per-site specifics as data rather than code. Two things that will bite whoever builds it, both known: * **Egress.** The five hosts in the web-culture set were handed to DevOps as a fetch grant and never filed until today, now tracked at `coilyco-bridge/deploy#772`. A retrieval tool that cannot reach the host is indistinguishable from one that is broken, which is `coilyco-gaming/sirens-echo#1088` exactly. * **The direct media hosts differ from the landing host.** Tenor serves assets from `media1.tenor.com` and `c.tenor.com`, so an allowlist naming only `tenor.com` grants the page and not the thing. ## Related * `coilyco-gaming/sirens-echo#996` - the original, closed as moved * `coilyco-gaming/sirens-echo#1029` - the web-culture pack, whose reading half shipped * `coilyco-bridge/deploy#772` - the egress grant this depends on

coilyco-ops added the

labels

2026-08-22 22:15:16 +00:00

coilyco-ops referenced this issue from coilyco-gaming/sirens-echo

2026-08-22 22:15:24 +00:00

allow pulling actual gifs from tenor.com #996