I was going to comment how it might be ironic to call the project evil instead, but remembered that's the name for the vim emulation on emacs.
> The workflow I’m going to describe has one core principle: never let Claude write code until you’ve reviewed and approved a written plan. This separation of planning and execution is the single most important thing I do. It prevents wasted effort, keeps me in control of architecture decisions, and produces significantly better results with minimal token usage than jumping straight to code.
The rabbit hole goes deep, and it will be a fulfilling journey, with all its ups and downs. I won't claim it to be your particular panacea, so I won't force it, and won't judge your response. After all "you know how judgemental christians can be!" - Moral Orel
It's hard to distinguish who's a bot, who's a narrative pusher and who's an enthusiast. Which is exactly what you'd want from an astroturfing campaign. There's a clear benefit: people in the industry are reading this, and in doing so they're granting mindshare.
There's one way that can prevent inauthentic support campaigns - personal key signature. But judging by how afraid people, especially in the US, need to be of their government surveilling them, this isn't going to catch on.