Wednesday, September 16, 2026  🔗 **Source:** [Wednesday, September 16, 2026](http://scripting.com/2026/09/16.html#a135924) > [!note]+ Document Notes > --- > tags: [feedland, rss-syndication, wordpress-plugins, open-web, news-rivers, indieweb] > author: Dave Winer (published under the Scripting News byline) > source: Scripting News — scripting.com > reference: http://scripting.com/2026/09/16.html#a135924 > date created: 2026-09-19 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > ## 🏷️ Title > **Wednesday, September 16, 2026** — Scripting News daily post. Working subtitle for filing purposes: *FeedLand rivers land inside WordPress via Scott Hanson's River Embed plugin.* > This is a dated daily roll-up, not a titled essay. The capture contains one substantive entry (the FeedLand/WordPress plugin announcement), the site's standing copyright and last-update lines, the standing nightly-email pitch that sits at the foot of every Scripting News page, and one orphaned linkblog fragment ("Don't make me laugh.") that arrived without its link. > ## 🧭 Table of Contents > - 🏷️ Title > - 🧭 Table of Contents > - 🔗 References (in-page) > - 📝 Summary > - 📖 Main Content → 🗒️ Notes > - 📚 References > - 🗣️ Paraphrase > - 📰 Newsletter > - ✅ Action Items > - 🧪 Hypotheses > - 📊 Methodology > - ❓ Questions > - 🔮 Future Research > - 💡 Implications > - 🧠 Learning Styles Assessment > - 📊 Accessibility Assessment > - 🌍 DEIB Assessment > - ✅ Logical Validity > - 🛡️ DARVO Analysis > - 🎯 Conclusion > - 🔄 Refactor Appendix > ## 🔗 References (in-page) > The post is link-dense in the way Scripting News usually is: four outbound links inside a short body, and the links carry most of the actionable payload. This source is **not** uncited. > | Anchor text (verbatim) | Destination | Kind | Why it matters | > |---|---|---|---| > | River Embed for FeedLand | https://wordpress.org/plugins/river-embed-for-feedland/ | WordPress.org plugin directory listing | The artifact itself. Authored by Scott Hanson, distributed through the official plugin repository, which means GPL-compatible licensing, the plugin review queue, and one-click install from any wp-admin. | > | thread | https://github.com/scripting/feedlandSupport/issues/251 | GitHub issue in the FeedLand support repo | The designated Q&A venue. Support is being routed to a public issue tracker rather than a forum or a mailing list. | > | # (permalink glyph) | http://scripting.com/2026/09/16.html#a135924 | Permalink to this individual entry | Confirms the post-per-day, anchor-per-entry structure of the blog; the anchor ID is timestamp-derived. | > | sign up for the nightly email | http://scripting.com/email/ | Newsletter subscription page | Standing site furniture, not part of the day's news. Included here for completeness. | > Two named third parties appear without links: **CNN** and **TechCrunch**, both cited as examples of news organizations running WordPress. **Scott Hanson** is named as the plugin author, and **feedland.com** / **feedland.org** are named as hosted instances alongside the self-hosting option. > ## 📝 Summary > **What happened.** Dave Winer announced that FeedLand — his feed-reading and feed-organizing service — now has a WordPress integration path. Scott Hanson has published a plugin, River Embed for FeedLand, to the WordPress.org plugin directory. The workflow Winer describes is three steps: build a timeline in FeedLand, decide it is ready for public consumption, then use the plugin to surface that river of news as a page inside a WordPress site. He explicitly notes that the FeedLand backend can be the hosted feedland.com, the hosted feedland.org, or an instance you run yourself. Questions go to a GitHub issue thread. > **Why it matters.** This is a small piece of plumbing with a disproportionate reach, because of the denominator on the WordPress side. Winer's own framing — that CNN and TechCrunch both run WordPress and could therefore carry a stream of news from related publications — is the argument in miniature: the integration does not ask publishers to adopt a new platform, it meets them where roughly two-fifths of the web already lives. For the open-web/syndication crowd, it is a distribution story. RSS has never had a discovery problem so much as a placement problem; a river that renders inside a site people already visit is placement. It also nudges the "river of news" pattern — reverse-chronological, unread-count-free, no-algorithm feed reading, which Winer has advocated for roughly two decades — from a reader-side habit into a publisher-side feature. > **Stakeholders.** > - *Publishers on WordPress* (news orgs, product sites, the "political leader site" Winer names) — get a low-effort curated news module without building one. > - *FeedLand users* — gain an output surface for timelines they were already curating. > - *Scott Hanson* — the plugin author, now carrying the maintenance and support surface that comes with a directory listing. > - *The WordPress plugin ecosystem* — another entry in the small but persistent category of feed/syndication plugins. > - *Publications being aggregated* — they gain referral traffic they did not negotiate for, and lose control over the context their headlines appear in. > - *Readers* — get more cross-publication context on a page, or more clutter, depending on execution. > **Risks.** > - **Single-maintainer dependency.** A plugin with one author, embedding a service with essentially one author, is two bus-factor-of-one links in a chain. Winer's own back catalogue is full of services that have come and gone. > - **Remote-content coupling.** Embedding a river means a WordPress page's content depends on an external service's uptime, rate limits, and CORS/embed policy. Winer does not say whether the embed is server-side fetched, iframed, or client-side JavaScript — and that distinction determines caching, SEO, privacy, and accessibility behavior. > - **Performance.** A page of externally-fetched news items is exactly the kind of feature that quietly costs a site its Core Web Vitals if it renders client-side and unbounded. > - **Editorial and legal.** Automatically republishing headlines and excerpts from "related pubs" is fine until it is not; the aggregating site inherits a moderation surface it did not staff. > - **Accessibility.** An embedded third-party river is an accessibility liability the host site cannot easily fix — if the markup is wrong, the host publisher owns the complaint but not the code. > **Bottom line.** A genuinely useful bridge between two open-web ecosystems that mostly ignore each other, announced with characteristic brevity. The idea is stronger than the 150 words given to it, and the interesting questions — how the embed actually renders, who maintains it, what it costs a page — are all left to the linked GitHub thread. > ## 📖 Main Content > The capture is a single day's page from Scripting News. Structurally it breaks into four parts, only the first of which is news. > **1. The FeedLand × WordPress entry.** Winer opens with a one-line lede — the two systems "have a new hookup" — then immediately credits Scott Hanson and links the plugin by name. He states the deployment flexibility up front: feedland.com, feedland.org, or self-hosted, all work as the backend. The mechanism is then given as a compressed three-beat recipe: create a timeline, decide when it is ready, use the plugin to show it. He offers two use-case classes. The first is news organizations, where he names CNN and TechCrunch specifically and observes that both already run WordPress — the point being that the addressable market is already installed. The second is broader: "a product site, or a political leader site," receiving news from publications covering their area. He closes with the framing sentence that does the conceptual work — this is about bringing the feed world into the world of news — and points readers to a GitHub issue for questions. > **2. Site chrome.** A copyright line (1994–2026, Dave Winer — the 1994 start date is itself a quiet flex about longevity on the open web) and a last-updated timestamp of 10:31 AM EDT. > **3. The standing newsletter pitch.** A long-running footer that opens by contrasting Scripti FeedLand and WordPress have a new hookup. With Scott Hanson's plugin: [River Embed for FeedLand](https://wordpress.org/plugins/river-embed-for-feedland/) you can use feedland.com or feedland.org, or host your own FeedLand, to include a page of news in your site. How it works: Create a timeline, when you're ready show the river to your readers of your WordPress site, use the new plugin. For a news orgs like CNN and TechCrunch, both use WordPress, they could have a stream of news from related pubs. For a product site, or a political leader site, news from pubs that cover the area. It's a way of bringing the feed world into the world of news. Here's a [thread](https://github.com/scripting/feedlandSupport/issues/251) where you can ask questions. [#](http://scripting.com/2026/09/16.html#a135924) © copyright 1994-2026 Dave Winer. Last update: Wednesday September 16, 2026; 10:31 AM EDT. You know those obnoxious sites that pop up dialogs when they think you're about to leave, asking you to subscribe to their email newsletter? Well that won't do for Scripting News readers who are a discerning lot, very loyal, but that wouldn't last long if I did rude stuff like that. So here I am at the bottom of the page *quietly* encouraging you to [sign up for the nightly email](http://scripting.com/email/). It's got everything from the previous day on Scripting, plus the contents of the linkblog and who knows what else we'll get in there. People really love it. I wish I had done it sooner. And every email has an unsub link so if you want to get out, you can, easily -- no questions asked, and no follow-ups. Go ahead and do it, you won't be sorry! :-) Don't make me laugh., Wednesday, September 16, 2026, Scripting News, 01m2p4vdw3y7dfnmnwx37x2hpn.