Skip to content

Nostalgia loop (Hermes / Crusty)

Field Value
Status Active — personal daily loop live; multi-user PoC next
Type Hermes scheduled job on projects/crusty (dedicated machine)
Delivery Telegram only
Updated 2026-07-16

Description

Morning nostalgia pickup on Hermes / Crusty: one curated YouTube clip from the 1970s–early/mid-1980s, delivered in Telegram so Darcy can watch in the Telegram in-app browser (~5–7 minutes, no bounce out to YouTube, no ad interrupt in that flow).

Catalog mix (era-locked): TV show clips, pre-MTV music videos, musical performances from TV, commercials, movie trailers — and adjacent period media in the same window.

Interaction:

Action Detail
Scheduled ~6:30 AM daily (one pick)
On demand Ask Hermes via Telegram → generate another
Feedback Like / dislike on each send (steers future picks)

Early signal (personal): ~19–20 sends so far — liked nearly all (one lukewarm). Quality strong enough to keep running.

Why it matters

  • Proves a low-friction daily delight loop on the same Hermes stack as email digest / Aye Robot / Darwin robot / idea generation — not just ops or posting.
  • Telegram as watch surface (in-app browser) is part of the product feel, not just a notification channel.
  • Natural next experiment for multi-user Hermes conversations without building a separate app.

Hermes daily job context (Crusty machine)

Live automation on the dedicated laptop (high level — no private paths/keys in this wiki):

Job Role
Email summary Morning Gmail digest
Aye Robot (“iRobot”) Daily comic pipeline → Telegram → optional gated X
Darwin robot Daily use-case robot video lane (creative / Operator practice)
Idea generation Recurring brainstorm surface
Nostalgia loop This page — era media pickup → Telegram

Canonical agent page: projects/crusty.

Next — multi-user PoC

Goal: Quick proof that friends can talk to Hermes in their own Telegram conversations and receive nostalgia picks.

Plan (light):

  1. Issue separate conversation / chat identities to a couple of friends.
  2. They message Hermes directly (not Darcy’s personal thread).
  3. Same loop semantics: scheduled and/or on-demand era clip + like/dislike.
  4. Watch quality, trust boundary, and whether shared agent + isolated chats is enough before any productization.

Not yet: public launch, billing, or a standalone app. PoC only.

Counterpoint / risk

Risk Note
Taste drift Early likes may not hold; keep dislike path honest
YouTube / Telegram dependency Delivery assumes both stay usable in-app
Multi-user blast radius Friends on the same Hermes instance need clear chat isolation and no leak of Darcy’s other jobs
Scope creep PoC ≠ product — don’t build AaaS packaging until friends actually use it