Skip to content

Changes in the feeds RSS.chat generates #14

Open

Description

@scripting

We got an inquiry yesterday about the source:account element, which the spec says is channel-level, we were using it in items.

So we've changed how this works.

  1. The <source> element is in items in the everyone feed and in comments feeds.
  2. The <source:account> element appears only at the channel level in personal feeds.

Examples

https://rss.chat/users/rss.xml

https://rss.chat/users/dave/rss.xml

Caveat and self-kudos

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.

Activity

  1. andrewshell commented on Jul 17, 2026

    @andrewshell

    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.

  2. rmdes commented on Jul 17, 2026

    @rmdes

    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.

  3. scripting commented on Jul 18, 2026

    @scripting
    OwnerAuthor

    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-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.

  4. rmdes commented on Jul 18, 2026

    @rmdes

    @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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions