← Back to all sparks
R

RSS-Bridge

INFRA · APIS
Velocity0.0

Generates RSS feeds for sites that do not provide one

The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.

rssweb-scrapingself-hostedphpcommunity-maintainedbot-protection
Current state
RSS-Bridge generates feeds for sites that removed theirs, and each release is a batch of community fixes to individual bridges plus a handful of new ones. Releases are date-tagged rather than versioned and land every few months, with the most recent in August 2025 — roughly a year of silence since. The core is stable PHP; the churn is in the ~400 site-specific scrapers that break whenever a target site changes markup or adds bot protection.
Where it's heading
The project has been shifting from a curated tool to a general-purpose scraping surface: bridges are now all enabled by default, caching was rewritten, and token-based URL auth was added to make public instances survivable. That combination points at operators running shared instances rather than individuals running one bridge. The maintenance load, however, is entirely community-carried, and the gap since the last release suggests that pipeline has thinned.
Prediction
The next release is likely another routine batch of bridge repairs and additions rather than a core change. The stated intentions in these notes — raising the minimum PHP version and separating the document root from the data folder — remain unshipped, and nothing here indicates when that lands.

Recent moves

  1. 0y ago

    Routine batch: new bridges plus bot-protection and parser repairs

    The most recent release and a clean sample of the steady state: two new bridges added, a bot-protection bypass for Idealo, and parser repairs for sites that changed layout. The mix of new coverage and decay repair is what every RSS-Bridge release looks like.

    View source ↗
  2. 1y ago

    Bridge repairs, subcategory support, default 1-day cache TTL

    Another routine batch, with one change that touches every install rather than one bridge: a default cache TTL of one day. The rest is the usual repair work, including a broken VK bridge semi-disabled rather than fixed.

    View source ↗
  3. 1y ago

    Re-tag release to correct the version shown in Configuration

    Issued three weeks after the previous release mainly to carry the correct version tag in the Configuration page — the notes describe the earlier omission as a visual bug. A few bridge fixes ride along.

    View source ↗
  4. 1y ago

    All bridges now enabled by default

    ⚡ SPARK

    The default flips from a curated handful of enabled bridges to everything on, which is the change that turns RSS-Bridge from a tool you configure into a service you expose. The token auth and cache work in surrounding releases only make sense read against this.

    View source ↗
  5. 2y ago

    URL token authentication and cache administration tooling

    Password-protection via a required URL token arrives here, along with tools for manually administering the configured cache. In hindsight this is the groundwork for the all-bridges-on default that followed — a public instance needs a door before you open every window.

    View source ↗
  6. 2y ago

    Caching system rewritten; all existing cache items expire

    A full rewrite of the caching layer that invalidates every existing cache item on upgrade. Invisible in normal use but the reason later releases could add per-cache config options and TTL defaults without further churn.

    View source ↗