Rob Fahrni blogs more thoughts on Dave Winer’s call for inbound RSS:

The problem is the platform folks tend to say “use our API.” Which makes sense, but most API’s are painful in some way because of authentication or some hoop you have to go through. If the platform natively supported inbound RSS it would greatly simplify the developer and user experience.

Micro.blog was designed around inbound RSS. We had that before we had blog hosting. It’s still a unique architecture that I haven’t seen any other platforms replicate.

Kuba Suder 🇵🇱🇺🇦

Maybe Dave would have more luck getting people to implement this if he explained what the hell he means by “inbound RSS”, because this is the first time I’m hearing this term…

Dave Winer

“Use our api” is no answer to people who have a blog that has outbound RSS. They aren’t programmers. Saying use our api is the same thing as saying get lost.

They would even have to say where the feed is, just let me use my blog to write stuff on Bluesky.

Think how great that would be.

Dave Winer

What the hell do I mean by “inbound RSS”?

It looks like the first time I used the term on my blog was in 2022, when I was thinking about using Substack to do email distribution of my blog. I asked if I could use RSS to feed my writing into Substack, instead of having to copy/paste it. They apparently didn’t read the question and they told me about how Substack supports RSS. It was at that point that I realized there needed to be a distinction between inbound and outbound RSS.

I guess I thought it was pretty straightforward. Feed readers view RSS as inbound, and blogging tools regard it as outbound. But sometimes you want a feed reader to generate RSS feeds (FeedLand does) and sometimes you want blogging software to handle inbound feeds, thus acting a bit like a feed reader. As Manton points out, micro.blog does this.

Now it makes total sense to me and I think it will make sense to everyone else pretty soon that twitter-like systems which are starting to support outbound RSS would also support inbound.

The reason this is a good thing as in the case of Substack, is that I can use the writing tools I like best to publish through Substack. In fact I wasn’t willing to do the copy/paste thing, I had tried it with Medium and I hated it. It turned me into a piece of software. I have spent a considerable portion of my career working on APIs that get software to take their input from anywhere, not just from their own often pretty shitty editors. And Substack doesn’t want you uisng someone else’s editor, because that’s where a good portion of their lock-in comes from. And I suspect we’ll encounter resistance to the idea from Bluesky because despite their hype about the wonders of AT Proto, they really want you living in their environment and not posting to it from outside, so they benefit by making it hard to do so, while as it has been pointed out, their APIs make it possible to do it anyway. It’s the friction and complexity and fragility that helps keep them from being replaced. If they realllly believed in the open web, they would jump at the opportunity to support inbound RSS.

If you have any questions, let me know I’ll probably put an edited version of this on my blog in a few minutes.

Dave Winer

A longer more detailed explanation on Inbound RSS. Hope it helps!

scripting.com/2025/04/1…

Rob Fahrni

@manton.org I touch on that in my piece. Basically when you publish RSS that’s outbound.

If you read it and do something with it, that’s inbound.

An inbound feed could be used to put test into your Bluesky, Twitter, or name your service account.

Your RSS feed is the source.

Rob Fahrni

I touch on that in my piece. Basically when you publish RSS that’s outbound.

If you read it and do something with it, that’s inbound.

An inbound feed could be used to put test into your Bluesky, Twitter, or name your service account.

Your RSS feed is the source.

Dave Winer

Rob I wanted to comment on your post. I thought it was very good. One little thing – the RSS feed would be your account, not be imported into your account. One of the nice things about AT Proto is that they have a componentized view of the pieces, so it doesn’t matter what’s behind it. Supporting inbound RSS could be a very simple thing. Not something I have time to work on unfortunately.

Manton Reece @manton
Lightbox Image