Post #1354093

@mitsuhiko setting aside the issue that is *undeniably* a derivative work because the original was in the training set. It wasn't vibe *forked*. It was vibe-hijacked! I don't think people who have chardet in their dependencies expected to get an entirely slop rewrite (this point is extremely slightly tempered by the major version bump). Also, collaborators didn't expect to have the entire repo replaced. A fork into a different repo with a different name would be one thing, but this is like replacing someone I know with an AI replica and acting super surprised when I'm upset.