I will investigate the issue with #HolosDiscover. Since another bot was launched on holm.community, I have been getting several complaints:

- NoIndex/nobot in bio not respected
- Locked accounts followed
- AP flag not honored

I contacted the maintainer to ask whether the code was changed. This should never happen. These complaints only started after that bot appeared.

I am taking this very seriously. If the problem is in my code, I will fix it immediately. Sorry about that.

I need help with the server hosting all my open-source projects: #Fedilab, #HolosSocial, #HolosDiscover, and more.
The current server costs €350/year but is no longer suited for the load. I often run out of disk space. I need to migrate to a more powerful one with expandable storage. Renewal is due in a few days.
I have set a goal of €500 on Ko-fi, cost unknown.

Ko-fi: ko-fi.com/tom79

Liberapay: liberapay.com/tom79

Sharing this post helps keep my open-source projects alive.

#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: discover.holos.social/how-it-w…

Account: @HolosDiscover

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?

• It should have stayed up (52%, 150 votes)
• Right call to shut it down (24%, 71 votes)
• No opinion (22%, 65 votes)

I'm really sad to see this happen. I thought it was a great project that respected users.

#HolosDiscover