This fundamentally alters the blog experience from monotemporality to multitemporal. If RSS was like single-channel appointment tv (“new episodes of ribbonfarm drop on thursdays around 5pm” was my standard for years) to something like streaming TV.
Conversation
I would *love* it if blogchain writing got popular enough that it would be worthwhile for someone to reinvent RSS along these lines. In stead of being subscribed yo a bunch of channels on a push clock, you’re subscribed to a bunch of shows (blogchains) on a pull clock.
1
2
6
This is unfortunately a 2-sided market problem with chicken-egg dynamics. I could probably fund someone to write a wordpress plugin to do the destination server side (you see custom page when you land on a blog) but this is more naturally a client side problem.
1
1
Done server side, cookie-based management is janky (expiration timing and cross-device persistence mess) and more stable stateful user accounts for all readers is a nightmare for both publishers and readers (and both are GDPR nightmares; I don’t want to manage users)
2
Client side is far cleaner. Not email. Email is push. Not RSS. That’s also push. Though both have queuing of unreads, it is not quite what you want. You want it factored by “show” and pick up where you left off. Need new streaming style UX. Not unread-buffer style.
2
3
Replying to
RSS is pull, actually. And I think “per-show” RSS feeds get you 90% of the way to where you’re going.
1
1
Replying to
The UI is push though as in when you open up the reader it autofetches all new stuff. You don’t have to take an action like visiting the site or pushing an update button. Like email that way. Inbox UI
1
Replying to
OK, I guess I’m confused then. Either “when you open up the reader” counts as “taking an action”, OR *everything* is “push”, including streaming TV. But I think your definition of push might depend on whether you’re the type who leaves their email client open all the time.
1
Replying to
I am probably guilty of mixing up technical backend notions of push/pull andsofter UX notions, so hope idea is clear even if terminology is off
1
Not to me.
What problem do you see a user having under a feed-per-chain system?
1
I don’t know how to produce a feed per chain except to make it a category and inking the category feed, which still limits to rss subscribers


