Refine OpenClaw payloads and reorganize docs
This commit is contained in:
zhuyongxin
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:4139f277b8cb621b02b3398f8a7bd78e3f9eef7bcd320b70b8590e802540c6ca",
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"published_at": "2026-03-21T10:19:11Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被证实套壳中国Kimi K2.5模型，引发侵权争议。Kimi官方确认Cursor通过Fireworks AI获得授权，不存在侵权。作者分析Cursor隐瞒事实是为了支撑其不断膨胀的估值，将其包装成大模型公司。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际调用的是Kimi K2.5模型。",
|
||||
"Kimi官方确认Cursor通过Fireworks AI获得授权，因此不构成侵权。",
|
||||
"Cursor隐瞒使用Kimi模型，被认为是为了支撑其高达500亿美元的估值。",
|
||||
"事件显示中国大模型技术已具备输出能力，国产模型与国外旗舰差距缩小。",
|
||||
"Composer 2性能低于GPT-5.4但成本最低，生成速度较快。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"套壳模型",
|
||||
"模型授权",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术争议",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入剖析了AI行业的热点事件，涉及技术真相、商业动机和行业趋势，具有较高的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:a16942c9699333155498d2bc59c530358bd6d81d9afe01e2b96e0e862edfc6a6",
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"published_at": "2026-03-19T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何招聘和面试程序员。作者认为考察重点应从代码能力转向AI使用、架构理解和需求转化能力。文章指出传统面试方法面临挑战，并引发了对未来程序员核心技能的思考。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的重点可能从代码能力转向AI工具的使用熟练度。",
|
||||
"面试问题需要考察将复杂需求转化为清晰提示词的能力。",
|
||||
"AI编程时代，对系统架构知识和项目分解能力的要求依然重要。",
|
||||
"传统的编程语法细节考察在AI辅助下意义可能减弱。",
|
||||
"文章引发了关于AI如何颠覆软件开发及人才评估标准的讨论。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"Skill",
|
||||
"MCP",
|
||||
"多Agent协同",
|
||||
"系统架构"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"技术趋势",
|
||||
"人才评估"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入探讨了AI时代程序员招聘的前瞻性问题，具有启发性和讨论价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:0d315d9489010cfd470a8d479e4e4443722fffdc34ecc1245c1b92458ace5093",
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"published_at": "2026-03-12T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本文以 Cloudflare 工程师用 AI 在一周内复刻 Next.js 框架为例，指出 AI 使得代码的护城河不复存在。作者认为，软件公司未来将依赖保密的测试用例来防止 AI 复刻，测试成为新的竞争壁垒。",
|
||||
"highlights": [
|
||||
"Cloudflare 工程师仅用一周时间和 1100 美元 Token 费用，通过 AI 成功复刻了 Next.js 框架，性能优于原版。",
|
||||
"AI 能够复刻软件的关键在于开源项目提供了完备的文档、社区文章和测试用例，使得 API 兼容性得以验证。",
|
||||
"为防止 AI 复刻，大型软件项目可能选择将核心测试用例闭源，如 SQLite 的 TH3 测试套件和 tldraw 的计划。",
|
||||
"AI 复刻软件引发了版权争议，例如 chardet 项目的许可证更改，且美国法律认定 AI 生成物无版权，冲击现有许可证体系。",
|
||||
"文章还讨论了 AI 对软件行业的多方面影响，包括提高效率、替代岗位以及可能引发的社会复杂性崩溃问题。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI 复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT 许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源协议",
|
||||
"技术趋势",
|
||||
"行业影响"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入探讨了 AI 对软件行业护城河的颠覆性影响，并提出了测试用例作为新壁垒的见解，具有前瞻性和讨论价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Article may be behind a paywall.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 95
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:419828361de854cd29dbcd3e8205d3da50ff955ac9c85861d2e195bc888b2103",
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"published_at": "2026-01-25T18:20:16Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能、性能改进和多项错误修复。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的回归问题。",
|
||||
"新增了注册关闭时的可自定义消息功能。",
|
||||
"在 Apache 访问日志和 Docker 日志中添加了用户名记录。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了包括用户查询扩展、标签搜索、令牌访问在内的多项错误。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug fixing",
|
||||
"regression",
|
||||
"Apache logs",
|
||||
"GReader API",
|
||||
"Ajax",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "提供了 FreshRSS 特定版本更新的详细变更信息，对用户和开发者有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:6b36071bbd22c58692c039e172669ae28ac1ec8a6a6bce150c22d80af29761fc",
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"published_at": "2025-12-24T19:27:23Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了按用户修改日期排序、高级搜索表单等新功能，并改进了性能和安全性。此版本还包含多项错误修复，并更新了Docker默认镜像。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，并支持对应的搜索操作符。",
|
||||
"引入了新的高级搜索表单和文章长度排序选项。",
|
||||
"改进了用户统计的扩展性，以支持拥有1000名以上用户的实例。",
|
||||
"修复了OpenID Connect在Debian 13上的兼容性问题。",
|
||||
"Docker默认镜像已更新至Debian 13 Trixie和PHP 8.4.11。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Docker",
|
||||
"Debian 13",
|
||||
"PHP 8.4",
|
||||
"OpenID Connect",
|
||||
"性能优化"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统部署"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "该文章详细记录了FreshRSS一个重要版本的功能更新、性能改进和错误修复，对用户和开发者具有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
@@ -0,0 +1,222 @@
|
||||
{
|
||||
"run_id": "openclaw-delivery-20260325-102553",
|
||||
"date": "2026-03-25",
|
||||
"candidates": [
|
||||
{
|
||||
"candidate_id": "cand:sha256:0d315d9489010cfd470a8d479e4e4443722fffdc34ecc1245c1b92458ace5093",
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"published_at": "2026-03-12T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本文以 Cloudflare 工程师用 AI 在一周内复刻 Next.js 框架为例，指出 AI 使得代码的护城河不复存在。作者认为，软件公司未来将依赖保密的测试用例来防止 AI 复刻，测试成为新的竞争壁垒。",
|
||||
"highlights": [
|
||||
"Cloudflare 工程师仅用一周时间和 1100 美元 Token 费用，通过 AI 成功复刻了 Next.js 框架，性能优于原版。",
|
||||
"AI 能够复刻软件的关键在于开源项目提供了完备的文档、社区文章和测试用例，使得 API 兼容性得以验证。",
|
||||
"为防止 AI 复刻，大型软件项目可能选择将核心测试用例闭源，如 SQLite 的 TH3 测试套件和 tldraw 的计划。",
|
||||
"AI 复刻软件引发了版权争议，例如 chardet 项目的许可证更改，且美国法律认定 AI 生成物无版权，冲击现有许可证体系。",
|
||||
"文章还讨论了 AI 对软件行业的多方面影响，包括提高效率、替代岗位以及可能引发的社会复杂性崩溃问题。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI 复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT 许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源协议",
|
||||
"技术趋势",
|
||||
"行业影响"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入探讨了 AI 对软件行业护城河的颠覆性影响，并提出了测试用例作为新壁垒的见解，具有前瞻性和讨论价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Article may be behind a paywall.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 95
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:4139f277b8cb621b02b3398f8a7bd78e3f9eef7bcd320b70b8590e802540c6ca",
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"published_at": "2026-03-21T10:19:11Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被证实套壳中国Kimi K2.5模型，引发侵权争议。Kimi官方确认Cursor通过Fireworks AI获得授权，不存在侵权。作者分析Cursor隐瞒事实是为了支撑其不断膨胀的估值，将其包装成大模型公司。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际调用的是Kimi K2.5模型。",
|
||||
"Kimi官方确认Cursor通过Fireworks AI获得授权，因此不构成侵权。",
|
||||
"Cursor隐瞒使用Kimi模型，被认为是为了支撑其高达500亿美元的估值。",
|
||||
"事件显示中国大模型技术已具备输出能力，国产模型与国外旗舰差距缩小。",
|
||||
"Composer 2性能低于GPT-5.4但成本最低，生成速度较快。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"套壳模型",
|
||||
"模型授权",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术争议",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入剖析了AI行业的热点事件，涉及技术真相、商业动机和行业趋势，具有较高的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:a16942c9699333155498d2bc59c530358bd6d81d9afe01e2b96e0e862edfc6a6",
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"published_at": "2026-03-19T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何招聘和面试程序员。作者认为考察重点应从代码能力转向AI使用、架构理解和需求转化能力。文章指出传统面试方法面临挑战，并引发了对未来程序员核心技能的思考。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的重点可能从代码能力转向AI工具的使用熟练度。",
|
||||
"面试问题需要考察将复杂需求转化为清晰提示词的能力。",
|
||||
"AI编程时代，对系统架构知识和项目分解能力的要求依然重要。",
|
||||
"传统的编程语法细节考察在AI辅助下意义可能减弱。",
|
||||
"文章引发了关于AI如何颠覆软件开发及人才评估标准的讨论。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"Skill",
|
||||
"MCP",
|
||||
"多Agent协同",
|
||||
"系统架构"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"技术趋势",
|
||||
"人才评估"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入探讨了AI时代程序员招聘的前瞻性问题，具有启发性和讨论价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:419828361de854cd29dbcd3e8205d3da50ff955ac9c85861d2e195bc888b2103",
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"published_at": "2026-01-25T18:20:16Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能、性能改进和多项错误修复。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的回归问题。",
|
||||
"新增了注册关闭时的可自定义消息功能。",
|
||||
"在 Apache 访问日志和 Docker 日志中添加了用户名记录。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了包括用户查询扩展、标签搜索、令牌访问在内的多项错误。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug fixing",
|
||||
"regression",
|
||||
"Apache logs",
|
||||
"GReader API",
|
||||
"Ajax",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "提供了 FreshRSS 特定版本更新的详细变更信息，对用户和开发者有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:6b36071bbd22c58692c039e172669ae28ac1ec8a6a6bce150c22d80af29761fc",
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"published_at": "2025-12-24T19:27:23Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了按用户修改日期排序、高级搜索表单等新功能，并改进了性能和安全性。此版本还包含多项错误修复，并更新了Docker默认镜像。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，并支持对应的搜索操作符。",
|
||||
"引入了新的高级搜索表单和文章长度排序选项。",
|
||||
"改进了用户统计的扩展性，以支持拥有1000名以上用户的实例。",
|
||||
"修复了OpenID Connect在Debian 13上的兼容性问题。",
|
||||
"Docker默认镜像已更新至Debian 13 Trixie和PHP 8.4.11。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Docker",
|
||||
"Debian 13",
|
||||
"PHP 8.4",
|
||||
"OpenID Connect",
|
||||
"性能优化"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统部署"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "该文章详细记录了FreshRSS一个重要版本的功能更新、性能改进和错误修复，对用户和开发者具有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
],
|
||||
"stats": {
|
||||
"total": 5,
|
||||
"keep_total": 0,
|
||||
"review_total": 5,
|
||||
"drop_total": 0
|
||||
}
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"success": true,
|
||||
"article": {
|
||||
"extract_id": "sha256:169f2b50eec3d198df126a8daedb95c48cff252ead9d4d2598a449e128cae2b8",
|
||||
"item_id": "sha256:419828361de854cd29dbcd3e8205d3da50ff955ac9c85861d2e195bc888b2103",
|
||||
"source_id": "freshrss:2987af960359c5c0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"author": "Alkarex",
|
||||
"published_at": "2026-01-25T18:20:16Z",
|
||||
"language": null,
|
||||
"content_kind": "article",
|
||||
"plain_text": "Alkarex\nreleased this\n25 Jan 18:20\n·\n78 commits\nto edge\nsince this release\nImmutable\nrelease. Only release title and notes can be modified.\nThis is a release focussing on bug fixing, in particular regressions from the release 1.28.0.\nSelected new features ✨:\n- New customisable message for closed registrations\n- Add username in Apache access logs (also in Docker logs): for GReader API, and for HTTP Basic Auth from reverse proxy\nImproved performance 🏎️:\n- Disable counting articles in user labels for Ajax requests (unused)\nMany bug fixes 🐛\nThis release has been made by @Alkarex, @Frenzie, @Inverle and newcomers @ciro-mota, @eveiscoull, @hackerman70000, @Hufschmidt, @johan456789, @martgnz, @mmeier86, @netsho, @neuhaus, @RobLoach, @rupakbajgain.\nFull changelog:\n- Features\n- Bug fixing\n- Fix unwanted expansion of user queries (saved searches) applied to filters #8395\n- Fix encoding of filter actions for labels #8368\n- Fix searching of tags #8425\n- Fix refreshing feeds with token while anonymous refresh is disabled #8371\n- Fix RSS and OPML access by token #8434\n- Fix MySQL/MariaDB\ntransliterator_transliterate\nfallback (when thephp-intl\nextension is unavailable) #8427 - Fix regression with MySQL/MariaDB index hint #8460\n- Auto-add\nlastUserModified\ndatabase column also during mark-as-read action #8346 - Do not include hidden feeds when counting unread articles in categories #8357\n- Remove wrong PHP deprecation of OPML export action #8399\n- Fix shortcut for next unread article #8466\n- Fix custom\nsession.cookie-lifetime\n#8446 - Fix feed validator button when changing the feed URL #8436\n- Performance\n- Disable counting articles in user labels for Ajax requests (unused) #8352\n- Security\n- Deployment\n- Add username in Apache access logs (also in Docker logs): for GReader API, and for HTTP Basic Auth from reverse proxy #8392\n- SimplePie\n- Update of\nCURLOPT_ACCEPT_ENCODING\n#8376, simplepie#960, simplepie#962 - Fix don’t preserve children inside disallowed\n<template>\nelement #8443 - Fixes before PHPStan 2 #8445, simplepie#957\n- Update of\n- Extensions\n- Update\n.gitignore\nto ignore installed extensions #8372\n- Update\n- UI\n- I18n\n- Misc.",
|
||||
"quality_flags": {
|
||||
"is_paywalled": false,
|
||||
"is_truncated": false,
|
||||
"is_low_content": false
|
||||
},
|
||||
"metadata": {
|
||||
"content_source": "fetched_html",
|
||||
"extractor": "trafilatura",
|
||||
"char_count": 2155
|
||||
},
|
||||
"pipeline_state": "extracted"
|
||||
},
|
||||
"error": null,
|
||||
"debug": {
|
||||
"content_source": "fetched_html",
|
||||
"extractor": "trafilatura"
|
||||
},
|
||||
"warnings": []
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,40 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-paywalled-content",
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Article may be behind a paywall.",
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"paywall",
|
||||
"quality",
|
||||
"summary"
|
||||
],
|
||||
"priority": 95,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-paywalled-content",
|
||||
"decision": "review",
|
||||
"reason": "Article may be behind a paywall.",
|
||||
"labels": [
|
||||
"quality",
|
||||
"paywall"
|
||||
],
|
||||
"priority": 95
|
||||
},
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
+130
File diff suppressed because one or more lines are too long
+42
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:4139f277b8cb621b02b3398f8a7bd78e3f9eef7bcd320b70b8590e802540c6ca",
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"published_at": "2026-03-21T10:19:11Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被揭露实为套壳中国模型Kimi K2.5。尽管Cursor通过合作伙伴获得授权未侵权，但其隐瞒行为被认为是为支撑高估值而包装成自研模型公司。事件引发对国产大模型技术输出和信心的讨论。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际请求的模型ID为Kimi K2.5。",
|
||||
"Cursor通过Fireworks AI获得Kimi授权，未违反许可条款，但刻意隐瞒使用事实。",
|
||||
"Cursor估值在短期内从数千万美元飙升至数百亿美元，有动机包装自研能力以支撑估值。",
|
||||
"事件显示中国大模型技术已能对外输出，国产模型与国外旗舰差距正在缩小。",
|
||||
"Kimi在此事件中获得大量曝光，其下一代K3模型被期待有显著性能提升。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"模型套壳",
|
||||
"MIT许可证",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术授权",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入剖析了AI行业热点事件，涉及技术真相、商业动机和产业趋势，具有较高的讨论和参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
+130
File diff suppressed because one or more lines are too long
+42
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:a16942c9699333155498d2bc59c530358bd6d81d9afe01e2b96e0e862edfc6a6",
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"published_at": "2026-03-19T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何有效招聘程序员。作者认为传统的代码能力考察将不再重要，面试重点应转向考察应聘者使用AI工具、分解项目需求以及系统架构的能力。文章也指出，目前尚难确定一套能可靠筛选合格AI编程人才的面试问题。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的核心考察点将从手写代码能力转向熟练运用AI工具的能力。",
|
||||
"面试问题可能包括如何将复杂需求转化为清晰的提示词，以及设计多Agent协同工作机制。",
|
||||
"传统的编程语法细节考察意义下降，系统架构知识和项目经验可能仍是重要参考。",
|
||||
"AI的快速发展使得软件开发流程和人才评估标准面临颠覆性变化。",
|
||||
"文章还包含科技动态、工具推荐、资源分享等周刊常规栏目内容。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"多Agent协同",
|
||||
"系统架构",
|
||||
"科技动态",
|
||||
"工具推荐"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"科技资讯",
|
||||
"效率工具"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入探讨了AI时代对程序员职业及招聘流程的潜在影响，具有前瞻性和讨论价值，且内容结构完整、信息量丰富。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
+144
File diff suppressed because one or more lines are too long
+42
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:0d315d9489010cfd470a8d479e4e4443722fffdc34ecc1245c1b92458ace5093",
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"published_at": "2026-03-12T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本期讨论了AI快速复刻大型软件的现象，以Cloudflare工程师一周内用AI重写Next.js为例。文章指出，完备的测试用例成为软件公司防止AI复刻的新护城河，并探讨了AI复刻带来的版权问题。",
|
||||
"highlights": [
|
||||
"Cloudflare工程师仅用一周和1100美元Token费用，通过AI复刻了Next.js，性能优于原版。",
|
||||
"软件护城河从代码转向测试用例，例如SQLite的闭源测试套件TH3是其难以复刻的核心。",
|
||||
"AI复刻软件引发版权争议，如chardet项目因许可证更改产生纠纷，且AI生成物可能无版权。",
|
||||
"文章列举了多个科技动态，包括AI改写脏话、激光飞机上网、数字分身争议等。",
|
||||
"周刊还包含工具推荐、资源分享及读者评论，探讨了AI对程序员行业的影响。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源技术",
|
||||
"科技趋势",
|
||||
"版权法律"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入分析了AI对软件行业的冲击，提出了测试作为新护城河的见解，具有前瞻性和讨论价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Article may be behind a paywall.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 95
|
||||
}
|
||||
+129
File diff suppressed because one or more lines are too long
+42
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:419828361de854cd29dbcd3e8205d3da50ff955ac9c85861d2e195bc888b2103",
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"published_at": "2026-01-25T18:20:16Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能，如可自定义的注册关闭消息，并进行了性能优化。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的多个回归错误。",
|
||||
"新增了可自定义的注册关闭消息和 Apache 访问日志中的用户名记录功能。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了涉及过滤器、标签搜索、RSS/OPML 访问和数据库等多个具体问题。",
|
||||
"该版本由多位贡献者共同完成，包括新加入的开发者。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug 修复",
|
||||
"回归问题",
|
||||
"GReader API",
|
||||
"HTTP Basic Auth",
|
||||
"Ajax 请求",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "该文章清晰记录了 FreshRSS 一个具体版本的更新内容，对用户和开发者具有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
+129
File diff suppressed because one or more lines are too long
+42
@@ -0,0 +1,42 @@
|
||||
{
|
||||
"candidate_id": "cand:sha256:6b36071bbd22c58692c039e172669ae28ac1ec8a6a6bce150c22d80af29761fc",
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"published_at": "2025-12-24T19:27:23Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了多项新功能、性能改进和错误修复。更新包括新的排序过滤选项、高级搜索表单、API 功能增强以及 Docker 镜像更新。此版本还包含安全增强、UI 优化和针对大型实例的性能扩展。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，支持如 userdate:PT1H 的搜索操作符。",
|
||||
"改进了对拥有 1000 以上用户的大型实例的统计信息扩展和 SQL 查询速度。",
|
||||
"Docker 默认镜像已更新至 Debian 13 Trixie 和 PHP 8.4.11。",
|
||||
"修复了 OpenID Connect 在 Debian 13 上的问题以及 MySQL/MariaDB 的错误排序。",
|
||||
"将不安全的自动登录功能移至扩展，并对部分扩展存在潜在的破坏性变更。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Capy Reader",
|
||||
"Docker",
|
||||
"Debian 13 Trixie",
|
||||
"PHP 8.4.11",
|
||||
"OpenID Connect"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS 阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统维护"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "该文章详细记录了 FreshRSS 一个重要版本的功能更新、性能优化和修复内容，对用户和开发者具有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
@@ -0,0 +1,224 @@
|
||||
{
|
||||
"schema_version": "v1",
|
||||
"generated_at": "2026-03-26T02:17:31.459980Z",
|
||||
"run_id": "openclaw-delivery-20260326-021731",
|
||||
"date": "2026-03-25",
|
||||
"candidates": [
|
||||
{
|
||||
"candidate_id": "cand:sha256:0d315d9489010cfd470a8d479e4e4443722fffdc34ecc1245c1b92458ace5093",
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"published_at": "2026-03-12T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本期讨论了AI快速复刻大型软件的现象，以Cloudflare工程师一周内用AI重写Next.js为例。文章指出，完备的测试用例成为软件公司防止AI复刻的新护城河，并探讨了AI复刻带来的版权问题。",
|
||||
"highlights": [
|
||||
"Cloudflare工程师仅用一周和1100美元Token费用，通过AI复刻了Next.js，性能优于原版。",
|
||||
"软件护城河从代码转向测试用例，例如SQLite的闭源测试套件TH3是其难以复刻的核心。",
|
||||
"AI复刻软件引发版权争议，如chardet项目因许可证更改产生纠纷，且AI生成物可能无版权。",
|
||||
"文章列举了多个科技动态，包括AI改写脏话、激光飞机上网、数字分身争议等。",
|
||||
"周刊还包含工具推荐、资源分享及读者评论，探讨了AI对程序员行业的影响。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源技术",
|
||||
"科技趋势",
|
||||
"版权法律"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入分析了AI对软件行业的冲击，提出了测试作为新护城河的见解，具有前瞻性和讨论价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Article may be behind a paywall.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 95
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:4139f277b8cb621b02b3398f8a7bd78e3f9eef7bcd320b70b8590e802540c6ca",
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"published_at": "2026-03-21T10:19:11Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被揭露实为套壳中国模型Kimi K2.5。尽管Cursor通过合作伙伴获得授权未侵权，但其隐瞒行为被认为是为支撑高估值而包装成自研模型公司。事件引发对国产大模型技术输出和信心的讨论。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际请求的模型ID为Kimi K2.5。",
|
||||
"Cursor通过Fireworks AI获得Kimi授权，未违反许可条款，但刻意隐瞒使用事实。",
|
||||
"Cursor估值在短期内从数千万美元飙升至数百亿美元，有动机包装自研能力以支撑估值。",
|
||||
"事件显示中国大模型技术已能对外输出，国产模型与国外旗舰差距正在缩小。",
|
||||
"Kimi在此事件中获得大量曝光，其下一代K3模型被期待有显著性能提升。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"模型套壳",
|
||||
"MIT许可证",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术授权",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入剖析了AI行业热点事件，涉及技术真相、商业动机和产业趋势，具有较高的讨论和参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:a16942c9699333155498d2bc59c530358bd6d81d9afe01e2b96e0e862edfc6a6",
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"canonical_url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"published_at": "2026-03-19T23:59:16Z",
|
||||
"author": "阮一峰",
|
||||
"source_name": "阮一峰的网络日志",
|
||||
"language": null,
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何有效招聘程序员。作者认为传统的代码能力考察将不再重要，面试重点应转向考察应聘者使用AI工具、分解项目需求以及系统架构的能力。文章也指出，目前尚难确定一套能可靠筛选合格AI编程人才的面试问题。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的核心考察点将从手写代码能力转向熟练运用AI工具的能力。",
|
||||
"面试问题可能包括如何将复杂需求转化为清晰的提示词，以及设计多Agent协同工作机制。",
|
||||
"传统的编程语法细节考察意义下降，系统架构知识和项目经验可能仍是重要参考。",
|
||||
"AI的快速发展使得软件开发流程和人才评估标准面临颠覆性变化。",
|
||||
"文章还包含科技动态、工具推荐、资源分享等周刊常规栏目内容。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"多Agent协同",
|
||||
"系统架构",
|
||||
"科技动态",
|
||||
"工具推荐"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"科技资讯",
|
||||
"效率工具"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "文章深入探讨了AI时代对程序员职业及招聘流程的潜在影响，具有前瞻性和讨论价值，且内容结构完整、信息量丰富。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:419828361de854cd29dbcd3e8205d3da50ff955ac9c85861d2e195bc888b2103",
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"published_at": "2026-01-25T18:20:16Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能，如可自定义的注册关闭消息，并进行了性能优化。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的多个回归错误。",
|
||||
"新增了可自定义的注册关闭消息和 Apache 访问日志中的用户名记录功能。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了涉及过滤器、标签搜索、RSS/OPML 访问和数据库等多个具体问题。",
|
||||
"该版本由多位贡献者共同完成，包括新加入的开发者。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug 修复",
|
||||
"回归问题",
|
||||
"GReader API",
|
||||
"HTTP Basic Auth",
|
||||
"Ajax 请求",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "该文章清晰记录了 FreshRSS 一个具体版本的更新内容，对用户和开发者具有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
},
|
||||
{
|
||||
"candidate_id": "cand:sha256:6b36071bbd22c58692c039e172669ae28ac1ec8a6a6bce150c22d80af29761fc",
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"canonical_url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"published_at": "2025-12-24T19:27:23Z",
|
||||
"author": "Alkarex",
|
||||
"source_name": "FreshRSS releases",
|
||||
"language": null,
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了多项新功能、性能改进和错误修复。更新包括新的排序过滤选项、高级搜索表单、API 功能增强以及 Docker 镜像更新。此版本还包含安全增强、UI 优化和针对大型实例的性能扩展。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，支持如 userdate:PT1H 的搜索操作符。",
|
||||
"改进了对拥有 1000 以上用户的大型实例的统计信息扩展和 SQL 查询速度。",
|
||||
"Docker 默认镜像已更新至 Debian 13 Trixie 和 PHP 8.4.11。",
|
||||
"修复了 OpenID Connect 在 Debian 13 上的问题以及 MySQL/MariaDB 的错误排序。",
|
||||
"将不安全的自动登录功能移至扩展，并对部分扩展存在潜在的破坏性变更。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Capy Reader",
|
||||
"Docker",
|
||||
"Debian 13 Trixie",
|
||||
"PHP 8.4.11",
|
||||
"OpenID Connect"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS 阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统维护"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"worth_reason": "该文章详细记录了 FreshRSS 一个重要版本的功能更新、性能优化和修复内容，对用户和开发者具有明确的参考价值。",
|
||||
"selection_decision": "review",
|
||||
"selection_reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"digest_section_hint": null,
|
||||
"digest_rank": 60
|
||||
}
|
||||
],
|
||||
"stats": {
|
||||
"total": 5,
|
||||
"keep_total": 0,
|
||||
"review_total": 5,
|
||||
"drop_total": 0
|
||||
}
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"success": true,
|
||||
"article": {
|
||||
"extract_id": "sha256:169f2b50eec3d198df126a8daedb95c48cff252ead9d4d2598a449e128cae2b8",
|
||||
"item_id": "sha256:419828361de854cd29dbcd3e8205d3da50ff955ac9c85861d2e195bc888b2103",
|
||||
"source_id": "freshrss:2987af960359c5c0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"author": "Alkarex",
|
||||
"published_at": "2026-01-25T18:20:16Z",
|
||||
"language": null,
|
||||
"content_kind": "article",
|
||||
"plain_text": "Alkarex\nreleased this\n25 Jan 18:20\n·\n79 commits\nto edge\nsince this release\nImmutable\nrelease. Only release title and notes can be modified.\nThis is a release focussing on bug fixing, in particular regressions from the release 1.28.0.\nSelected new features ✨:\n- New customisable message for closed registrations\n- Add username in Apache access logs (also in Docker logs): for GReader API, and for HTTP Basic Auth from reverse proxy\nImproved performance 🏎️:\n- Disable counting articles in user labels for Ajax requests (unused)\nMany bug fixes 🐛\nThis release has been made by @Alkarex, @Frenzie, @Inverle and newcomers @ciro-mota, @eveiscoull, @hackerman70000, @Hufschmidt, @johan456789, @martgnz, @mmeier86, @netsho, @neuhaus, @RobLoach, @rupakbajgain.\nFull changelog:\n- Features\n- Bug fixing\n- Fix unwanted expansion of user queries (saved searches) applied to filters #8395\n- Fix encoding of filter actions for labels #8368\n- Fix searching of tags #8425\n- Fix refreshing feeds with token while anonymous refresh is disabled #8371\n- Fix RSS and OPML access by token #8434\n- Fix MySQL/MariaDB\ntransliterator_transliterate\nfallback (when thephp-intl\nextension is unavailable) #8427 - Fix regression with MySQL/MariaDB index hint #8460\n- Auto-add\nlastUserModified\ndatabase column also during mark-as-read action #8346 - Do not include hidden feeds when counting unread articles in categories #8357\n- Remove wrong PHP deprecation of OPML export action #8399\n- Fix shortcut for next unread article #8466\n- Fix custom\nsession.cookie-lifetime\n#8446 - Fix feed validator button when changing the feed URL #8436\n- Performance\n- Disable counting articles in user labels for Ajax requests (unused) #8352\n- Security\n- Deployment\n- Add username in Apache access logs (also in Docker logs): for GReader API, and for HTTP Basic Auth from reverse proxy #8392\n- SimplePie\n- Update of\nCURLOPT_ACCEPT_ENCODING\n#8376, simplepie#960, simplepie#962 - Fix don’t preserve children inside disallowed\n<template>\nelement #8443 - Fixes before PHPStan 2 #8445, simplepie#957\n- Update of\n- Extensions\n- Update\n.gitignore\nto ignore installed extensions #8372\n- Update\n- UI\n- I18n\n- Misc.",
|
||||
"quality_flags": {
|
||||
"is_paywalled": false,
|
||||
"is_truncated": false,
|
||||
"is_low_content": false
|
||||
},
|
||||
"metadata": {
|
||||
"content_source": "fetched_html",
|
||||
"extractor": "trafilatura",
|
||||
"char_count": 2155
|
||||
},
|
||||
"pipeline_state": "extracted"
|
||||
},
|
||||
"error": null,
|
||||
"debug": {
|
||||
"content_source": "fetched_html",
|
||||
"extractor": "trafilatura"
|
||||
},
|
||||
"warnings": []
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,40 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-paywalled-content",
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Article may be behind a paywall.",
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"paywall",
|
||||
"quality",
|
||||
"summary"
|
||||
],
|
||||
"priority": 95,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-paywalled-content",
|
||||
"decision": "review",
|
||||
"reason": "Article may be behind a paywall.",
|
||||
"labels": [
|
||||
"quality",
|
||||
"paywall"
|
||||
],
|
||||
"priority": 95
|
||||
},
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"decision": "review",
|
||||
"matched_rules": [
|
||||
"review-worth-keeping-other"
|
||||
],
|
||||
"reasons": [
|
||||
"Worth-keeping signal is positive but no stronger keep rule matched."
|
||||
],
|
||||
"labels": [
|
||||
"needs-review",
|
||||
"summary"
|
||||
],
|
||||
"priority": 60,
|
||||
"matches": [
|
||||
{
|
||||
"rule_id": "review-worth-keeping-other",
|
||||
"decision": "review",
|
||||
"reason": "Worth-keeping signal is positive but no stronger keep rule matched.",
|
||||
"labels": [
|
||||
"summary",
|
||||
"needs-review"
|
||||
],
|
||||
"priority": 60
|
||||
}
|
||||
]
|
||||
}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被揭露实为套壳中国模型Kimi K2.5。尽管Cursor通过合作伙伴获得授权未侵权，但其隐瞒行为被认为是为支撑高估值而包装成自研模型公司。事件引发对国产大模型技术输出和信心的讨论。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际请求的模型ID为Kimi K2.5。",
|
||||
"Cursor通过Fireworks AI获得Kimi授权，未违反许可条款，但刻意隐瞒使用事实。",
|
||||
"Cursor估值在短期内从数千万美元飙升至数百亿美元，有动机包装自研能力以支撑估值。",
|
||||
"事件显示中国大模型技术已能对外输出，国产模型与国外旗舰差距正在缩小。",
|
||||
"Kimi在此事件中获得大量曝光，其下一代K3模型被期待有显著性能提升。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"模型套壳",
|
||||
"MIT许可证",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术授权",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业热点事件，涉及技术真相、商业动机和产业趋势，具有较高的讨论和参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,11 @@
|
||||
{
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被揭露实为套壳中国模型Kimi K2.5。尽管Cursor通过合作伙伴获得授权未侵权，但其隐瞒行为被认为是为支撑高估值而包装成自研模型公司。事件引发对国产大模型技术输出和信心的讨论。",
|
||||
"highlights": ["Cursor的Composer 2模型被技术手段揭露实际请求的模型ID为Kimi K2.5。", "Cursor通过Fireworks AI获得Kimi授权，未违反许可条款，但刻意隐瞒使用事实。", "Cursor估值在短期内从数千万美元飙升至数百亿美元，有动机包装自研能力以支撑估值。", "事件显示中国大模型技术已能对外输出，国产模型与国外旗舰差距正在缩小。", "Kimi在此事件中获得大量曝光，其下一代K3模型被期待有显著性能提升。"],
|
||||
"keywords": ["Cursor", "Composer 2", "Kimi K2.5", "Fireworks AI", "模型套壳", "MIT许可证", "估值泡沫", "AI编程工具"],
|
||||
"topics": ["人工智能", "大模型", "商业伦理", "技术授权", "创业融资"],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业热点事件，涉及技术真相、商业动机和产业趋势，具有较高的讨论和参考价值。"
|
||||
}
|
||||
+37
@@ -0,0 +1,37 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [],
|
||||
"normalized_result": {
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被揭露实为套壳中国模型Kimi K2.5。尽管Cursor通过合作伙伴获得授权未侵权，但其隐瞒行为被认为是为支撑高估值而包装成自研模型公司。事件引发对国产大模型技术输出和信心的讨论。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际请求的模型ID为Kimi K2.5。",
|
||||
"Cursor通过Fireworks AI获得Kimi授权，未违反许可条款，但刻意隐瞒使用事实。",
|
||||
"Cursor估值在短期内从数千万美元飙升至数百亿美元，有动机包装自研能力以支撑估值。",
|
||||
"事件显示中国大模型技术已能对外输出，国产模型与国外旗舰差距正在缩小。",
|
||||
"Kimi在此事件中获得大量曝光，其下一代K3模型被期待有显著性能提升。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"模型套壳",
|
||||
"MIT许可证",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术授权",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业热点事件，涉及技术真相、商业动机和产业趋势，具有较高的讨论和参考价值。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被揭露实为套壳中国模型Kimi K2.5。尽管Cursor通过合作伙伴获得授权未侵权，但其隐瞒行为被认为是为支撑高估值而包装成自研模型公司。事件引发对国产大模型技术输出和信心的讨论。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际请求的模型ID为Kimi K2.5。",
|
||||
"Cursor通过Fireworks AI获得Kimi授权，未违反许可条款，但刻意隐瞒使用事实。",
|
||||
"Cursor估值在短期内从数千万美元飙升至数百亿美元，有动机包装自研能力以支撑估值。",
|
||||
"事件显示中国大模型技术已能对外输出，国产模型与国外旗舰差距正在缩小。",
|
||||
"Kimi在此事件中获得大量曝光，其下一代K3模型被期待有显著性能提升。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"模型套壳",
|
||||
"MIT许可证",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术授权",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业热点事件，涉及技术真相、商业动机和产业趋势，具有较高的讨论和参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何有效招聘程序员。作者认为传统的代码能力考察将不再重要，面试重点应转向考察应聘者使用AI工具、分解项目需求以及系统架构的能力。文章也指出，目前尚难确定一套能可靠筛选合格AI编程人才的面试问题。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的核心考察点将从手写代码能力转向熟练运用AI工具的能力。",
|
||||
"面试问题可能包括如何将复杂需求转化为清晰的提示词，以及设计多Agent协同工作机制。",
|
||||
"传统的编程语法细节考察意义下降，系统架构知识和项目经验可能仍是重要参考。",
|
||||
"AI的快速发展使得软件开发流程和人才评估标准面临颠覆性变化。",
|
||||
"文章还包含科技动态、工具推荐、资源分享等周刊常规栏目内容。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"多Agent协同",
|
||||
"系统架构",
|
||||
"科技动态",
|
||||
"工具推荐"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"科技资讯",
|
||||
"效率工具"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代对程序员职业及招聘流程的潜在影响，具有前瞻性和讨论价值，且内容结构完整、信息量丰富。"
|
||||
}
|
||||
@@ -0,0 +1,19 @@
|
||||
```json
|
||||
{
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何有效招聘程序员。作者认为传统的代码能力考察将不再重要，面试重点应转向考察应聘者使用AI工具、分解项目需求以及系统架构的能力。文章也指出，目前尚难确定一套能可靠筛选合格AI编程人才的面试问题。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的核心考察点将从手写代码能力转向熟练运用AI工具的能力。",
|
||||
"面试问题可能包括如何将复杂需求转化为清晰的提示词，以及设计多Agent协同工作机制。",
|
||||
"传统的编程语法细节考察意义下降，系统架构知识和项目经验可能仍是重要参考。",
|
||||
"AI的快速发展使得软件开发流程和人才评估标准面临颠覆性变化。",
|
||||
"文章还包含科技动态、工具推荐、资源分享等周刊常规栏目内容。"
|
||||
],
|
||||
"keywords": ["AI编程", "程序员招聘", "面试问题", "提示词工程", "多Agent协同", "系统架构", "科技动态", "工具推荐"],
|
||||
"topics": ["人工智能", "软件开发", "职业发展", "科技资讯", "效率工具"],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代对程序员职业及招聘流程的潜在影响，具有前瞻性和讨论价值，且内容结构完整、信息量丰富。"
|
||||
}
|
||||
```
|
||||
+37
@@ -0,0 +1,37 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [],
|
||||
"normalized_result": {
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何有效招聘程序员。作者认为传统的代码能力考察将不再重要，面试重点应转向考察应聘者使用AI工具、分解项目需求以及系统架构的能力。文章也指出，目前尚难确定一套能可靠筛选合格AI编程人才的面试问题。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的核心考察点将从手写代码能力转向熟练运用AI工具的能力。",
|
||||
"面试问题可能包括如何将复杂需求转化为清晰的提示词，以及设计多Agent协同工作机制。",
|
||||
"传统的编程语法细节考察意义下降，系统架构知识和项目经验可能仍是重要参考。",
|
||||
"AI的快速发展使得软件开发流程和人才评估标准面临颠覆性变化。",
|
||||
"文章还包含科技动态、工具推荐、资源分享等周刊常规栏目内容。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"多Agent协同",
|
||||
"系统架构",
|
||||
"科技动态",
|
||||
"工具推荐"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"科技资讯",
|
||||
"效率工具"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代对程序员职业及招聘流程的潜在影响，具有前瞻性和讨论价值，且内容结构完整、信息量丰富。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何有效招聘程序员。作者认为传统的代码能力考察将不再重要，面试重点应转向考察应聘者使用AI工具、分解项目需求以及系统架构的能力。文章也指出，目前尚难确定一套能可靠筛选合格AI编程人才的面试问题。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的核心考察点将从手写代码能力转向熟练运用AI工具的能力。",
|
||||
"面试问题可能包括如何将复杂需求转化为清晰的提示词，以及设计多Agent协同工作机制。",
|
||||
"传统的编程语法细节考察意义下降，系统架构知识和项目经验可能仍是重要参考。",
|
||||
"AI的快速发展使得软件开发流程和人才评估标准面临颠覆性变化。",
|
||||
"文章还包含科技动态、工具推荐、资源分享等周刊常规栏目内容。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"多Agent协同",
|
||||
"系统架构",
|
||||
"科技动态",
|
||||
"工具推荐"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"科技资讯",
|
||||
"效率工具"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代对程序员职业及招聘流程的潜在影响，具有前瞻性和讨论价值，且内容结构完整、信息量丰富。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"summary": "本期讨论了AI快速复刻大型软件的现象，以Cloudflare工程师一周内用AI重写Next.js为例。文章指出，完备的测试用例成为软件公司防止AI复刻的新护城河，并探讨了AI复刻带来的版权问题。",
|
||||
"highlights": [
|
||||
"Cloudflare工程师仅用一周和1100美元Token费用，通过AI复刻了Next.js，性能优于原版。",
|
||||
"软件护城河从代码转向测试用例，例如SQLite的闭源测试套件TH3是其难以复刻的核心。",
|
||||
"AI复刻软件引发版权争议，如chardet项目因许可证更改产生纠纷，且AI生成物可能无版权。",
|
||||
"文章列举了多个科技动态，包括AI改写脏话、激光飞机上网、数字分身争议等。",
|
||||
"周刊还包含工具推荐、资源分享及读者评论，探讨了AI对程序员行业的影响。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源技术",
|
||||
"科技趋势",
|
||||
"版权法律"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入分析了AI对软件行业的冲击，提出了测试作为新护城河的见解，具有前瞻性和讨论价值。"
|
||||
}
|
||||
@@ -0,0 +1,11 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"summary": "本期讨论了AI快速复刻大型软件的现象，以Cloudflare工程师一周内用AI重写Next.js为例。文章指出，完备的测试用例成为软件公司防止AI复刻的新护城河，并探讨了AI复刻带来的版权问题。",
|
||||
"highlights": ["Cloudflare工程师仅用一周和1100美元Token费用，通过AI复刻了Next.js，性能优于原版。", "软件护城河从代码转向测试用例，例如SQLite的闭源测试套件TH3是其难以复刻的核心。", "AI复刻软件引发版权争议，如chardet项目因许可证更改产生纠纷，且AI生成物可能无版权。", "文章列举了多个科技动态，包括AI改写脏话、激光飞机上网、数字分身争议等。", "周刊还包含工具推荐、资源分享及读者评论，探讨了AI对程序员行业的影响。"],
|
||||
"keywords": ["Next.js", "AI复刻", "测试用例", "SQLite", "MIT许可证", "Cloudflare", "vinext", "护城河"],
|
||||
"topics": ["人工智能", "软件开发", "开源技术", "科技趋势", "版权法律"],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入分析了AI对软件行业的冲击，提出了测试作为新护城河的见解，具有前瞻性和讨论价值。"
|
||||
}
|
||||
+37
@@ -0,0 +1,37 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [],
|
||||
"normalized_result": {
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"summary": "本期讨论了AI快速复刻大型软件的现象，以Cloudflare工程师一周内用AI重写Next.js为例。文章指出，完备的测试用例成为软件公司防止AI复刻的新护城河，并探讨了AI复刻带来的版权问题。",
|
||||
"highlights": [
|
||||
"Cloudflare工程师仅用一周和1100美元Token费用，通过AI复刻了Next.js，性能优于原版。",
|
||||
"软件护城河从代码转向测试用例，例如SQLite的闭源测试套件TH3是其难以复刻的核心。",
|
||||
"AI复刻软件引发版权争议，如chardet项目因许可证更改产生纠纷，且AI生成物可能无版权。",
|
||||
"文章列举了多个科技动态，包括AI改写脏话、激光飞机上网、数字分身争议等。",
|
||||
"周刊还包含工具推荐、资源分享及读者评论，探讨了AI对程序员行业的影响。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源技术",
|
||||
"科技趋势",
|
||||
"版权法律"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入分析了AI对软件行业的冲击，提出了测试作为新护城河的见解，具有前瞻性和讨论价值。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"summary": "本期讨论了AI快速复刻大型软件的现象，以Cloudflare工程师一周内用AI重写Next.js为例。文章指出，完备的测试用例成为软件公司防止AI复刻的新护城河，并探讨了AI复刻带来的版权问题。",
|
||||
"highlights": [
|
||||
"Cloudflare工程师仅用一周和1100美元Token费用，通过AI复刻了Next.js，性能优于原版。",
|
||||
"软件护城河从代码转向测试用例，例如SQLite的闭源测试套件TH3是其难以复刻的核心。",
|
||||
"AI复刻软件引发版权争议，如chardet项目因许可证更改产生纠纷，且AI生成物可能无版权。",
|
||||
"文章列举了多个科技动态，包括AI改写脏话、激光飞机上网、数字分身争议等。",
|
||||
"周刊还包含工具推荐、资源分享及读者评论，探讨了AI对程序员行业的影响。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源技术",
|
||||
"科技趋势",
|
||||
"版权法律"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入分析了AI对软件行业的冲击，提出了测试作为新护城河的见解，具有前瞻性和讨论价值。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能，如可自定义的注册关闭消息，并进行了性能优化。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的多个回归错误。",
|
||||
"新增了可自定义的注册关闭消息和 Apache 访问日志中的用户名记录功能。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了涉及过滤器、标签搜索、RSS/OPML 访问和数据库等多个具体问题。",
|
||||
"该版本由多位贡献者共同完成，包括新加入的开发者。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug 修复",
|
||||
"回归问题",
|
||||
"GReader API",
|
||||
"HTTP Basic Auth",
|
||||
"Ajax 请求",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章清晰记录了 FreshRSS 一个具体版本的更新内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,11 @@
|
||||
{
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能，如可自定义的注册关闭消息，并进行了性能优化。",
|
||||
"highlights": ["此版本主要修复了 1.28.0 版本引入的多个回归错误。", "新增了可自定义的注册关闭消息和 Apache 访问日志中的用户名记录功能。", "通过禁用 Ajax 请求中用户标签的文章计数来提升性能。", "修复了涉及过滤器、标签搜索、RSS/OPML 访问和数据库等多个具体问题。", "该版本由多位贡献者共同完成，包括新加入的开发者。"],
|
||||
"keywords": ["FreshRSS", "bug 修复", "回归问题", "GReader API", "HTTP Basic Auth", "Ajax 请求", "MySQL", "MariaDB"],
|
||||
"topics": ["开源软件", "版本更新", "RSS 阅读器", "软件开发", "性能优化"],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章清晰记录了 FreshRSS 一个具体版本的更新内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
+39
@@ -0,0 +1,39 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [
|
||||
"`??` category marked as worth keeping; check if this is intentional."
|
||||
],
|
||||
"normalized_result": {
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能，如可自定义的注册关闭消息，并进行了性能优化。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的多个回归错误。",
|
||||
"新增了可自定义的注册关闭消息和 Apache 访问日志中的用户名记录功能。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了涉及过滤器、标签搜索、RSS/OPML 访问和数据库等多个具体问题。",
|
||||
"该版本由多位贡献者共同完成，包括新加入的开发者。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug 修复",
|
||||
"回归问题",
|
||||
"GReader API",
|
||||
"HTTP Basic Auth",
|
||||
"Ajax 请求",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章清晰记录了 FreshRSS 一个具体版本的更新内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "FreshRSS 1.28.1",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.1",
|
||||
"summary": "FreshRSS 1.28.1 是一个专注于修复错误的版本，主要解决了 1.28.0 版本引入的回归问题。该版本包含少量新功能，如可自定义的注册关闭消息，并进行了性能优化。",
|
||||
"highlights": [
|
||||
"此版本主要修复了 1.28.0 版本引入的多个回归错误。",
|
||||
"新增了可自定义的注册关闭消息和 Apache 访问日志中的用户名记录功能。",
|
||||
"通过禁用 Ajax 请求中用户标签的文章计数来提升性能。",
|
||||
"修复了涉及过滤器、标签搜索、RSS/OPML 访问和数据库等多个具体问题。",
|
||||
"该版本由多位贡献者共同完成，包括新加入的开发者。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"bug 修复",
|
||||
"回归问题",
|
||||
"GReader API",
|
||||
"HTTP Basic Auth",
|
||||
"Ajax 请求",
|
||||
"MySQL",
|
||||
"MariaDB"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"版本更新",
|
||||
"RSS 阅读器",
|
||||
"软件开发",
|
||||
"性能优化"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章清晰记录了 FreshRSS 一个具体版本的更新内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了多项新功能、性能改进和错误修复。更新包括新的排序过滤选项、高级搜索表单、API 功能增强以及 Docker 镜像更新。此版本还包含安全增强、UI 优化和针对大型实例的性能扩展。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，支持如 userdate:PT1H 的搜索操作符。",
|
||||
"改进了对拥有 1000 以上用户的大型实例的统计信息扩展和 SQL 查询速度。",
|
||||
"Docker 默认镜像已更新至 Debian 13 Trixie 和 PHP 8.4.11。",
|
||||
"修复了 OpenID Connect 在 Debian 13 上的问题以及 MySQL/MariaDB 的错误排序。",
|
||||
"将不安全的自动登录功能移至扩展，并对部分扩展存在潜在的破坏性变更。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Capy Reader",
|
||||
"Docker",
|
||||
"Debian 13 Trixie",
|
||||
"PHP 8.4.11",
|
||||
"OpenID Connect"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS 阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统维护"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章详细记录了 FreshRSS 一个重要版本的功能更新、性能优化和修复内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,19 @@
|
||||
```json
|
||||
{
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了多项新功能、性能改进和错误修复。更新包括新的排序过滤选项、高级搜索表单、API 功能增强以及 Docker 镜像更新。此版本还包含安全增强、UI 优化和针对大型实例的性能扩展。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，支持如 userdate:PT1H 的搜索操作符。",
|
||||
"改进了对拥有 1000 以上用户的大型实例的统计信息扩展和 SQL 查询速度。",
|
||||
"Docker 默认镜像已更新至 Debian 13 Trixie 和 PHP 8.4.11。",
|
||||
"修复了 OpenID Connect 在 Debian 13 上的问题以及 MySQL/MariaDB 的错误排序。",
|
||||
"将不安全的自动登录功能移至扩展，并对部分扩展存在潜在的破坏性变更。"
|
||||
],
|
||||
"keywords": ["FreshRSS", "用户修改日期排序", "高级搜索表单", "Capy Reader", "Docker", "Debian 13 Trixie", "PHP 8.4.11", "OpenID Connect"],
|
||||
"topics": ["开源软件", "RSS 阅读器", "版本发布", "软件开发", "系统维护"],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章详细记录了 FreshRSS 一个重要版本的功能更新、性能优化和修复内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
```
|
||||
+39
@@ -0,0 +1,39 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [
|
||||
"`??` category marked as worth keeping; check if this is intentional."
|
||||
],
|
||||
"normalized_result": {
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了多项新功能、性能改进和错误修复。更新包括新的排序过滤选项、高级搜索表单、API 功能增强以及 Docker 镜像更新。此版本还包含安全增强、UI 优化和针对大型实例的性能扩展。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，支持如 userdate:PT1H 的搜索操作符。",
|
||||
"改进了对拥有 1000 以上用户的大型实例的统计信息扩展和 SQL 查询速度。",
|
||||
"Docker 默认镜像已更新至 Debian 13 Trixie 和 PHP 8.4.11。",
|
||||
"修复了 OpenID Connect 在 Debian 13 上的问题以及 MySQL/MariaDB 的错误排序。",
|
||||
"将不安全的自动登录功能移至扩展，并对部分扩展存在潜在的破坏性变更。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Capy Reader",
|
||||
"Docker",
|
||||
"Debian 13 Trixie",
|
||||
"PHP 8.4.11",
|
||||
"OpenID Connect"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS 阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统维护"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章详细记录了 FreshRSS 一个重要版本的功能更新、性能优化和修复内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "FreshRSS 1.28.0",
|
||||
"url": "https://github.com/FreshRSS/FreshRSS/releases/tag/1.28.0",
|
||||
"summary": "FreshRSS 1.28.0 是一个主要版本更新，引入了多项新功能、性能改进和错误修复。更新包括新的排序过滤选项、高级搜索表单、API 功能增强以及 Docker 镜像更新。此版本还包含安全增强、UI 优化和针对大型实例的性能扩展。",
|
||||
"highlights": [
|
||||
"新增按用户修改日期排序和过滤功能，支持如 userdate:PT1H 的搜索操作符。",
|
||||
"改进了对拥有 1000 以上用户的大型实例的统计信息扩展和 SQL 查询速度。",
|
||||
"Docker 默认镜像已更新至 Debian 13 Trixie 和 PHP 8.4.11。",
|
||||
"修复了 OpenID Connect 在 Debian 13 上的问题以及 MySQL/MariaDB 的错误排序。",
|
||||
"将不安全的自动登录功能移至扩展，并对部分扩展存在潜在的破坏性变更。"
|
||||
],
|
||||
"keywords": [
|
||||
"FreshRSS",
|
||||
"用户修改日期排序",
|
||||
"高级搜索表单",
|
||||
"Capy Reader",
|
||||
"Docker",
|
||||
"Debian 13 Trixie",
|
||||
"PHP 8.4.11",
|
||||
"OpenID Connect"
|
||||
],
|
||||
"topics": [
|
||||
"开源软件",
|
||||
"RSS 阅读器",
|
||||
"版本发布",
|
||||
"软件开发",
|
||||
"系统维护"
|
||||
],
|
||||
"category": "资讯",
|
||||
"worth_keeping": true,
|
||||
"reason": "该文章详细记录了 FreshRSS 一个重要版本的功能更新、性能优化和修复内容，对用户和开发者具有明确的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被证实套壳中国Kimi K2.5模型，引发侵权争议。Kimi官方确认Cursor通过Fireworks AI获得授权，不存在侵权。作者分析Cursor隐瞒事实是为了支撑其不断膨胀的估值，将其包装成大模型公司。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际调用的是Kimi K2.5模型。",
|
||||
"Kimi官方确认Cursor通过Fireworks AI获得授权，因此不构成侵权。",
|
||||
"Cursor隐瞒使用Kimi模型，被认为是为了支撑其高达500亿美元的估值。",
|
||||
"事件显示中国大模型技术已具备输出能力，国产模型与国外旗舰差距缩小。",
|
||||
"Composer 2性能低于GPT-5.4但成本最低，生成速度较快。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"套壳模型",
|
||||
"模型授权",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术争议",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业的热点事件，涉及技术真相、商业动机和行业趋势，具有较高的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,11 @@
|
||||
{
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被证实套壳中国Kimi K2.5模型，引发侵权争议。Kimi官方确认Cursor通过Fireworks AI获得授权，不存在侵权。作者分析Cursor隐瞒事实是为了支撑其不断膨胀的估值，将其包装成大模型公司。",
|
||||
"highlights": ["Cursor的Composer 2模型被技术手段揭露实际调用的是Kimi K2.5模型。", "Kimi官方确认Cursor通过Fireworks AI获得授权，因此不构成侵权。", "Cursor隐瞒使用Kimi模型，被认为是为了支撑其高达500亿美元的估值。", "事件显示中国大模型技术已具备输出能力，国产模型与国外旗舰差距缩小。", "Composer 2性能低于GPT-5.4但成本最低，生成速度较快。"],
|
||||
"keywords": ["Cursor", "Composer 2", "Kimi K2.5", "Fireworks AI", "套壳模型", "模型授权", "估值泡沫", "AI编程工具"],
|
||||
"topics": ["人工智能", "大模型", "商业伦理", "技术争议", "创业融资"],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业的热点事件，涉及技术真相、商业动机和行业趋势，具有较高的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,37 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [],
|
||||
"normalized_result": {
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被证实套壳中国Kimi K2.5模型，引发侵权争议。Kimi官方确认Cursor通过Fireworks AI获得授权，不存在侵权。作者分析Cursor隐瞒事实是为了支撑其不断膨胀的估值，将其包装成大模型公司。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际调用的是Kimi K2.5模型。",
|
||||
"Kimi官方确认Cursor通过Fireworks AI获得授权，因此不构成侵权。",
|
||||
"Cursor隐瞒使用Kimi模型，被认为是为了支撑其高达500亿美元的估值。",
|
||||
"事件显示中国大模型技术已具备输出能力，国产模型与国外旗舰差距缩小。",
|
||||
"Composer 2性能低于GPT-5.4但成本最低，生成速度较快。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"套壳模型",
|
||||
"模型授权",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术争议",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业的热点事件，涉及技术真相、商业动机和行业趋势，具有较高的参考价值。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "套壳中国大模型撑起500亿美元估值？扒一扒 Cursor 的\"套壳\"疑云",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/kimi-cursor.html",
|
||||
"summary": "AI编程工具Cursor推出的Composer 2模型被证实套壳中国Kimi K2.5模型，引发侵权争议。Kimi官方确认Cursor通过Fireworks AI获得授权，不存在侵权。作者分析Cursor隐瞒事实是为了支撑其不断膨胀的估值，将其包装成大模型公司。",
|
||||
"highlights": [
|
||||
"Cursor的Composer 2模型被技术手段揭露实际调用的是Kimi K2.5模型。",
|
||||
"Kimi官方确认Cursor通过Fireworks AI获得授权，因此不构成侵权。",
|
||||
"Cursor隐瞒使用Kimi模型，被认为是为了支撑其高达500亿美元的估值。",
|
||||
"事件显示中国大模型技术已具备输出能力，国产模型与国外旗舰差距缩小。",
|
||||
"Composer 2性能低于GPT-5.4但成本最低，生成速度较快。"
|
||||
],
|
||||
"keywords": [
|
||||
"Cursor",
|
||||
"Composer 2",
|
||||
"Kimi K2.5",
|
||||
"Fireworks AI",
|
||||
"套壳模型",
|
||||
"模型授权",
|
||||
"估值泡沫",
|
||||
"AI编程工具"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"大模型",
|
||||
"商业伦理",
|
||||
"技术争议",
|
||||
"创业融资"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入剖析了AI行业的热点事件，涉及技术真相、商业动机和行业趋势，具有较高的参考价值。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何招聘和面试程序员。作者认为考察重点应从代码能力转向AI使用、架构理解和需求转化能力。文章指出传统面试方法面临挑战，并引发了对未来程序员核心技能的思考。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的重点可能从代码能力转向AI工具的使用熟练度。",
|
||||
"面试问题需要考察将复杂需求转化为清晰提示词的能力。",
|
||||
"AI编程时代，对系统架构知识和项目分解能力的要求依然重要。",
|
||||
"传统的编程语法细节考察在AI辅助下意义可能减弱。",
|
||||
"文章引发了关于AI如何颠覆软件开发及人才评估标准的讨论。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"Skill",
|
||||
"MCP",
|
||||
"多Agent协同",
|
||||
"系统架构"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"技术趋势",
|
||||
"人才评估"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代程序员招聘的前瞻性问题，具有启发性和讨论价值。"
|
||||
}
|
||||
@@ -0,0 +1,19 @@
|
||||
```json
|
||||
{
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何招聘和面试程序员。作者认为考察重点应从代码能力转向AI使用、架构理解和需求转化能力。文章指出传统面试方法面临挑战，并引发了对未来程序员核心技能的思考。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的重点可能从代码能力转向AI工具的使用熟练度。",
|
||||
"面试问题需要考察将复杂需求转化为清晰提示词的能力。",
|
||||
"AI编程时代，对系统架构知识和项目分解能力的要求依然重要。",
|
||||
"传统的编程语法细节考察在AI辅助下意义可能减弱。",
|
||||
"文章引发了关于AI如何颠覆软件开发及人才评估标准的讨论。"
|
||||
],
|
||||
"keywords": ["AI编程", "程序员招聘", "面试问题", "提示词工程", "Skill", "MCP", "多Agent协同", "系统架构"],
|
||||
"topics": ["人工智能", "软件开发", "职业发展", "技术趋势", "人才评估"],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代程序员招聘的前瞻性问题，具有启发性和讨论价值。"
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,37 @@
|
||||
{
|
||||
"valid": true,
|
||||
"errors": [],
|
||||
"warnings": [],
|
||||
"normalized_result": {
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何招聘和面试程序员。作者认为考察重点应从代码能力转向AI使用、架构理解和需求转化能力。文章指出传统面试方法面临挑战，并引发了对未来程序员核心技能的思考。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的重点可能从代码能力转向AI工具的使用熟练度。",
|
||||
"面试问题需要考察将复杂需求转化为清晰提示词的能力。",
|
||||
"AI编程时代，对系统架构知识和项目分解能力的要求依然重要。",
|
||||
"传统的编程语法细节考察在AI辅助下意义可能减弱。",
|
||||
"文章引发了关于AI如何颠覆软件开发及人才评估标准的讨论。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"Skill",
|
||||
"MCP",
|
||||
"多Agent协同",
|
||||
"系统架构"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"技术趋势",
|
||||
"人才评估"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代程序员招聘的前瞻性问题，具有启发性和讨论价值。"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 389 期）：未来如何招聘程序员",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-389.html",
|
||||
"summary": "本文探讨了在AI编程普及的未来，如何招聘和面试程序员。作者认为考察重点应从代码能力转向AI使用、架构理解和需求转化能力。文章指出传统面试方法面临挑战，并引发了对未来程序员核心技能的思考。",
|
||||
"highlights": [
|
||||
"未来程序员招聘的重点可能从代码能力转向AI工具的使用熟练度。",
|
||||
"面试问题需要考察将复杂需求转化为清晰提示词的能力。",
|
||||
"AI编程时代，对系统架构知识和项目分解能力的要求依然重要。",
|
||||
"传统的编程语法细节考察在AI辅助下意义可能减弱。",
|
||||
"文章引发了关于AI如何颠覆软件开发及人才评估标准的讨论。"
|
||||
],
|
||||
"keywords": [
|
||||
"AI编程",
|
||||
"程序员招聘",
|
||||
"面试问题",
|
||||
"提示词工程",
|
||||
"Skill",
|
||||
"MCP",
|
||||
"多Agent协同",
|
||||
"系统架构"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"职业发展",
|
||||
"技术趋势",
|
||||
"人才评估"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了AI时代程序员招聘的前瞻性问题，具有启发性和讨论价值。"
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"summary": "本文以 Cloudflare 工程师用 AI 在一周内复刻 Next.js 框架为例，指出 AI 使得代码的护城河不复存在。作者认为，软件公司未来将依赖保密的测试用例来防止 AI 复刻，测试成为新的竞争壁垒。",
|
||||
"highlights": [
|
||||
"Cloudflare 工程师仅用一周时间和 1100 美元 Token 费用，通过 AI 成功复刻了 Next.js 框架，性能优于原版。",
|
||||
"AI 能够复刻软件的关键在于开源项目提供了完备的文档、社区文章和测试用例，使得 API 兼容性得以验证。",
|
||||
"为防止 AI 复刻，大型软件项目可能选择将核心测试用例闭源，如 SQLite 的 TH3 测试套件和 tldraw 的计划。",
|
||||
"AI 复刻软件引发了版权争议，例如 chardet 项目的许可证更改，且美国法律认定 AI 生成物无版权，冲击现有许可证体系。",
|
||||
"文章还讨论了 AI 对软件行业的多方面影响，包括提高效率、替代岗位以及可能引发的社会复杂性崩溃问题。"
|
||||
],
|
||||
"keywords": [
|
||||
"Next.js",
|
||||
"AI 复刻",
|
||||
"测试用例",
|
||||
"SQLite",
|
||||
"MIT 许可证",
|
||||
"Cloudflare",
|
||||
"vinext",
|
||||
"护城河"
|
||||
],
|
||||
"topics": [
|
||||
"人工智能",
|
||||
"软件开发",
|
||||
"开源协议",
|
||||
"技术趋势",
|
||||
"行业影响"
|
||||
],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了 AI 对软件行业护城河的颠覆性影响，并提出了测试用例作为新壁垒的见解，具有前瞻性和讨论价值。"
|
||||
}
|
||||
@@ -0,0 +1,17 @@
|
||||
{
|
||||
"title": "科技爱好者周刊（第 388 期）：测试是新的护城河",
|
||||
"url": "http://www.ruanyifeng.com/blog/2026/03/weekly-issue-388.html",
|
||||
"summary": "本文以 Cloudflare 工程师用 AI 在一周内复刻 Next.js 框架为例，指出 AI 使得代码的护城河不复存在。作者认为，软件公司未来将依赖保密的测试用例来防止 AI 复刻，测试成为新的竞争壁垒。",
|
||||
"highlights": [
|
||||
"Cloudflare 工程师仅用一周时间和 1100 美元 Token 费用，通过 AI 成功复刻了 Next.js 框架，性能优于原版。",
|
||||
"AI 能够复刻软件的关键在于开源项目提供了完备的文档、社区文章和测试用例，使得 API 兼容性得以验证。",
|
||||
"为防止 AI 复刻，大型软件项目可能选择将核心测试用例闭源，如 SQLite 的 TH3 测试套件和 tldraw 的计划。",
|
||||
"AI 复刻软件引发了版权争议，例如 chardet 项目的许可证更改，且美国法律认定 AI 生成物无版权，冲击现有许可证体系。",
|
||||
"文章还讨论了 AI 对软件行业的多方面影响，包括提高效率、替代岗位以及可能引发的社会复杂性崩溃问题。"
|
||||
],
|
||||
"keywords": ["Next.js", "AI 复刻", "测试用例", "SQLite", "MIT 许可证", "Cloudflare", "vinext", "护城河"],
|
||||
"topics": ["人工智能", "软件开发", "开源协议", "技术趋势", "行业影响"],
|
||||
"category": "观点评论",
|
||||
"worth_keeping": true,
|
||||
"reason": "文章深入探讨了 AI 对软件行业护城河的颠覆性影响，并提出了测试用例作为新壁垒的见解，具有前瞻性和讨论价值。"
|
||||
}
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user