R Open Source RecordTHE TOML CHRONICLE
繁體中文Captured 27 Oct 2026
Open source × Localization × AI

A Traditional
Chinese translation.
An AI dispute.

The TOML chronicle

A request for a zh-TW locale became a debate about tools, quality, trust and the boundaries of collaboration.

03 GitHub threads144 Individual records23 Oct Proposal and PR opened25 Oct Renewed issue closed and locked
Chapters +

Reading settings

Preferences stay in this browser. Browser zoom (Ctrl/⌘ +) and pinch zoom remain available.

00 / IN BRIEF

The dispute in one minute

At the capture cutoffs: all three GitHub threads are closed, and translation PR #98 is unmerged.

  1. The request

    On October 23, Will (doggy8088) proposed a Traditional Chinese locale and submitted translations plus shared-interface changes. He later disclosed AI assistance and said he had reviewed the work.

  2. The escalation

    arp242 first objected to agent-mediated submissions and closed the original issue and PR. The new issue #99 on October 25 was closed and locked after the maintainer linked the Facebook post and confronted the contributor.

  3. The disagreement

    The contributor wants the result judged on quality; the maintainer expects carefully vetted human translations for the official site. Review evidence, maintenance costs, tone and wording extending suspicion to future zh-TW translations are also disputed.

  4. The responses

    Facebook contains support as well as criticism about integrity, public shaming and maintenance costs. In one reply, Will explicitly accepts criticism and acknowledges insufficient consideration; elsewhere he continues to prioritize result quality.

Public statements and recorded actions can be checked. This chronicle has not comprehensively reviewed the translations or resolved every allegation of deception, mobilization or discrimination.

01 / CONTEXT

Before the dispute,
there was a contribution.

Demand, submitted work and the public response are distinct parts of this story.

TOML is a text format for configuration files. Its website provides specifications in several languages. On October 23, 2026, doggy8088 (Will, whose Facebook page is named Will 保哥的技術交流中心) proposed a Taiwanese Traditional Chinese locale and submitted a homepage, two specification versions and interface changes. TOML website ↗ Read the proposal

Project member arp242 characterized the first issue as an LLM prompt and objected to agent-mediated submissions. The issue and PR were closed. The contributor disclosed AI assistance, said he reviewed the work and accepted responsibility, and asked for assessment of the result. Two days later, a renewed issue was closed and locked after the maintainer linked Facebook. First rejection · The renewed closure

Responses do not form a single camp: some emphasize human review and cultural differences, some criticize the submission or publicity strategy, and others also ask maintainers for better feedback. This chronicle paraphrases each statement and distinguishes participant claims from facts the record can establish.

Three layers to assess separately

Demand

Traditional Chinese localization

Characters, Taiwanese technical terms and reading habits: whose needs support another locale?

Result

Translation and code

Is the prose accurate? Are shared templates correct? What review evidence can others verify?

Collaboration

Rules, effort and trust

Which methods are welcome? How is rejection explained? How does public discussion affect trust?

People in the record

doggy8088

Issue and PR author; publicly discloses AI assistance and accepts responsibility.

arp242

Shown as a project member on GitHub; closes threads and explains his position.

ShikiSuen · d4n1elchen · ddman

Discuss localization, human review and the rejection’s handling.

brlin-tw · pcchou

Describe localization or community experience and differ on publicity and handling.

Copilot

An automated reviewer; the concrete finding concerns interface language tags.

Who is arp242? Maintenance work and earlier positions

A developer with a long record in Go and technical communities

arp242 publicly identifies as Martin Tournoij; his GitHub profile and personal website link to each other. His public CV describes him as the founder of GoatCounter, an open-source web analytics service focused on privacy and ease of use. NLnet separately records funding for the project between 2019 and 2022. GitHub profile ↗ · His CV ↗ · NLnet funding record ↗

His public work also includes the Unicode lookup tool uni, the Go plugin gopher.vim and maintenance activity on Go libraries including fsnotify and lib/pq. His 2019 resignation post records that he served as a moderator on Vi and Vim Stack Exchange. His project list ↗ · Moderator resignation ↗

Visible work in TOML

arp242 published the TOML 1.1.0 GitHub release, merged the Simplified Chinese and French 1.1.0 translations on toml.io and proposed a CODEOWNERS file to identify translation reviewers. That proposal remained unmerged when checked. These actions establish a maintenance role, but the public record alone does not show whether other members were consulted about the present decision. GitHub release ↗ · Chinese #92 ↗ · French #96 ↗ · Reviewer proposal #89 ↗

His AI contribution policies in other projects

The written bans below are published in other repositories. In toml-lang/toml.io, the repository involved in this dispute, the PR-base README contained no AI-use restriction. In the event discussions, arp242 explicitly asked contributors not to use agents to submit issues or PRs and called for carefully vetted human translations. toml.io README at the time ↗ · Submission restriction in #97 ↗ · Translation requirement in #99 ↗

On August 19, 2026, Taiwan time, he added AI contribution policies to BurntSushi/toml, lib/pq and GoatCounter. They prohibit AI-generated PRs, issues, commit messages and comments. The restrictions cover several forms of contribution text; they cannot be reduced to a ban only on drafts lacking human review. Fixed BurntSushi/toml policy ↗ · Fixed lib/pq policy ↗ · Fixed GoatCounter policy ↗

That day, he described roughly 110 agent reports and a large PR on lib/pq as difficult to review; the count and attribution are his account. The Go vulnerability database’s rolandshoemaker subsequently acknowledged that some reports had slipped through review, said they had been withdrawn and apologized. arp242 also said some issues could still be fixed. This gives context for his discussion of maintenance workload without establishing that all reports were fabricated. His account of review workload ↗ · Withdrawal and apology ↗ · His reply on possible fixes ↗

The fsnotify dispute over maintenance access

In May 2026, removing some collaborators’ access to fsnotify prompted public discussion. arp242 cited rapidly merged changes, inadequate quality and an undiscussed funding-list change. mattn listed fixes and releases, disputed the wholesale dismissal of his work and apologized for incorrectly describing the original maintainers as recently removed and for his judgment in directly changing the funding file. arp242 also acknowledged that he should have opened an issue beforehand. Quality and governance remained disputed; this provides context about maintenance procedures, not proof of his motive in rejecting the translation. arp242’s explanation ↗ · mattn’s full response ↗ · arp242 on prior communication ↗

Earlier views and the acceptance criteria still unresolved

In “Open source DIY ethics,” he describes open source as working together to solve problems and expects users to share the work. In “Tired of Stack Overflow,” he criticizes harsh treatment of newcomers and argues that quality and kindness can coexist. These are his earlier published views, not established explanations for his present replies. Open source DIY essay ↗ · Stack Overflow essay ↗

The PR-base README provides translation steps but contains no AI clause. Policies in other projects do not automatically establish a previously announced toml.io rule. In the Russian discussion, pradyunsg described a practice of finding another native speaker to review. In #99, arp242 said he did not oppose Traditional Chinese, yet also said subsequent zh-TW submissions would be suspected of AI translation. Whether human checking and independent native-speaker review offer an acceptable path remains unanswered in the public record. Translation guide at the time ↗ · Native-speaker review practice ↗ · His full position in this dispute

Background checked on October 27, 2026, Taiwan time. CV details remain attributed to him. This research did not contact participants or recapture all event comments. The background is separate from the counts of 144 records and 28 timeline entries. Source scope and method

R

Keep the context.
Give judgments a record to stand on.

Back to top ↑