Pipe Dreams: The life and times of Yahoo Pipes

Original Article ↗ Hacker News Discussion ↗

Once a beloved web tool for visually wiring together RSS feeds, APIs, and scraped web pages, Yahoo Pipes is remembered as emblematic of a more open, interoperable “Web 2.0” era. Commenters share concrete ways they used it—from filtering podcasts and Craigslist listings to cross-domain scraping—and contrast its flexibility with today’s more locked-down, API-key-gated ecosystem, pointing to modern successors like Node-RED, n8n, Zapier, and others that still don’t fully recapture its spirit. The Retool retrospective on Pipes is widely praised for its research and design, though many readers report that its heavy, animated presentation performs poorly on current browsers and devices.

Personal uses and nostalgia

  • Many describe Yahoo Pipes as their first experience with automation: scraping sites, generating alerts, combining and filtering RSS feeds and podcasts, or randomizing roommate assignments.
  • Use cases included Craigslist game hunting, project-awareness dashboards aggregating Jira and GitHub, building CORS proxies, and filtering specific podcast episode types or YouTube content.
  • Several recall it as one of Yahoo’s best and most ahead‑of‑its‑time tools, regretting that leadership didn’t “SaaS-ify” it as AWS later did.

RSS, open web, and what was lost

  • Multiple commenters stress that RSS is still how they read the web and that it has become more important as Twitter unravels.
  • Pipes is seen as emblematic of a Web 2.0 era of open standards, mashups, and loose interoperability.
  • Many lament the shift to locked‑down APIs, aggressive monetization, and walled gardens that make Pipes-style mashups much harder today.

Modern successors and alternatives

  • A broad ecosystem of “business glue” and automation tools is mentioned: IFTTT, Zapier, Make/Integromat, n8n, Node‑RED, Pipedream, Val Town, windmill, Huginn, Activepieces, and others.
  • Some self-hostable or OSS options are highlighted; others are SaaS-only. Opinions differ on quality, openness, and buginess.
  • One person built a modest open-source “pipes” successor for RSS filtering and scraping, noting it can’t match Yahoo Pipes’ breadth.

APIs, business models, and feasibility

  • A recurring theme: many useful web services no longer expose parseable HTML or affordable public APIs (e.g., search), making generic blocks difficult.
  • Discussion of server costs, lack of micropayments, and the difficulty of running free/open services sustainably.
  • Some argue there is still untapped B2B and “power user” demand for Pipes-like tools despite not being universal.

Retool article design and performance

  • The Retool piece is praised for production quality, storytelling, and Easter eggs; some see it as a love letter rather than direct marketing.
  • At the same time, many report severe lag, scrolljacking, and unusability across devices (Android, iOS, macOS, Linux, even powerful desktops), while others say it runs smoothly.
  • Several wish for a plain-text or reader-friendly version and criticize heavy animations for a text-heavy story.