From 1379910e5712a4b2110336e1d3fa638b2245b54a Mon Sep 17 00:00:00 2001 From: PPPDUD <107440101+PPPDUD@users.noreply.github.com> Date: Mon, 29 Sep 2025 15:45:36 -0400 Subject: [PATCH 1/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1f70025a76..768beca0ff 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -21,6 +21,7 @@ Strictly, nothing is banned, but the following are *highly* discouraged: - One-use personal extensions (load the extension as a local file instead) - Extensions whose primary purpose is monetization (not in the spirit of an open source project) - Joke extensions (they aren't funny when they cause us to get bug reports) + - Extensions that were written mostly or entirely by a large language model (ChatGPT, Gemini, Perplexity, Claude, Grok, etc.) Some extensions were added before these rules existed. That doesn't mean you will be exempted too. @@ -40,6 +41,14 @@ New extensions should be added in a user folder. You can name your folder anythi Extensions must be self-contained. All libraries and hardcoded resources should be embedded into the extension's JavaScript file. If you include minified code, please link where to find the unminified code and include a copy of the original license. +## Some guidelines for LLM-generated code +As a rule of thumb, any extension is unlikely to be accepted if: + - It would not fulfill its primary goals without the portions which were written by an LLM + - The person submitting the extension does not appear to understand the LLM-generated code to a reasonable extent + - The person submitting the extension has written the entire extension with an LLM + - The LLM produced faulty code or "hallucinated" things that do not exist in the present context + +While there are no rules explicitly prohibiting the use of machine learning models to produce the images used in an extension or to write the extension's description, it does not make you look favorable with the extension reviewers. ## License **We are not lawyers. This is not legal advice.** From d829e00388a5fe6256d01ae1182b90e7a8721e96 Mon Sep 17 00:00:00 2001 From: PPPDUD <107440101+PPPDUD@users.noreply.github.com> Date: Mon, 29 Sep 2025 15:55:35 -0400 Subject: [PATCH 2/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 768beca0ff..1850c0a945 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,7 +48,7 @@ As a rule of thumb, any extension is unlikely to be accepted if: - The person submitting the extension has written the entire extension with an LLM - The LLM produced faulty code or "hallucinated" things that do not exist in the present context -While there are no rules explicitly prohibiting the use of machine learning models to produce the images used in an extension or to write the extension's description, it does not make you look favorable with the extension reviewers. +While there are no rules explicitly prohibiting the use of machine learning models to produce the images used in an extension or to write the extension's description, it does not make you favorable with many of the extension reviewers. ## License **We are not lawyers. This is not legal advice.** From f7e1e6b60d6ae3f88ae54041edb4ec3fed49bfe3 Mon Sep 17 00:00:00 2001 From: PPPDUD <107440101+PPPDUD@users.noreply.github.com> Date: Tue, 30 Sep 2025 08:47:54 -0400 Subject: [PATCH 3/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1850c0a945..700254af8f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,13 +41,15 @@ New extensions should be added in a user folder. You can name your folder anythi Extensions must be self-contained. All libraries and hardcoded resources should be embedded into the extension's JavaScript file. If you include minified code, please link where to find the unminified code and include a copy of the original license. -## Some guidelines for LLM-generated code +## Some guidelines for content generated by a machine learning model +### Large language models (LLMs) As a rule of thumb, any extension is unlikely to be accepted if: - It would not fulfill its primary goals without the portions which were written by an LLM - The person submitting the extension does not appear to understand the LLM-generated code to a reasonable extent - The person submitting the extension has written the entire extension with an LLM - The LLM produced faulty code or "hallucinated" things that do not exist in the present context +### Image generation models While there are no rules explicitly prohibiting the use of machine learning models to produce the images used in an extension or to write the extension's description, it does not make you favorable with many of the extension reviewers. ## License From e7ba5a9d648d3506bbb30e654a16b867c8e295fa Mon Sep 17 00:00:00 2001 From: PPPDUD <107440101+PPPDUD@users.noreply.github.com> Date: Fri, 17 Oct 2025 11:54:13 -0400 Subject: [PATCH 4/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 700254af8f..9eb3cb19ea 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -21,7 +21,7 @@ Strictly, nothing is banned, but the following are *highly* discouraged: - One-use personal extensions (load the extension as a local file instead) - Extensions whose primary purpose is monetization (not in the spirit of an open source project) - Joke extensions (they aren't funny when they cause us to get bug reports) - - Extensions that were written mostly or entirely by a large language model (ChatGPT, Gemini, Perplexity, Claude, Grok, etc.) + - Extensions that were written mostly or entirely by a large language model (ChatGPT, Gemini, Perplexity, Claude, Grok, DeepSeek, etc.) Some extensions were added before these rules existed. That doesn't mean you will be exempted too. @@ -47,7 +47,11 @@ As a rule of thumb, any extension is unlikely to be accepted if: - It would not fulfill its primary goals without the portions which were written by an LLM - The person submitting the extension does not appear to understand the LLM-generated code to a reasonable extent - The person submitting the extension has written the entire extension with an LLM - - The LLM produced faulty code or "hallucinated" things that do not exist in the present context + +Some other points to consider: + - Visibly faulty code is almost never allowed in new extensions, no matter if an LLM wrote it or a human did + - The extension reviewers have the final say on what's okay and what's not, regardless of what these guidelines say + - If you spam us with LLM-generated slop and then make something that's really amazing and useful, you might get ignored ([remind you of something?](https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf)) ### Image generation models While there are no rules explicitly prohibiting the use of machine learning models to produce the images used in an extension or to write the extension's description, it does not make you favorable with many of the extension reviewers. From 9e784e5efbc56a32c6d619473ca1aeea969e9097 Mon Sep 17 00:00:00 2001 From: PPPDUD <107440101+PPPDUD@users.noreply.github.com> Date: Sat, 18 Oct 2025 18:18:48 -0400 Subject: [PATCH 5/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9eb3cb19ea..419b2b395c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -49,9 +49,10 @@ As a rule of thumb, any extension is unlikely to be accepted if: - The person submitting the extension has written the entire extension with an LLM Some other points to consider: - - Visibly faulty code is almost never allowed in new extensions, no matter if an LLM wrote it or a human did + - Visibly faulty code is almost never allowed in new extensions, no matter if an LLM or a human being wrote it - The extension reviewers have the final say on what's okay and what's not, regardless of what these guidelines say - - If you spam us with LLM-generated slop and then make something that's really amazing and useful, you might get ignored ([remind you of something?](https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf)) + - If you spam us with LLM-generated slop and then make something that's really amazing and useful, you might get ignored ([remind you of anything?](https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf)) + - You do NOT need to write in perfect English when submitting an extension (though this is preferred); worst case, a contributor can edit your post for clarity ### Image generation models While there are no rules explicitly prohibiting the use of machine learning models to produce the images used in an extension or to write the extension's description, it does not make you favorable with many of the extension reviewers. From ed4e1da4ff463ba49bd990954a46f4230d990dca Mon Sep 17 00:00:00 2001 From: PPPDUD <107440101+PPPDUD@users.noreply.github.com> Date: Sat, 22 Nov 2025 13:56:29 -0500 Subject: [PATCH 6/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8623626bf8..3b0b2c1bdc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,6 +19,7 @@ These categories of extensions are **highly discouraged**: - Very niche extensions. You can write the extension for yourself, then import it as a file instead without needing us to review. - Extensions whose primary purpose is monetization. It isn't in the spirit of a free and open source project. - Joke extensions. Things that are funny to you are not funny to everyone, especially when we get bug reports about it. + - Extensions that were written mostly or entirely by a large language model (ChatGPT, Gemini, Perplexity, Claude, Grok, DeepSeek, etc.) Some extensions were added before these guidelines existed. We're trying to enforce them moving forward.