Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Changes in the feeds RSS.chat generates

未关闭
#14 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
冷清
技术栈
javascript
领域
backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
JavaScript
星标
37
派生
7
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

scripting/rss.chat 的其他 Issue

查看 scripting/rss.chat 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。