Do we have a tool that can detect whether a project is majority LLM-written? This is an unenforceable rule, unless it's just coming down to vibes and they're going to decide what projects to ban based on their feelings.
Are you sure? It's pretty easy to find telltale signs of LLM usage, like the CLAUDE.md file, the '.cursor' directory, the 'vim'-sized codebase done in a week.
That's just vibes. Measuring how much data someone uses is concrete and empirical. They are implementing TOS rules that are based on judgement and require a judge. Very different when implemented practically, especially in terms of effort on the part of the org. Quotas are automated, evicting projects is highly manual.
Do we have a tool that can detect whether a project is majority LLM-written? This is an unenforceable rule, unless it's just coming down to vibes and they're going to decide what projects to ban based on their feelings.
They are monitoring their resource usage. If they find a resource leak and it's traced to an LLM project, they will delete it.
Terms of use should be read as a statement of intent, not a series of if-then statements.
> It is an unenforceable rule
Are you sure? It's pretty easy to find telltale signs of LLM usage, like the CLAUDE.md file, the '.cursor' directory, the 'vim'-sized codebase done in a week.
That's just vibes. Measuring how much data someone uses is concrete and empirical. They are implementing TOS rules that are based on judgement and require a judge. Very different when implemented practically, especially in terms of effort on the part of the org. Quotas are automated, evicting projects is highly manual.
2 replies →