AI policy

This article is a stub. You can help the IndieWeb wiki by expanding it with relevant information.

For the indieweb.org wiki policy, see wikifying

AI policy is a page (or section like on an about page or homepage) that describes the site owner’s policy about use of AI (typically LLMs or other GenAI) on their site, and sometimes an explicit part of a contribution policy to a community effort such as a blogging challenge.

IndieWeb Examples

AI policies on personal websites are typically posted at /ai-policy or /ai, sometimes part of an about page.

https://reillyspitzfaden.com/ai-policy/
https://michaelkupietz.com/ai-policy/
https://gregorlove.com/about/#ai (also gregorlove.com/ai redirects there)
Joe Crawford added his own /ai slash page in late 2025.
Ricardo Mendes AI page https://rmendes.net/ai/ and declares optional AI metadata information on every post via JSON-LD
https://brennan.day/ai/
https://thamara.co.uk/ai
https://onlinegoddess.net/ai-statement/
V.H. Belvadi has his policy at https://vhbelvadi.com/ai

in general:

https://slashai.page is an open directory of websites with AI policies, also available in a Google Doc (found via https://slashpages.net/)

Community Examples

Blaugust 2026 contribution policy (see initial blog post)

IndieWeb Community Examples

wikifying#Do_not_copy_from_LLM_generated_text
https://events.indieweb.org/2026/08/homebrew-website-club-asia-pacific-k2R3yMsm9xD4 "Requirements" notes
AI-assisted technology such as transcribing or recording tools are not allowed during these meetings.

See AI and the IndieWeb

More examples

Tim Bray has guidance on how he uses AI in the "Principles" section of his website Colophon:

The words here are not AI-generated. Exceptions occur only as examples in discussions of AI-related issues and are clearly labeled.
I edit pictures with software which advertises its use of AI, for example in operations such as “Select sky” and “Denoise”. However, I claim that none of the pictures are in any way AI-generated.

Platform Examples

Artificial Intelligence section of art silo ArtStation’s terms of service
- 2026-09-02 ArtStation: ArtStation Should Put Artists First
Codeberg has introduced prohibitions on LLM-generated projects
- 2026-07-23 Codeberg: Protecting our FLOSS commons from LLMs
Sourcehut prohibits original content written with or which facilitates the use of LLMs
- 2026-08-27 Drew DeVault: Changes to SourceHut's terms of service regarding LLMs
PixelFed code documentation reads "AI-generated contributions are not accepted."

Pull requests, patches, documentation, translations, issues, or other contributions that are substantially generated by generative AI or large language models will not be accepted. Contributors are expected to understand, author, and take responsibility for the work they submit.[1]

2026-09-28 PixelFed: README.md

2026-10-20 32-Bit Cafe: Rules and Community Guidelines Updates

Articles & Blogposts

2025-11-03 Xkeeper: No means no

Incidents

events/2026-08-05-hwc-asia-pacific-incident

Brainstorming

Brainstorming HWC policy

capjamesg's thoughts based on Naty S's excellent example above:

We do not allow use of AI-based transcription, recording, and note-taking tools during Homebrew Website Club, except for accessibility purposes, in which case we are happy to make accommodations. This applies to both the Zoom and Etherpad. If you breach this policy, we will ask you to leave the session, and we will inform other event organisers of the incident. If you would like or require closed captioning, please let the event organiser know before the call or when you join so we can make sure this is set up in Zoom for you.

James would use such a policy on both HWC event listings on events.indieweb.org, and also call it out any time a new participant joins a meeting.
- Does this mean closed captioning is not available either? It might fall under their umbrella of "transcription" but this support page looks like it may be separate. If it's possible to allow captioning without broader AI/LLM usage, I would be in favor. gRegor Morrill 15:24, 5 August 2026 (PDT)
  - I just made an edit based on this comment to clarify we can set up transcription in Zoom. Let me know if the language makes sense / reads well! capjamesg
    - The language is decent, though it comes after some strong language that sounds like a zero tolerance policy, so it might be missed (or may be ambiguous with "transcription" vs "closed caption"). I also think if it's disabled at the Zoom account level, it's not something that can be turned on once the meeting has started. I would be interested in running some tests with the two different options "Automated captions on device" vs "Automated captions" gRegor Morrill 09:38, 6 August 2026 (PDT)
    - I have just softened the opening sentence -- open to thoughts! capjamesg
      - 👍 looks good! gRegor Morrill 09:50, 20 August 2026 (PDT)

Tantek Çelik thoughts on AI-policy guidance to add
- Homebrew Website Club context in particular:
  - Problem: Boring/offtopic AI/LLM tooling chatting. I have been in a few HWCs where a few folks went on and on about their vibe-coding setup or other AI/LLM tooling, and seem more enamored of the setup/use of their tools than any measurable or demonstrable. Like they have fallen in love with using the tools, to the detriment of actually being productive or even having fun on their personal website. AI brainrot is a real thing.
    - Hearing people's anecdotes of AI tool use for their consulting business or day job or whatever is not what HWC is for.
  - Possible solution: As facilitators, if someone is taking more than 2 min to tie their point to something specific about their personal site, then they should be cutoff to allow someone else to chat (whoever is raising their hand or has said something in #events chat recently). As in at the 2 minute mark, let's find a way to politely cut them off, remind the group to keep chat relevant to what you are doing on your personal site, then call on the next person. This should be immediate IMO rather than giving someone AI-topic-chatting "one last chance" to connect their talking to their website — better to encourage them to take time to reflect on why/how what they are saying is relevant to their personal site in some observable or otherwise user-visible way.