#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

#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

@apps

So this dead horse flinched again

"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."

I'll copy-pasta with only slight edits:

My entire point (all the noise notwithstanding) focused on

Default opt-in versus default opt-out

This is an agent --> recipient transaction

Default opt-in: the recipient is opted into (and receives) the agent's action whether the recipient --> knows of <-- the action or not

Default opt-out: the recipient is opted out of (and cannot receive) the action whether the recipient --> knows of <-- the action or not

Neither default opt-in nor default opt-out have any logical meaning if

--> THE RECIPIENT DOES NOT KNOW OF THE AGENT <--

in advance

There was no mechanism for prior notification *before* indexing

People would have had to stumble on what you're doing, by how, exactly?

How dose the recipient learn of what you've done *before* you do it?