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.

[apps@toot.fedilab.app]

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.

[lexinova@cyberplace.social]

@apps the issue of #nobot #noindex, it's the fact it's opt-out

and people are fedup of opt out and want opt in

[apps@toot.fedilab.app]

@lexinova
The debate goes beyond that. The real question is why developers chose to enable "indexable" by default when creating an account. A default opt-in is effectively an opt-out. That's where the conversation should start.

[raphaelmorgan@disabled.social]

@apps I see no problem with this approach generally opt-in is better than opt-out, so if there's a way to make it opt-in even for people on servers that allow indexing by default that would probably decrease the backlash, but like... If we don't want our posts indexed, we can turn indexing off and it seems y'all were respecting that so I don't mind

[apps@toot.fedilab.app]

We were caught off guard by the reactions and acted quickly. But we want to give the community a voice. We'll follow the result of this poll: if it should have stayed up, we'll reopen the source code and bring the service back.

[lutindiscret@mastodon.libre-entreprise.com]

@apps if an account is marked as indexable, just index it. If the default is wrong, that's the instance admin fault, nit yours.

If Google can index it you can too.

If people are unhappy with the setting of their profile, they can change it or blame the software or the admin and not people of good faith like you.

Public toots are talking to the world in a megaphone by design, expecting privacy is absurd

[lutindiscret@mastodon.libre-entreprise.com]

@apps this 100℅ the wrong people in being blamed here

[apps@toot.fedilab.app]

@lutindiscret
We panicked quickly because things escalated beyond what we expected. But we still believe our approach was far more respectful than what's already happening: the same data is being exploited by others without users even knowing. At worst, we raised awareness.

[scriptfanix@maly.io]

@apps Tough one: I feel like you did set it up respectfully, so it should have stayed up. BUT taking it down when people voice concerns and objected was also the right thing to do, both morally and for the reputation of the Holos project.