Some of you noticed that @HolosDiscover is following you. It's a Fediverse search engine we built to solve a problem: when you start your own server with #Holos, your index is empty. #HolosDiscover provides a ready-to-use content catalog for everyone.
Only public posts from consenting users are indexed. Deletions and edits are reflected in real-time through ActivityPub activities.
How it works: https://discover.holos.social/how-it-works
Open-source (AGPL-3.0): https://codeberg.org/tom79/Holos-Discover
Holos is a very nice project, congratulations. Note that wrt Holos-Discover, the “How it works” does not explain the search mechanism, and the repo link gives a 404.
Regarding Holos-App the docs mention that it implements a “full ActivityPub server”, but it is unclear whether you mean “a full server” (S2S) or the “ActivityPub conformant Federated Server” specification profile, which in a quick peek is not what Holos-App is.. looks like? 
Sorry to hear that, and good to see how you acted on feedback. Many times before issues with the consent mechanisms have had similar outcomes. It is interesting what you mention in your toot, namely that:
This highlighted a real conversation the Fediverse needs about default settings.
From what I can glean of information still available is that you assumed particular microblogging mechanics to be defaults, where AS/AP is not a microblogging specification. I cross-referenced your toot in a different discussion with @stevebate where this notion of what is “generic” versus what is “app” was also unclear.