The rule is for vibe coded projects. From the article:
If your work fits into these cases, it is unlikely that you are affected at all:
- Projects who have an active community that cares about and maintains the software
- Projects with a significant pre-LLM history
- Maintainers who unknowingly or willingly accepted LLM-generated contributions from other contributors, if your project otherwise does not involve the heavy use of LLMs
They don't need a rule that can be run automatically because it's a purely human operation that is trying to take a stand against the more pernicious effects of corporate LLMs.
Do you just disagree with this stance and are just trying to poke whatever hypothetical holes you can in their logic, or do you just want more rigorous definitions/rules?
From experience, content moderation works best when there is some flexibility in the rules, so people can talk it out and come to concessions together.
Or maybe a lighter version of the duress pin that just loads the fake profile (or alternate profile) but leaves the other(s) intact.
If you're just handing your phone over for a border pig to swipe through before waving you through that might be adequate.