Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Changes in the feeds RSS.chat generates

Open
#14 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript
Domain
backend

Research direction

The issue names no files, tests, or implementation entry points. Start by comparing the example feeds at rss.chat/users/rss.xml and rss.chat/users/dave/rss.xml with the source:account behavior described here and in issue #9; done would require an explicit, testable follow-up task, which this report does not define.

Written by the indexing model from the issue text.

Description

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.

Dominant language
JavaScript
Stars
37
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/rss.chat

All issues in scripting/rss.chat

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.