this post was submitted on 05 Jun 2026
56 points (96.7% liked)
FreeAssembly
152 readers
13 users here now
this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.
in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.
some posting guidelines apply in addition to the typical awful.systems stuff:
- all types of passion projects and contributions are welcome, including and especially those that aren't programming or engineering in nature
- this is an explicitly noncommercial, share-alike space
- don't force yourself to do work you don't enjoy, or demand it of others
(logo credit, with modifications by @dgerard@awful.systems)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
conforming tools should ignore it, and that’ll work just fine if it’s renamed
I don’t think there’ll ever be a conforming LLM because LLMs are built on systemic consent violation, but the slop machines can use their magic mind powers or whatever bullshit I’m expected to swallow this week to find the correct file
I recommend the renamed file gets a mention in the project docs so humans can find it, and a good name is also very obvious and more or less self-documenting. I’ve seen some projects use
.noaiwhich I like too, but unfortunately that’s very likely to get lost in a directory listing, and locallylswon’t display it at all without-a.They can't ignore it, because they have no way to identify it. Combining the various dtatemennts in the readme, you've said it can have any name, and contents, and be in any location. That means it could be an empty file called
fred.txtin thetests/stuffdirectory. My suggestion is simply to remove the rename/move clause, and settle on a fixed name in the root to remove any excuse for not finding it.With respect for what you're trying to do, and no love at all for them, they really can't as you've mafe the spec too loose.
I think that's probably the point. Once you've cloned the project, you neither need, nor want, to see the file as you're not an LLM. It also means any tooling that cares, say an IDE plugin to disable LLMs on a project, can easily identify it.
I’ll take a bug to rephrase the section as “conforming tools shouldn’t process AAA-NO-SLOP.md files in any special way” if that helps make it clearer why the file can have any name and contents
if in spite all of the marketing claims to the contrary an LLM can’t understand a request to not slopify a repository but a human can, that sounds like a bug for anthropic’s bug tracker to me
That sounds much clearer, yes.
Amen.
you did read this bit right, its name is for humans
I get that, but one paragraph later, they say:
I don't see how any tool could obey this, given the fact the
AAA-NO-SLOP.mdfile may not be called that, and its location, and indeed very existence, only mentioned in a readme. It seems to me that, if the aim is to keep LLMs and similar tooling off of a code base, it should be made possible for them to reliably find the signal to do so.They should, but they won't.
You're still arguing with a file that's for humans.