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

@Purplegengar25@lgbtqia.space you can add #noindex but no actor has to follow it

Contrary to what some people say, #HolosDiscover is not a scraper. It speaks #ActivityPub, and every deleted or edited post is immediately updated in the database. It relies on the #Fediverse indexable flag, with stricter rules: accounts with #NoBot or #NoIndex in their profile, and locked accounts, are excluded. Only public posts are indexed. I recently fixed a bug where the #NoIndex tag in bios was not respected. Sorry about that. https://discover.holos.social/

@Seb_Solon@framapiaf.org Yes, it is an opt-out service, because Mastodon makes accounts indexable by default. But the service goes further by also checking bios and profile fields for #NoIndex or #NoBot tags or words. Locked accounts are also excluded.

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.

@jvnebnunny@lgbtqia.space @site_admin@newsmast.community There was a dude a few weeks ago who vibe coded an account to automatically share posts across fediverse' without the posters permission, using tags. It was suggested that adding #NoIndex to a users bio would prevent this. Not sure if it worked as the account was quickly blocked on the server I'm on, however I suspect this is the same person.

@mxk@hachyderm.io #NoBots like this? Or does it have to be #NoBot? I've also seen both. Along with #NoBridge, #NoIndex, and a few others...plus the new ones Evan mentioned today. Also, that's not how consent works. I shouldn't need to defend myself from your lack of boundaries. But I guess I just need to add the #NoBots pack to my purse along with the Rohypnol test kits, mace, and other things I'm supposed to carry to keep guys from violating my boundaries.

@alice@lgbtqia.space I'd seen the tags.pub bot before, and hadn't thought about it at the time. I read Evan's post and opted for the "extreme" option of blocking the domain. That seemed the most logical option. Imagine if all the different bots required different hashtags to opt out. #nobots #botgoaway #noindex #nobotno #stopitbot #BotNo #NoTagBot #robotstop #NOTHANKS #stopindex #nobotscrape #noscraping #ignorethis #noindexno #donotscrape #donotindex No room for bio. @evan@cosocial.ca

@chad@vault37.xyz For what it is worth, the dev of that AI timeline tool says it now supports several ways to stop it.

Zeitgeist now:

• respects the noindex preference if set on your account
• respects #noindex or #nobots if those are in your bio
• sends a unique user-agent ("Zeitgeist/1.0") if you want to block the client entirely.

@maddad@mastodon.world @mastodonmigration@mastodon.online