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

Watching the flow of ActivityPub posts via WordPress

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
wordpress
领域
backend, web-dev

调研方向

Start by reviewing the proposed wordpress.com changes.json feed and the six fields listed in the issue. Determine where this project could consume and present the feed, and clarify the desired display and polling behavior before coding. Done means the ActivityPub/WordPress activity is visible beyond the user's own posts and the result is useful for evaluating the connection.

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

描述

I want to see how people are using the connection between WordPress and ActivityPub.

Right now all I see are the posts I write.

Seeing what people are doing might give us ideas how to improve our respective products.

1999

We had a similar itch in 1999 when we wanted to see what the bloggers were writing. When a blog updated it would ping, we'd verify that they changed and if so, it would appear at the top of the list at weblogs.com.

Its output was a file called changes.xml, it had three bits of info for each update, the name, a url and timestamp.

There was a limit to 100 items in the file.

2025

wordpress.com maintains a changes.json file at a fixed location which we can poll.

there's a limit to the number of items in the file.

each item has:

  1. name of blog it came from
  2. title of the post if it has one
  3. when it was published
  4. url of the post via mastodon
  5. url of the post via wordpress
  6. url of rss feed for the site

that's where to start. let's see what we get to see where we go with this.

What will happen

We will of course share the info with the people who are using it. ;-)

Guess what we'll all start writing about -- how great it is and what doesn't work.

Giving a voice to the bloggers to help drive the direction of the tech.

I bet the users we're attracting now are pretty leading edge people.

主要语言
HTML
星标
134
派生
10
PR 合并指标
30 天内没有已合并 PR

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

scripting/Scripting-News 的其他 Issue

查看 scripting/Scripting-News 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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