# Let's allow AI output in some restricted sense

**URL:** <https://discourse.julialang.org/t/lets-allow-ai-output-in-some-restricted-sense/139371>\
**Category:** Meta Discussion\
**Created:** [September 11, 2026, 5:35pm UTC](https://discourse.julialang.org/t/lets-allow-ai-output-in-some-restricted-sense/139371 "2026-09-11T17:35:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [September 11, 2026, 5:35pm UTC](https://discourse.julialang.org/t/lets-allow-ai-output-in-some-restricted-sense/139371/1 "2026-09-11T17:35:41Z")

</div>

Continuing the discussion from [I don’t want to read LLM output](https://discourse.julialang.org/t/i-don-t-want-to-read-llm-output/139244/125):

I was going to suggest allowing AI output, and have it labelled, then that was the next thing a saw in that very long thread. [While I like reading threads, that one is getting very long… so I like some resolution.]

Full disclosure: I’ve had one post of mine hidden likely because of AI output:

> [@\[ANN\] JuliaLibWrapping.jl: bringing Julia libraries to C and Python users](https://discourse.julialang.org/t/ann-julialibwrapping-jl-bringing-julia-libraries-to-c-and-python-users/139150/12):
>
> Test a distribution with pip install in a clean virtual environment on such a machine. I’m not involved with the project just posting what seems relevant above and: Pass privatize = false only when that isolation is knowingly unnecessary. Only the Julia runtime libraries are privatized. BLAS, Fortran, and unwind libraries may still be shared. Bundles produced by different Julia versions have not been established as mutually compatible. This behavior has been measured on Linux; macOS and …

There as always, I’m just trying to help people, most of the text was mine, like a screen-full, and the AI part only like 4 lines in the end, and I dropped them and the inferior/incomplete answer appeared again.

The discussion has been mainly about announcement posts, I don’t know the post(s) being objected to. I do know some of the great packages I see are made with AI, to a large degree, and we will see more of such. I don’t think AI use should be overused in such announcement posts, right now, the ban on AI here is more strict than for the packages you make. I think the main thing is that people know they are getting some genAI. It would be great if we could even color-code genAI parts. At least just state it, and if discourse could label as 30% is AI content etc. that would be great. First thing is do we like to allow some exceptions, like maybe up to 40% max genAI? I suppose we might want to review the policy over time… I don’t know how to make a poll on this.

---

<div class="post-metadata">

**Author:** ![Nathan\_Boyer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nathan_boyer/32/14825_2.png) [@Nathan\_Boyer](https://discourse.julialang.org/u/Nathan_Boyer)\
**Post date:** [September 11, 2026, 5:53pm UTC](https://discourse.julialang.org/t/lets-allow-ai-output-in-some-restricted-sense/139371/2 "2026-09-11T17:53:39Z")

</div>

This topic was expanded on and largely settled in this other thread:

> [@Updates to the site guidelines, especially regarding gen-AI](https://discourse.julialang.org/t/updates-to-the-site-guidelines-especially-regarding-gen-ai/134315/29):
>
> That might indeed go into the right direction. I would simply suggest to a) appeal to refrain from AI use in direct communication with people (e.g., more or less “chatting” or “talking” with each other), b) make clearer content quality related guidelines not simply (do not use a certain tool), and c) clearly offer the poster a chance to heal the post. What about that? EDIT: A more technical solution would be “transcribed video messages” so there can be no doubt; might even be a market for suc…

> [@Updates to the site guidelines, especially regarding gen-AI](https://discourse.julialang.org/t/updates-to-the-site-guidelines-especially-regarding-gen-ai/134315/30):
>
> Holy cow, I think we might have done it! @gwr: that’s the status quo, or at least the intent of it! slight_smile If and how we improve the wording in the guidelines, flags and DMs is really the only question… along with the fact that I’d say that this entire site is for direct communication with people. But, yes, that is exactly our intention.

---

<div class="post-metadata">

**Author:** ![technocrat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/technocrat/32/220947_2.png) [@technocrat](https://discourse.julialang.org/u/technocrat)\
**Post date:** [September 11, 2026, 10:54pm UTC](https://discourse.julialang.org/t/lets-allow-ai-output-in-some-restricted-sense/139371/3 "2026-09-11T22:54:41Z")

</div>

This post was temporarily hidden by the community for possibly being off-topic, unfocused, inappropriate, or spammy.

---

<div class="post-metadata">

**Author:** ![adienes](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/adienes/32/37459_2.png) [@adienes](https://discourse.julialang.org/u/adienes)\
**Post date:** [September 12, 2026, 1:48am UTC](https://discourse.julialang.org/t/lets-allow-ai-output-in-some-restricted-sense/139371/4 "2026-09-12T01:48:51Z")

</div>

This post was temporarily hidden by the community for possibly being off-topic, unfocused, inappropriate, or spammy.