Summary

A website asked; the browser answered

A feed is an invitation issued by a publisher's website: here is an address where fresh entries will appear. It is not a command to a browser. The browser decides whether to notice it, explain it, or make it useful. In 2004 Firefox made that small publisher signal unusually powerful. A page could put an RSS alternate link in its head. The Live Bookmarks design discussion proposed that Firefox detect it, show a browser-level cue, and offer an Add Bookmark action. Accepting the invitation created a special folder. Its children represented items from the feed rather than a fixed list of URLs someone had filed once.

That crossed an important boundary. A small website did not need a separate distribution agreement to appear in a reader's daily routine. It could publish a feed address; Firefox supplied discovery and an update-shaped place in the browser. The publisher controlled the entries. The browser controlled the shelf on which a reader would see them. The original design record is careful about the feature's scope: the proposed folder was not a promise of alerts on a schedule. Its simpler trick was to make new material appear where saved destinations usually sat still.

The Firefox 1.0 launch announcement of 9 November 2004 sold that trick plainly. Live Bookmarks let people glance at the latest news and blog headlines. In the era of tabbed browsing and competing homepages, that was a distinctive account of what a browser could be. It could be a reader of the distributed web, not just a window that opened a page after someone already knew its address.

The export kept addresses, not the habit

Fourteen years later Mozilla drew a different product boundary. The 2018 removal issue grouped feed discovery, preview and Live Bookmarks as built-in work to remove. Mozilla staff pointed to maintenance and security cost and judged the use too small to sustain that work. That was a product decision by the browser maker. It was not a measurement of how many people valued any given feed, and it could not erase the feed files on publishers' sites.

The migration plan says exactly what changed for an existing subscriber. Firefox would export the details of Live Bookmarks to an OPML file on the desktop, a format other feed readers could import. It would replace a Live Bookmark with a normal bookmark pointing to the associated site URL where that URL existed, and open an explanation page. Mozilla's support instructions spell out the edge case: without an associated site URL, there was no ordinary bookmark to leave in its place. The export carried feed addresses; the ordinary bookmark carried a destination. Neither made headlines keep appearing as children of a living folder.

The Firefox 64 release notes put a date on the switch: 11 December 2018. They said RSS feed preview and Live Bookmarks were available only through add-ons. This was a withdrawal of native integration, not a decree against feeds. A publisher could still offer RSS or Atom. A reader could still choose another reader or an extension. What disappeared was the default browser path from a site's declaration to a recognizable subscription action and a place to encounter new entries.

That distinction matters to internet history. A format can remain open and technically reachable while a widely distributed client stops giving it a prominent handle. The publisher still owns the feed; the reader may still want it; the browser no longer spends its interface and maintenance budget connecting the two. The modest OPML file is both useful and revealing. It protects a list of addresses at the moment the browser retires the experience that made those addresses feel alive.