to the @standard.site folks, adding a field to `site.standard.publication` which declares where the RSS feed is would help in constructing subscription OPMLs or /blogroll pages indieweb.org/blogroll

I made a reader for standard.site called "Standard Reader" Partially inspired by Google Reader (or what i remember of it) it provides a place to browse, discover, read and subscribe to standard site publications Also has some cool features like article dictation (I like to listen to longform)

Who at beehiiv decided that sending RSS *at all* was a paid feature They seem to be growing more popular, but it's still feeling like they're blowing it on the open web stuff that so many other tools are moving towards

@jaredlemler.com is putting together a blog about RSS & AT Protocol. How we are incorporating both to transition the current state of podcast distribution!!

okay who's building standard.reader? I want to replace rss and wallabag - follow my subscriptions, rss or standardsite - save a to-read list (also for any article type, readability.js-ified) - annotate via margin records - save / connect with semble - share with skyreader - works offline

The confusion about standard.site is that there are two distinct and different users. Those that use it as a database schema and those that use it as a new syndication format (like a Wordpress blog with a plugin). But HTML and RSS are views, whereas JSON doubles as both a storage schema and a view

Standard.site in Micro.blog: manton.org/2026/05/30/standardsite-in-mi…

I wrote this yesterday about how I want to hook RSS up to standard.site. I'd love to see my posts on their feed reader, and vice versa. scripting.com/2026/08/02.html

I've been absolutely swamped lately, but thanks to the atproto community, @sequoia.pub hasn't slowed down! Here's a quick rundown: A <sequoia-subscribe> web component that lets readers create a site.standard.graph.subscription record for your publication. Huge thanks to @heaths.dev for this!