While the developer claimed to be protecting privacy, the system displayed usernames and full message content from community spaces that were never intended for public indexing. The burden was placed on users to remove themselves from something they never opted into.
Discord’s own Developer Policy explicitly forbids scraping or mass data harvesting. This wasn’t innovation—it was exploitation dressed in pseudo-academic language. If you can still search by channel + user ID, that’s traceable content. That's not “privacy preserving,” that’s thinly veiled exposure.
The developer's status message (extremely concerning and very inappropriate) and behaviour during take-down tickets further emphasized the lack of empathy behind the project. This wasn’t a public service—it was a boundary violation, and the shutdown was well-earned.
I also want to challenge the idea that this tool “solves the problem of not being able to easily search Discord servers.” That’s not a problem—that’s a design choice. Discord isn’t built for global indexing on purpose. Private communities, support groups, fandoms, and sensitive spaces rely on that separation to feel safe. Treating the lack of global search as a bug instead of a boundary shows a complete disregard for how real people use the platform.