R Open Source RecordTHE TOML CHRONICLE
繁體中文Captured 27 Oct 2026
The TOML chronicle

All records and search

Chapters +

Reading settings

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

03 / THE RECORD

Every statement,
in its context.

English editorial paraphrases, organized by GitHub thread and Facebook post. Original names, source IDs, timestamps and links are retained. These are not verbatim translations of all original posts.

  1. A proposal for a Traditional Chinese locale doggy8088 ·

    Taiwanese terminology motivates a proposal covering translation, language tags and the website interface.

  2. The PR changes shared templates as well as translations doggy8088 ·

    PR #98 was opened 24 seconds after the issue and changed eight files.

  3. A maintainer characterizes the issue as an LLM prompt arp242 ·

    arp242 rejects agent-mediated submissions and closes the issue in the same second.

  4. The contributor discloses AI assistance and asks for review of the result doggy8088 ·

    He offers accountability and a smaller scope, while asking what standard led to rejection.

  5. A second response on tools, responsibility and review burden doggy8088 ·

    He cites a Linux mailing-list discussion and again offers to reduce the scope.

  6. ShikiSuen distinguishes localization from code contributions ShikiSuen ·

    He questions rejection based on AI use and later edits the comment to explain withdrawing another response.

  7. d4n1elchen emphasizes the work involved in human review d4n1elchen ·

    He rejects equating machine translation with an absence of quality control.

  8. brlin-tw criticizes both the submission and its rejection brlin-tw ·

    Speaking personally, he calls for observing conventions, actionable feedback and de-escalation.

  9. pcchou asks for a fairer assessment of public discussion pcchou ·

    He supports d4n1elchen’s analysis and sees possible benefits in greater awareness of localization.

  10. A shorter renewed proposal asks whether a contribution is welcome doggy8088 ·

    #99 starts with personal reading experience and offers a smaller initial scope.

  11. ddman: localization involves culture and everyday terminology ddman ·

    The first reply supports Traditional Chinese in both English and Chinese.

  12. A maintainer links Facebook and directly confronts the contributor arp242 ·

    The reply and closure of #99 occur in the same second; the thread is locked ten seconds later.

  13. The maintainer accepts the locale in principle but rejects the contribution method arp242 ·

    He separates language from submission method while using disparaging terms about the contributor and supporters.

  14. Copilot review summary: language tags on English fallback labels copilot-pull-request-reviewer[bot] ·

    The automated review raises one accessibility issue and lists eight changed files.

  15. Inline review: page language and interface-string language can differ Copilot ·

    The issue concerns English fallbacks in non-English locales, including mobile and language menus.

  16. The contributor reports a fix; the commit exists but is absent from the PR doggy8088 ·

    The fix follows the original commit, while the captured PR still lists only the original version.

  17. The renewed issue is closed too 高立宣 ·

    高立宣 reports that the renewed issue has also been closed, adding an emoticon.

  18. The author says he cannot understand the outcome Will 保哥的技術交流中心 ·

    Replying to 高立宣, the author says he really cannot understand the result. This brief response expresses continued puzzlement about closure without new technical or review evidence.

  19. Comparing the maintainer’s attitude with terminology disputes in Taiwan Tomady Tang ·

    Tomady Tang criticizes the maintainer’s manner as extreme and compares it with policing mainland Chinese vocabulary in Taiwan, arguing that communication should focus on the topic. He likens the project to the maintainer’s kingdom and criticizes decisions based on personal preferences. These are the commenter’s analogies and assessments.

  20. Criticizing the publicity strategy and fearing consequences for zh-TW 王韋傑 ·

    王韋傑 reminds the author that the maintainer has read Facebook. Contributors should follow project guidelines and carefully read the long reply, he argues. He worries that the entire zh-TW locale will acquire a label. This is criticism of the author’s handling, rather than simple support.

  21. Suggesting Chinese submissions that readers can translate themselves 熊國仁 ·

    熊國仁 asks whether submissions could simply be written in Traditional Chinese, leaving anyone who wants to understand them to use AI translation. The suggestion turns the translation-tool argument back on the other party.

  22. The author speculates that he may have been blocked Will 保哥的技術交流中心 ·

    The author invites 熊國仁 to try and says he has probably been blocked. His wording is uncertain; it is not a verified record of a block.

  23. Suggesting a challenge about racism 鄒錦翔 ·

    鄒錦翔 suggests asking whether the other party is racist if another rejection occurs. This proposed response does not establish discrimination or show that the author used the strategy.

  24. The author says the issue is closed and some people cannot change Will 保哥的技術交流中心 ·

    Replying to 鄒錦翔, the author says the issue has closed and some people cannot change. He does not explicitly agree to use the preceding suggestion of challenging the other party about racism.

  25. A sarcastic “generated by a human” signature Liāu Pik-Hān ·

    Liāu Pik-Hān says he would be tempted to sign the work as generated by a named human, mocking the argument about generation tools. This is sarcasm, not a new translation-quality check.

  26. An analogy with a conservative craft workshop Chang Alex ·

    Chang Alex compares the attitude toward new tools with a conservative workshop still insisting on handcraft after the Industrial Revolution.

  27. A brief negative judgment about the interaction Liu YuTang ·

    Liu YuTang describes the behavior as unreasonable. The short comment does not develop an argument.

  28. Questioning why zh-CN appears in a Traditional Chinese PR Logos ·

    Logos asks the author to check the code and questions why zh-CN appears in a contribution presented as Traditional Chinese. He attaches a formatter.js diff. The screenshot also shows cn mapped to zh-CN and tw to zh-TW; the mere presence of zh-CN does not establish that the Traditional Chinese translation was put in the wrong locale.

  29. The author explains that the tags support language switching Will 保哥的技術交流中心 ·

    Replying to Logos, the author says these are language tags used to switch languages. The original PR retains mappings for both cn and tw, so this explanation can be compared with the code.

  30. Mocking the questioner’s understanding of the code 婉晴吳 ·

    After the author’s explanation, 婉晴吳 questions whether Logos can read the code and points to the tag already present. This is a reply to the author’s reply, rather than a separate top-level comment.

  31. A disparaging reply to Logos Lxs Artmily ·

    Lxs Artmily leaves a disparaging remark suggesting Logos is exposing his own shortcomings, without further code analysis.

  32. Questioning the basis for “AI slop” while noting shared-code changes 李政旻 ·

    李政旻 asks how the maintainer judged the contribution poor and how someone unable to read Chinese could assess the translation. Having looked at the diff, he finds most of it normal apart from unusual template and JavaScript changes. This is his inspection impression, not a full language review.

  33. Speculating about reactions to rapid AI translation and Facebook Tomex Ou ·

    Tomex Ou suggests subjective factors: a rapid, enthusiastic submission, previous impressions of fast AI translation and Facebook comments may have increased the maintainer’s anger. These are the commenter’s explanations of motives, not a psychological state confirmed by the maintainer.

  34. Seeing generated-writing signals in the PR description’s length 林博仁 ·

    林博仁 links the description of #98 and argues that an ordinary contributor would not write so many paragraphs merely to add a display language. His point concerns submission style, rather than identifying errors paragraph by paragraph in the Traditional Chinese translation.

  35. The author links his separately published Traditional Chinese site Will 保哥的技術交流中心 ·

    The author provides a link to his Traditional Chinese TOML website. It is a public entry point to his separately published translation, not evidence that upstream toml.io accepted or merged this PR.

  36. Distinguishing the tool debate from integrity Yu-Fen Ceng ·

    Yu-Fen Ceng says the reasons for requiring human translation could have been discussed directly in the PR. She instead criticizes asking AI to sound human and then taking the dispute to the page’s audience, characterizing these choices as deception and public shaming. She cites the maintainer’s conclusion that apparent tolerance of lying makes Traditional Chinese translations suspect, insists that tool use and integrity are separate issues, and states that some people do care about integrity.

  37. Starting with maintenance costs and choosing to accommodate maintainers 吳立志 ·

    吳立志 argues that maintainers bear the actual costs and that a contributor cannot take responsibility for the wider problems caused by AI. He acknowledges a conflict but says he would choose to accommodate the maintainer’s position.

  38. Connecting the maintainer’s anger with the previous post’s tone 觀月唯 ·

    觀月唯 says the wording of the author’s previous Facebook post explains why the maintainer would be upset. This assesses tone and reaction rather than independently establishing the maintainer’s actual state of mind.

  39. Participation means accepting a project’s tool restrictions Jack Aior ·

    Jack Aior says some projects do not accept AI-generated results and that people wishing to participate must accept that requirement. This is a general contribution principle; he supplies no written policy source for this case.

  40. Citing Forgejo’s position on AI submissions 阮仕輔 ·

    阮仕輔 cites Forgejo, saying its community opposes AI and that even AI-written issues violate its rules because of maintenance burdens. This is the commenter’s description of another project without a policy link. This chronicle has not used it to declare Forgejo’s current rules or TOML’s adopted policy.

  41. Alleging broken support for existing locales Chun Yu Chen ·

    Chun Yu Chen alleges that the PR breaks existing language support in several places, says these should be fixed and uses that to explain rejection. The independently comparable technical finding here is Copilot’s English-fallback language-tag issue. No full regression test of every locale has been performed, so the wider allegation is not treated as wholly verified.

  42. Responding to the author’s anger with emojis 張振豪 ·

    張振豪 says the author is angry, adding several laughing emojis, without new technical, review or policy evidence.

  43. Finding human and AI writing harder to distinguish Shengan Lee ·

    Shengan Lee remarks that human writing is increasingly mistaken for AI while AI writing may be mistaken for human work. This general observation provides no verification of authorship or generation proportions in this case.

  44. Explaining open-source caution through low-quality code 陳冠霖 ·

    陳冠霖 argues that many open-source projects have been traumatized by poor-quality code. He proposes a community background without examples establishing that it was the actual reason for this rejection.

  45. A brush-writing analogy mocking tool restrictions 吳政達 ·

    吳政達 suggests asking the other party to start writing with a traditional brush before imposing tool requirements on others. This sarcastic analogy does not show that the author actually gave that response.

  46. Sharing a personal experience of rejected Chinese translation 朱家儀 ·

    朱家儀 says she spent considerable time translating for a foreign open-source language project that welcomed contributions, only to be told Chinese was not mainstream or important and have her PR quickly closed. No project or PR link is given, so this is recorded as her experience rather than assumed to be the TOML incident.

  47. Predicting different futures for projects that support or oppose AI Eric Theng ·

    Eric Theng predicts a divide between AI-supporting and AI-opposing camps. He expects supporters to iterate and improve rapidly and gain users, while opponents fix bugs slowly, lose users and eventually become dead projects. This prediction does not establish the quality, activity or future of this project.

  48. A Taiwanese-language criticism of language barriers and broader changes 楊孟諺 ·

    Writing in Taiwanese, 楊孟諺 says concern about unfamiliar-language content is natural and that this PR adds more than translation, making suspicion understandable. He also criticizes the author’s continued insistence on AI. The author later supplies a Mandarin rendering.

  49. Approving the term meat proxy ChihKang Lin ·

    ChihKang Lin says he has learned the term meat proxy, interprets it as a carrier of AI output and praises its aptness. Approval of a label is not an independent investigation of the author’s workflow.

  50. Favoring doing it yourself and reporting confirmed bugs Wai Tang ·

    Wai Tang supports doing the work oneself when dissatisfied and otherwise having little to say. Bugs should first be confirmed and then proactively reported. The original is brief; this chronicle does not extend it into approval of all behavior by either side.

  51. A brief suggestion to ignore the other party Low Man Woei ·

    Low Man Woei briefly advises ignoring the other party, without reasons or new information about the incident.

  52. Responding with a distinction between Taiwan and China Liu YuTang ·

    With a laughing tone, Liu YuTang says this is the time to emphasize that Taiwan is not China. The commenter’s political or regional distinction cannot establish the maintainer’s understanding of those places or motives for rejection.

  53. Reading the incident as an example of opposition to AI 莊念迪 ·

    莊念迪 says he had only heard about anti-AI attitudes before but now has seen them firsthand. This is his characterization and reaction, without evidence beyond the underlying discussion.

  54. Suggesting several Taiwanese readers comment to attest to readability Brune Kz ·

    Brune Kz suggests that more Taiwanese people comment to say that native speakers can understand the translation and get started easily. This verifiable invitation to comment belongs in the context of public amplification. It is this commenter’s suggestion, not proof that the author initiated or coordinated collective action or that anyone followed it.

  55. Questioning how the maintainer identified AI translation 王哲驊 ·

    王哲驊 asks how the maintainer can distinguish AI translation. He suspects the PR may have been read but that judgment was made without reading the entire translation. This speculation cannot establish how much the maintainer inspected.

  56. Speculating with political labels and possible regional misidentification 周正泰 ·

    周正泰 uses the disparaging political label “white left” and asks whether the maintainer mistook the author for someone from mainland China. These political and regional speculations lack direct evidence and are not verified motives.

  57. Replying with another political generalization 林昱廷 ·

    林昱廷 replies to 周正泰 with a generalization that people labeled “white left” tend to like China. The political label is recorded without treating this generalization as fact or as evidence of the maintainer’s own position.

  58. Generalizing about the number of anti-AI people 黃光希 ·

    黃光希 uses a derogatory term for people opposed to AI and says there are many of them now. This is an emotional group label, without new evidence relevant to the case.

  59. Describing personal complaints about rules and security 梁智峰 ·

    梁智峰 describes being accused of rule violations, backing up documents, complaining to Google about security and seeking compensation. He says the incident harmed his wellbeing and development work. No supporting documents or concrete link to TOML are provided; the serious allegations remain his account.

  60. Offering sympathy and good wishes Duke Hsu ·

    Duke Hsu recognizes the author’s effort and wishes him better luck, without a technical or policy argument.

  61. Recommending the maintainer’s reply and other readers’ advice 溫開水 ·

    溫開水 recommends reading arp’s reply and other readers’ advice, linking 王韋傑’s comment on another post. The attachment shows the Facebook-linked confrontation in #99, closure and locking, and the long reply on human translation and zh-TW. It connects a public reminder with actual GitHub wording.

  62. Rendering the long reply from the locked issue in Chinese 朱立恆 ·

    Replying under 溫開水, 朱立恆 says the long text turns out to be the reply in #99, gives its permalink and renders the passages on mechanical translation, human review and suspicion of zh-TW into Traditional Chinese. The attachment is another Chinese presentation of the same reply.

  63. Attachment 1: interface-label dictionaries and language-code mappings Chun Yu Chen ·

    Chun Yu Chen posts a code diff without additional written argument. It shows English and zh-TW interface labels, cn mapped to zh-CN and tw mapped to zh-TW. The presence of zh-CN alone does not mean Traditional Chinese is mislabeled, and the image cannot establish runtime behavior for every locale.

  64. Sharing a social-media repost about Linus Baozi Xi ·

    Baozi Xi says Linus recently discussed a related issue and links an X post by Hesamation. This comment does not elaborate on the original content. The link is retained without independently checking the repost’s full original context or declaring Linus’s position on this TOML dispute.

  65. Paraphrasing Linus on people who reject AI 陳存善 ·

    陳存善 says Linus stated that people who do not accept AI can fork or leave. No original source is provided. This is recorded as the commenter’s paraphrase, not a verified quotation or policy binding on TOML.

  66. Attachment 2: language and label changes in navigation Chun Yu Chen ·

    Chun Yu Chen posts another navigation-template diff without further text. It shows a lang attribute added to the header and fixed labels such as Full spec and Language replaced with variables. This establishes changes to shared templates, not a complete functional test.

  67. Attachment 3: specification container and menu-label changes Chun Yu Chen ·

    Chun Yu Chen posts a specification-template diff without written explanation. It shows lang added to the specification container and the fixed Menu label replaced by menuLabel, documenting shared-code changes beyond translated prose.

  68. Asking for respect for the website maintainer Chun Yu Chen ·

    In a separate short comment, Chun Yu Chen emphasizes that it is the other party’s website and asks for respect. This is retained separately from his comments on code changes, rather than merged into one technical judgment.

  69. Citing Copilot’s advice on English fallback labels Chun Yu Chen ·

    Chun Yu Chen says Copilot has already supplied a reason and attaches the review summary. The image concerns English fallback UI text inheriting a non-English lang attribute, potentially affecting screen-reader pronunciation. It matches the technical issue checked in this chronicle.

  70. Attachment 4: brlin-tw’s criticism and call to de-escalate Chun Yu Chen ·

    In a separate image-only comment, Chun Yu Chen reposts brlin-tw’s long response without adding text. The screenshot criticizes the submission method, lengthy PR description and move to Facebook, while also asking arp242 for actionable feedback, crediting the intention to contribute and urging de-escalation. It discloses LLM proofreading.

  71. Criticizing an echo chamber and equating disagreement with anti-AI views Pin-Han Huang ·

    In Yu-Fen Ceng’s thread, Pin-Han Huang sees an echo chamber where lack of support is easily branded anti-AI, turning an engineering issue into something like political conflict. He argues that many open-source projects accept AI assistance and oppose work that increases costs. No statistics support that generalization about most projects.

  72. The author accepts criticism and acknowledges insufficient consideration Will 保哥的技術交流中心 ·

    The author directly replies to Yu-Fen Ceng, accepts the criticism, acknowledges that he did not think things through, thanks her and says he will be more careful in his words and actions. This is a clear concession and conciliatory response. He does not itemize which accusations of deception, public shaming or mobilization he accepts, or say he will stop using AI.

  73. The author again asks for explicit contribution guidelines Will 保哥的技術交流中心 ·

    In 吳立志’s thread, the author says his issue made clear that he would follow contribution guidelines if supplied. He believes the requirements were not written down, yet only human translation was later accepted. He notes that the second submission was an issue rather than a new PR and expresses puzzlement that it was still closed.

  74. Connecting the GitHub profile with the Vibe Coder label 王藤諺 ·

    王藤諺 alleges that the author’s entire GitHub profile is AI-generated and would therefore make arp242 see him as a Vibe Coder. This claim about the profile and another person’s perception supplies no complete generation-history evidence. It cannot establish that all previous work or this translation was generated by AI.

  75. Deriving decision rights from responsibility 吳立志 ·

    In a reply mentioning 孫志貴, 吳立志 argues that responsibility gives the maintainer corresponding decision rights. Unless one can solve the maintainer’s problem, making a decision for him is intrusive. The platform also says the comment being replied to was deleted, preventing recovery of the full preceding exchange.

  76. Asking whether a profile label justifies discriminatory treatment 孫志貴 ·

    孫志貴 mentions 王藤諺 and asks whether that would justify such discriminatory treatment. He questions the move from an impression of a profile to how someone is treated. Calling the treatment discrimination remains his assessment.

  77. Acknowledging a misread username and a correction 孫志貴 ·

    Mentioning 郭超望, 孫志貴 admits misreading arp’s username and says he has corrected it. This correction of a name does not show withdrawal of all his views about policy and decision-making.

  78. Calling for an AI policy agreed by the maintenance team 孫志貴 ·

    孫志貴 says the repository does not belong to arp242 alone and that he has tagged other maintainers to discuss it. He criticizes suspicion toward all future zh-Hant-TW localization PRs and asks for a collectively agreed AI policy rather than decisions by one member.

  79. Pointing out arp being written as alp 郭超望 ·

    郭超望 asks why someone keeps writing alp when the person’s username is arp. This is a correction of a name, not a new translation-quality judgment.

  80. The author continues to prioritize results over tools Will 保哥的技術交流中心 ·

    Replying to Pin-Han Huang, the author says this is his first such experience and that most projects do not object to tools as long as results have quality. He focuses on what can be achieved rather than which tool is used. This view of tools and outcomes should be read separately from his later acceptance of Yu-Fen Ceng’s criticism of his handling.

  81. Explaining rejection through low-quality output overwhelming review Pin-Han Huang ·

    Pin-Han Huang offers a possible bad-money-drives-out-good explanation: low-quality output can overwhelm review and lead to outright rejection. He compares academic journals and the difficulty of distinguishing AI-assisted work from pure Vibe output. These possibilities and analogies do not establish the maintainer’s complete actual motives.

  82. The author refers to unspecified well-known examples Will 保哥的技術交流中心 ·

    Replying to 陳冠霖, the author briefly says it is really just those few well-known cases. He does not identify projects or people; this chronicle does not supply names on his behalf.

  83. The author renders the Taiwanese criticism into Mandarin Will 保哥的技術交流中心 ·

    Replying to 楊孟諺, the author explicitly supplies a translation into Mandarin of the criticism about language barriers, changes beyond translation and insistence on AI. He adds no separate rebuttal in this comment. Posting a translation does not establish complete agreement with the criticism.

  84. Citing suspicion toward future zh-TW work and doubting contribution prospects Qazplo Yao ·

    Replying to Brune Kz, Qazplo Yao quotes the maintainer’s English wording extending suspicion to future zh-TW translations and doubts that Traditional Chinese contributions remain possible. The passage actually comes from the long comment in #99, not a new PR ruling. Predicting that every future contribution is impossible goes beyond closure of this case.

  85. Emphasizing that the changes go beyond i18n 楊孟諺 ·

    Under Chun Yu Chen’s template diff, 楊孟諺 says in Taiwanese that the issue indeed goes beyond i18n. This is a brief assessment of scope, without independent test results.

  86. Questioning whether public discussion amounts to public shaming 江柏漢 ·

    江柏漢 says he has long read the author’s technical articles, then questions publishing a dispute after a rejected PR, seeing an element of public shaming. He argues that joining a project means following its rules and considering maintainers’ feelings, while also affirming the value of a willingness to contribute.

  87. Suggesting a brief agreement to end an argument 宮屏惠 ·

    宮屏惠 suggests responding in English that the other party is right. She does not elaborate on the PR or translation quality.

  88. Recognizing years of sharing and community work Roga Lin ·

    Roga Lin praises the author’s sustained sharing of knowledge and community work over many years, saying that readers including himself have quietly supported him.

  89. Focusing on understanding and checking AI output Watson Chen ·

    Watson Chen argues that AI use alone should not disqualify work if the person understands and checks the output. His criticism targets generation without quality control. This is a view about responsibility, not a review of this translation.

  90. Connecting the post’s advice with personal difficulties 劉育維 ·

    劉育維 says recent problems have troubled him and that the post’s advice about trusting one’s efforts and not needing to persuade everyone helped him find some answers. He expresses mutual encouragement.

  91. Joking about course sales Tonny Chiu ·

    Tonny Chiu jokes that the author already has ample sales, echoing the post’s suggestion that readers need not add more encouragement.

  92. Mentioning a fork as an option when people disagree Locutus Cardassia ·

    Locutus Cardassia jokingly notes that a common open-source option is to fork when people disagree. This proposes a way to continue work, rather than claiming a new project has been established here.

  93. Using vulgar language to criticize mockers 陳大衛 ·

    陳大衛 uses vulgar language to generalize about people he sees as seeking amusement at others’ expense and speculates about their lives or mental state. He says good deeds do not require approval and jokes that his own barbs can serve as reminders. His generalizations about others’ circumstances are unsupported assessments.

  94. Supporting the protection of personal enthusiasm 大魔術熊貓工程師 ·

    大魔術熊貓工程師 agrees with attending to one’s feelings and sees leaving negative interactions when necessary as a way to protect enthusiasm for open source.

  95. The author admits not expecting the maintainer to see Facebook Will 保哥的技術交流中心 ·

    Responding to 江柏漢, the author accepts that this was his problem. He says he would not have written in the same way if the other party spoke Chinese, and wrote more freely because he did not expect the Facebook post to be read. He still sees room for discussion and asks whether he should simply keep the peace. This account of his expectations and choices does not independently establish every allegation about mobilization or intent.

  96. Characterizing the post as venting about an experience Lxs Artmily ·

    Lxs Artmily disagrees with calling it public shaming and sees the author as publicly venting about something that happened to him.

  97. Opposing an automatic label of public shaming 王哲驊 ·

    王哲驊 argues that raising a discussion should be allowed. Provided it is not fabricated, merely describing what happened should not automatically be called public shaming. He objects to using that label to restrict public expression.

  98. Allowing both public discussion and maintainer discretion Sam Lin ·

    Sam Lin refers to a statement by Linus and argues that people may discuss public projects in their own spaces; interactions also have a public dimension when maintainers accept others’ contributions. He simultaneously acknowledges maintainer discretion. No link to the referenced Linus post is provided, so it is not equated with the mailing-list message checked elsewhere in this chronicle.

  99. Calling rejected PRs a normal part of open source 江柏漢 ·

    Replying to the author, 江柏漢 says rejected PRs are an ordinary part of open source, with nothing exceptional about that outcome.

  100. Affirming the intention to contribute and encouraging continued work 江柏漢 ·

    江柏漢 adds that people’s willingness to help is an important community asset and hopes the author will continue supporting the community and software industry.

  101. The author says the surprise was being called AI slop Will 保哥的技術交流中心 ·

    The author says he was polite on GitHub, did not intend to argue and has had many PRs rejected before. Being called AI slop for the first time was the surprise. He describes the Facebook post as venting, says he did not intend an escalation and again says he did not expect the maintainer to read it. These remain his descriptions of intent and tone.

  102. Locating the complaint in the tone of rejection Lxs Artmily ·

    Lxs Artmily sees the original issue as whether to accept AI translation but criticizes the maintainer’s impolite wording. In vulgar, joking language, he considers that sufficient reason to vent publicly.

  103. Recommending human editing of generated interactions 林博仁 ·

    林博仁 argues against directly using AI tools to interact with maintainers unless a project explicitly permits it. He sees generated signals in the issue and PR descriptions, rather than the diff, as the trigger, potentially giving the impression of a human proxy mass-submitting low-quality agent output. Even if files are created automatically, he recommends removing unnecessary explanation, observing interaction conventions and possibly documenting them as a skill. His account of the maintainer’s perception is an interpretation.

  104. Requesting an advance policy and criticizing the rejection’s tone Daniel Chen ·

    Daniel Chen argues that maintainers also have responsibilities: with AI assistance common, a strong objection should be communicated beforehand. He acknowledges generated-writing signals but personally finds the motivation and changes clear and fairly concise, apart from the questionable explanation for missing screenshots. He also criticizes the lack of a reply to the contributor’s explanation, followed by harsher wording elsewhere. This differs from 林博仁’s assessment of the same description.

  105. Emphasizing the right to reject and respect for stated requirements Frank Sung ·

    Frank Sung argues that responsibility for decisions includes a maintainer’s right to reject in any tone. He frames the issue as respect and criticizes using AI again to rewrite text as one’s own after being told no AI. His accusations of pretending and his judgments about attitude are not independently verified facts.

  106. Acknowledging the right to reject while asking for fuller context Daniel Chen ·

    Replying to Frank Sung, Daniel Chen says he never denied the maintainer’s right to reject, believes Frank has not fully understood the events and asks him to learn the context first. This makes the distinction between the right to reject and how rejection is communicated more explicit.

  107. Agreeing with the brief-response strategy Keio Kwan ·

    Keio Kwan replies to 宮屏惠 with complete agreement and a one-hundred-percent emoji.

  108. Quoting a classical saying about perseverance 許友財 ·

    許友財 quotes a classical saying to express determination after self-reflection. No additional event or technical evidence is offered.

  109. A Buddhist image of steadiness amid outside judgment Anderson A. Thomas ·

    Anderson A. Thomas locates the problem in people’s prejudice toward tools. He uses the Buddhist image of remaining unmoved by the eight winds to describe resilience to judgment, and likens the original motivation for open source to a lamp illuminating the path. These are metaphors and value judgments.

  110. A reader from Macau thanks the author Bevis Leong ·

    Bevis Leong identifies himself as a reader from Macau and thanks the author for sharing over the years, saying he has benefited greatly.

  111. Expressing support through a recent class experience Sheng Lee ·

    Sheng Lee expresses continued support and says he learned a great deal in a recent class. This is a personal account.

  112. Distinguishing a sound action from the way it is presented Yang Yung Ling ·

    Yang Yung Ling distinguishes doing the right thing from adopting the right manner and says events have causes. The brief comment does not specify a particular action or assign responsibility to one side.

  113. Hoping for future articles about Linux 陳嘉慶 ·

    陳嘉慶 builds on the author’s macOS experience and hopes he will try Linux and share his experience. This is a related exchange, not a review of the PR.

  114. Recalling learning about development tools through the author’s teaching 柯盛達 ·

    柯盛達 thanks the author’s teaching and sharing. He recalls searching for VS Code settings, discovering Copilot through the author’s GitHub teaching, and later using Claude and Codex. Although he has seen fewer articles recently, he remains grateful for that help.

  115. Saying course enrollment is a form of support 陳盛晃 ·

    陳盛晃 says he enrolled in every class as a form of paid support. This chronicle has not checked enrollment or transaction records.

  116. Comparing published work with a family heirloom Richard Lee ·

    Richard Lee suggests treating the work as an heirloom for later generations and worrying less about others’ opinions. This prompts a joking exchange about whether the next generation will appreciate it.

  117. Prioritizing personal enjoyment Horst Kan ·

    Horst Kan says enjoying the work oneself is enough and that other people’s opinions need not weigh too heavily.

  118. Taking useful criticism while treating the rest as noise 賴禹翰 ·

    賴禹翰 recommends returning to the original enjoyment of the work and accepting that some will need it and others will dislike it. Suggestions for improvement can be taken from negative comments; the rest need not be internalized. He also thanks the author for public resources.

  119. Sharing experience of PRs left unanswered 莊念迪 ·

    莊念迪 says some of his PRs received no maintainer response while most were merged, adding a personal example of differing open-source outcomes.

  120. Seeing shortcomings in old work as evidence of growth 張小白 ·

    張小白 says technology changes quickly and he often dislikes his earlier work. Being able to recognize its shortcomings now, he suggests, reflects personal progress.

  121. Encouragement to keep going 魏吉彥 ·

    魏吉彥 offers encouragement and urges the author to continue, without developing an argument about the incident.

  122. Learning new information from the author’s posts Tang Jung Kui ·

    Tang Jung Kui says the author’s sharing introduced him to much new information.

  123. Praising openness and sustained contributions Eric Chang ·

    Eric Chang expresses respect for the author’s openness in this post and his sustained sharing.

  124. A brief thank-you for the contributions 林雨蒼 ·

    林雨蒼 thanks the author for his contributions without further comment on this PR.

  125. A brief “come on” remark with unclear tone Lo Miller ·

    Lo Miller leaves a short phrase that could be rendered as “come on, okay?” The comment offers no further context; this chronicle does not decide whether it is encouragement or sarcasm.

  126. Encouraging persistence in what one believes is right Jun-Yuan Yan ·

    Jun-Yuan Yan encourages continuing to do what one believes is right, with an encouraging emoji.

  127. Crediting development experience with better use of AI Kavin Wang ·

    Kavin Wang questions the insistence on rejection and argues that the author’s development experience makes his use of AI different from that of an average user. Praise of personal ability does not substitute for checking this translation paragraph by paragraph.

  128. Asking about a live class 張振豪 ·

    張振豪 asks whether the author might offer a live class, prompting the subsequent course-information reply.

  129. Recalling helpful solutions as a beginner 陳永富 ·

    陳永富 says he sought the author’s solutions when starting out and benefited from them.

  130. Responding with a cartoon GIF containing “good” Ryan Pan ·

    Ryan Pan attaches an animated cartoon containing the word good, without a written argument about the incident. The GIF was inspected; the image alone does not establish his position on every disputed point.

  131. Recommending time for worthwhile things 楊禮峰 ·

    楊禮峰 suggests spending life on worthwhile things and letting an unpleasant incident pass rather than allowing it to occupy one’s thoughts indefinitely.

  132. Criticizing both a sweeping rejection and a mixed-scope PR Jacey Taavi ·

    Jacey Taavi finds the rejection too sweeping while also seeing unnecessary material in the PR. He recommends using the author’s experience to tidy it before resubmitting and links the diff. He does not simply endorse one side or list every change he considers unnecessary.

  133. Questioning the other party’s ability to recognize AI writing 巴農索 ·

    巴農索 negatively judges the other party as so preoccupied with AI that human expression becomes unrecognizable. This is an assessment, not a verified ability or psychological condition.

  134. Comparing the reaction with insults dating back to BBS culture 李奎翰 ·

    李奎翰 says online insults existed in the BBS era and are more common now, generalizing about younger people dismissing things they have not experienced. He extends the point with a joke about someone denying BBS existed, without offering a review of this translation.

  135. A disparaging remark aimed at critics Albert Chang ·

    Albert Chang disparagingly suggests that the critic plainly did not grow up reading the author’s articles. This is a short judgment directed at critics.

  136. Finding the articles useful C-j Kang ·

    C-j Kang thanks the author for sharing and says the articles are useful to him.

  137. Saying people already know the author 黃仁靖 ·

    黃仁靖 briefly says that everyone knows the author, without specifying a position on the incident.

  138. Valuing explanations in plain language 王品傑 ·

    王品傑 praises the author for making the same material easier to understand and reducing the burden of learning. He sees plain-language teaching as an important part of the author’s value.

  139. Valuing the willingness to share Kai-hsiang Wang ·

    Kai-hsiang Wang says the willingness to share is itself worthy of appreciation.

  140. An analogy with good gaming performance being mistaken for cheating John Yeung ·

    John Yeung recalls being accused of cheating in shooting games when his reactions were fast, comparing that with the author being accused of using AI because of his ability. This is the commenter’s analogy: the author publicly acknowledged AI assistance, so it cannot support rewriting the case as involving no AI use.

  141. The author jokes that descendants may not appreciate his work Will 保哥的技術交流中心 ·

    Replying to the heirloom metaphor, the author jokes self-deprecatingly that the next generation may not appreciate what he leaves behind. This does not establish what actual family members will think in the future.

  142. Leaving the next generation’s opinion to that generation Richard Lee ·

    Richard Lee replies that the next generation can decide its own opinion; the present generation can first find satisfaction in its work.

  143. The author supplies information about a live class Will 保哥的技術交流中心 ·

    Replying to 張振豪, the author says a class will take place that Friday and includes a course link and promotional image. This records a historical exchange, not a guarantee of current availability or an enrollment recommendation.

  144. Again separating rejection rights, tone and contribution guidelines Daniel Chen ·

    Daniel Chen again acknowledges that maintainers can reject in any tone but argues that extreme unfriendliness drives contributors away. He wants contribution guidelines to state boundaries in advance to reduce conflict. This reply appeared during the capture process and was included in the completed inventory.

R

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

Back to top ↑