Two Microsub reader updates this week:

Feed type indicators — each feed now shows its type (RSS, Atom, JSON Feed, h-feed) as a badge, and subscribing to a feed that already exists in another channel returns a clear error instead of silently creating a duplicate. URL normalization catches trailing slash and http/https variants.

Mark source as read — the mark-as-read button is now a split button. The main action marks a single item, but a dropdown caret reveals “Mark {source name} as read” — which bulk-marks all items from that feed in one click. Cards animate out smoothly. Handy when a noisy feed floods a channel and you want to clear it without losing items from other sources.

Both features work in the channel view and the unified timeline view. https://github.com/rmdes/indiekit-endpoint-microsub

🔗 https://rmendes.net/notes/2026/03/11/2e639

GitHub - rmdes/indiekit-endpoint-microsub: Microsub endpoint for Indiekit

Microsub endpoint for Indiekit. Contribute to rmdes/indiekit-endpoint-microsub development by creating an account on GitHub.

GitHub

So... #PADD is getting "Notifications". If your microsub server has a `notifications` channel then PADD will automatically treat them as such!

I realized that part of the #Microsub spec calls for a notifications channel when I was adding a microsub server to my blog software. So naturally if my blog was going to publish it, I figured my reader should consume it naturally.

Seriously, I am having _so_ much fun building this stuff. (https://crowdersoup.com/blog/post/photo-1772504988/)

I think I never subscribed to as many RSS feeds from small blogs as I did recently since I got myself my own #microsub reader integrated into my blog engine powered by #indiekit

it’s just very comfortable to use, you read the blog post and you can reply, like or repost right from the integrated Reader view (inspired by Monocle)

it makes me read more and subscribe to more people’s blogs, which from my weekend exploration is a huge world to explore… there are so many interesting people writin...

@jonmsterling Feels like all of this already exist and is being put in practice, this is my #microsub endpoint reader which basically is able to consume any type of feeds (rss, atom, jsonfeed) and then I can directly read or like/repost/comment on it from my blog backend, powered by #indiekit

Yes I have used Claude to orchestrate the development of #indiekit from @paulrobertlloyd

I have made a few plugins and then the entire development of a #microsub endpoint for indiekit (6K line of code) based on the excellent #ekster wiki and inspired by https://github.com/pstuifzand/ekster

Deploy Your Own IndieWeb Site on Cloudron with Indiekit

Deploy Your Own IndieWeb Site on Cloudron with Indiekit 24 January 2026 indiekit indieweb cloudron self-hosting Own your content. Syndicate everywhere. This guide walks you through deploying a complet...

Ricardo Mendes
The team @micro.blog have done it again.

They soft-launched https://micro.one yesterday¹.

This may be the most accessible onramp to the open social web ever.

Cost: $1 a month. Yes you read correctly.

This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online².

Stop posting in someone else’s garage³.

Time to export your Twitter, and migrate your Mastodon handle to your own home on the web.

Of course you can bring your own domain name. Additionally:
* blog posts, naturally, both articles and microblogging notes
* photos
* podcasting
* custom themes
* web-clients and native mobile posting clients
* WordPress, Tumblr, Mastodon, Medium import
More details (and alternatives) at https://micro.one/about/pricing

And yes, it interoperates with the open #socialWeb, including:
* #ActivityPub support, #Mastodon and #fediverse compatibility
* #IndieAuth to sign-in to third-party apps
* #microformats support in all built-in themes
* #Webmention for sending and receiving replies across websites
* #Micropub standard posting API, supporting dozens of clients
* #Microsub standard timeline API, supporting social readers
More #indieweb support details at https://micro.one/about/indieweb

Did I mention the the superb micro.blog (and micro.one) Community Guidelines?
* https://help.micro.blog/t/community-guidelines/39

Well done @manton.org and team.

This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb

https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24
https://tantek.com/2025/012/t1/eight-years-webmention


Glossary

IndieAuth
  https://indieweb.org/IndieAuth
microformats
  https://microformats.org/wiki/microformats
Micropub
  https://indieweb.org/Micropub
Microsub
  https://indieweb.org/Microsub
Webmention
  https://indieweb.org/Webmention

References

¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html
² https://tantek.com/2025/001/t1/15-years-notes-my-site-first
³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
Micro.blog

Post short thoughts or long essays, share photos, all on your own blog. Micro.blog makes it easy, and provides a friendly community where you can share and engage with others.

@maffeis #ActivityPub is for federation whereas #micropub and #microsub are for interacting with your instance, so they are not really exclusive though.

Micropub is already supported by tools like micro.blog, @ia Writer and such.

Not sure if anyone has implemented it on top of an ActivityPub backend though.

#Webmention, #WebSub and #Microformats would be the more direct #IndieWeb “competitor” to ActivityPub, but eg @snarfed.org and @pfefferle are both showing that the two can be bridged

@maffeis I like how the #IndieWeb is approaching this with #MicroPub and #MicroSub:

* https://indieweb.org/Micropub
* https://indieweb.org/Microsub

Clients can chose to implement one or both of those.

A typical social media app would implement both.

An app that’s meant only for authoring posts picks just MicroPub and an app that’s simply meant for consumption picks just MicroSub.

I find the #Fediverse / #Mastodon focus on #ActivityPub as the one and only API to be a bit lackluster in that regard.

Micropub

Micropub is an open web standard (W3C Recommendation) and API for creating, editing, and deleting posts on websites, like on your own domain, supported by numerous third-party clients, CMSs, and social readers.

IndieWeb

@benpate @scottjenson Oh, but there is no need to _host_ your reply within your reader, you simply have to be able to _write_ your response within your reader.

Eg: I use @ivory as a client for my Mastodon account and it both reads and writes to that Mastodon account (using the Mastodon-specific API?)

With #indieweb it instead could do:

- Read the content using a standard protocol like #MicroSub: https://indieweb.org/Microsub
- Write any actions / replies using #MicroPub: https://indieweb.org/Micropub

Microsub

Microsub is a proposed standard for creating a new generation of social readers that decouples the management of subscriptions to feeds and the parsing/delivering content from the user interface and presentation of the content.

IndieWeb