Attributed metadata history
Up to 100 retained publisher events per page for a19462e9783c2bc7a648819e1b47a2a5cd1bf291b25be59a05e7d0ea9d3dee9f. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_6dc544294b7f21f98a
observed · 2026-10-14 11:03:02 UTC
The original genspark-ai/genoffice repository has 9580 stars, is written in TypeScript, and ships under Apache-2.0. The Chinese version, yangshun2005/genoffice-cn, was published today. It has zero stars, which is normal for a repository that is a few hours old, and I'm not going to pretend otherwise. What it is: a translated documentation fork. The code is the upstream code. What changed is the README — and, more usefully, a short "中文快速上手" section prepended to it that the original does not have. Why a translated README is not a trivial thing For an English-speaking developer, the genoffice README is a normal README. You skim the feature list, find the Releases link, download the right installer, and you're running in five minutes. For a Chinese-speaking developer, the same document has a specific failure mode that isn't about vocabulary. It's about where the operational details sit. The upstream README is organized as a product page: positioning first, feature bullets second, install links somewhere in the middle, and the CLI/MCP/agent-skill material further down. If you're evaluating whether this thing can do a job for you, you read top to bottom and ho
Fingerprint: aae9f27eb4b7158531ea5641cc3717139bf6e65a7166e7d8e087e9628f3c2b1a
intelligence_src_6dc544294b7f21f98a
observed · 2026-10-12 11:01:03 UTC
available
Fingerprint: 2faf9469031bd0e00603457ab86d15e2040aea06ef98482184945872c5cb389f