You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There will be loose-ends like this. Until now there was relatively little interesting in the source namespace. That has changed, it's good, but it means we must review the feeds carefully. I have Claude do that every time there's a change, but Claude is not flawless, it misses things, I find. ;-)
We're still making big risky changes -- on Wednesday we completely redid the way we serve static files. There's at least one more coming.
Quick one, @scripting I follow your feeds in a secondary implementation and want to match your lead. After #14, threadwalker prints ? for authors (walker.js:49 still reads item-level source:account). Updating the walker to read the core <source>, or should item-level stay? I'll follow whichever.
@rmdes -- threadwalker is fixed on the repo. It now reads the core RSS <source> element on reply items -- that's the author attribution in the mixed feeds -- and for the single-author starting feed it takes the author from the channel, whose feed it is. Item-level source:account isn't coming back, so <source> is the one to follow.
Also fixed while in there: the walker's starting feed still pointed at the old users.rss.network address, and Node's bare https.get doesn't follow the redirect. It now points directly at https://rss.chat/users/manton/rss.xml.
@andrewshell -- when you start building, the docs are current: the API doc, and as of today a doc for the firehose with two working demo apps (Node and browser) in examples/firehose.
@rmdes -- threadwalker is fixed on the repo. It now reads the core RSS <source> element on reply items -- > > that's the author attribution in the mixed feeds -- and for the single-author starting feed it takes the author from the channel, whose feed it > is. Item-level source:account isn't coming back, so <source> is the one to follow.
my implementation dropped source:account and threadwalker work neat against my all user rss feed
will deploy the fix
Activity
andrewshell commentedon Jul 17, 2026
Sounds good to me. I haven't started implementing anything yet. I'm just trying to understand what's available and how it's being used.
rmdes commentedon Jul 17, 2026
Quick one, @scripting I follow your feeds in a secondary implementation and want to match your lead. After
#14, threadwalker prints?for authors (walker.js:49still reads item-level source:account). Updating the walker to read the core<source>, or should item-level stay? I'll follow whichever.scripting commentedon Jul 18, 2026
This is Claude, writing from Dave's account.
@rmdes -- threadwalker is fixed on the repo. It now reads the core RSS
<source>element on reply items -- that's the author attribution in the mixed feeds -- and for the single-author starting feed it takes the author from the channel, whose feed it is. Item-levelsource:accountisn't coming back, so<source>is the one to follow.Also fixed while in there: the walker's starting feed still pointed at the old users.rss.network address, and Node's bare https.get doesn't follow the redirect. It now points directly at https://rss.chat/users/manton/rss.xml.
@andrewshell -- when you start building, the docs are current: the API doc, and as of today a doc for the firehose with two working demo apps (Node and browser) in examples/firehose.
rmdes commentedon Jul 18, 2026
my implementation dropped
source:accountand threadwalker work neat against my all user rss feedwill deploy the fix