3 Most Prevalent Themes
1. Need for Context & Comparison
Users repeatedly ask the author to clarify how the project differs from existing tools and to acknowledge prior art.
"Personally I love when projects mention whether theyāve found other existing software that does something similar, and if so how this app compares." ā noānameāhere
"Thereās stuff like https://presidio.dataprivacystack.org originally from Microsoft." ā noānameāhere
These comments highlight that readers want a clear statement of novelty and a brief comparison with known alternatives.
2. Accidental Leakage & āLazyāCensorā Utility
Several participants point out that the real value lies in preventing accidental exposure of personal data, especially when users are lazy or unaware of leaks.
"It could be useful more as a labor saving device to enable censoring while allowing the human to engage in easy copyāpaste." ā frumiousirc
"I find it amusing how a lot expect people to ānot be lazyā, people are mostly lazy and even sometimes clueless about how much they leak to BigCorps." ā mohamed_am83
3. Requests for Expanded Reach & Practicality
There are multiple suggestions to broaden the toolās appealāe.g., making it work in browsers, CLI agents, or locally for code obfuscation, and targeting nonātechnical users.
"Iām not sure whether this project is truly practical in its current form. More and more people are using AI agents through CLI tools or desktop applications, so I think you should consider extending it to run locally." ā toto007
"The core is plain JS so it is easy to make a plugin, but I believe there are many plugins already for common coding agents. I wanted to target the less savvy and nonācoder people who treat chatgpt and friends like the new google." ā mohamed_am83
These points stress that the projectās future success may depend on extending its scope beyond simple webāAI interactions and making it accessible to a wider, possibly nonātechnical audience.