Z.ai says ZCode uploaded repo data, plans to open-source it after backlash
Mia@MiaAI_labOfficial response from ZAI: "We fully understand that any issue involving data directly affects users' trust in our product. In the near future, we will open-source the ZCode codebase to improve the product within a more open ecosystem.
- ▪Mia@MiaAI_labOfficial response from ZAI: "We fully understand that any issue involving data directly affects users' trust in our product.
- ▪In the near future, we will open-source the ZCode codebase to improve the product within a more open ecosystem.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,539 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | X (formerly Twitter) |
| Canonical URL | https://twitter.com/MiaAI_lab/status/2100998360643617148 |
| Publication time | Fri, 18 Sep 2026 18:03:03 +0000 |
| Retrieval time | 2026-09-18T18:08:45.448Z |
| Last seen | 2026-09-18T18:08:45.448Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 4UISNiG2Sd1W · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Mia@MiaAI_labOfficial response from ZAI: "We fully understand that any issue involving data directly affects users' trust in our product. In the near future, we will open-source the ZCode codebase to improve the product within a more open ecosystem. We will also invite independent third-party evaluators to audit the system's operation and continuously publish updates on the audit's progress." Our goal is to establish trust through complete transparency."Mia@MiaAI_lab3h (function (id, args) { var element = document.getElementById(id); if (!element) return; element.textContent = (function formatRelativePastTimestamp({ timestamp, lang, timeZone, nowLabel }) { const date = new Date(timestamp); const now = /* @__PURE__ */ new Date(); const diffInSeconds = Math.floor((now.getTime() -…
Excerpt limited to ~120 words for fair-use compliance. The full article is at X (formerly Twitter).
Discussion
0 commentsMore from X (formerly Twitter)
