noindex

With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.

#HolosDiscover is back, from a clean slate.
A #Fediverse search engine that uses standard #ActivityPub federation. It follows you like any account, respects indexable flags, #nobot, #noindex, locked accounts. Deletions, edits, blocks are processed instantly through ActivityPub.
You have full control. Block it, mention it with "unfollow", or disable indexing in your settings.
Source code under AGPL-3.0 on #Codeberg.

Details: https://discover.holos.social/how-it-works

Account: @HolosDiscover

I'm on social media to interact with other *people*.

If you're using or building a tool to scrape, analyze, summarize what I post — fuck you.

#NoAI #NoBots #NoIndex #NoBot

#HolosDiscover currently blocks #Bluesky accounts bridged via #BridgyFed, because AT Protocol has no equivalent to the indexable flag.
The bridge is opt-in, but bridged users cannot signal refusal of third-party indexing.
Standard opt-out mechanisms remain functional: block @HolosDiscover, #nobot or #noindex in bio, mention with "unfollow".

What's your opinion?

I fixed a privacy bug in #HolosDiscover. If you asked not to appear in search through your bio, it did not always respect that because the #NoIndex tag in bios had a bug and the bot did not read profile fields.
In some cases discovery also fell back to the discoverable flag, which is now removed (that flag is about accounts, not posts).
Everything is fixed and I also cleaned up what was already stored. The database is clean. Sorry for that.