#Mastodon #Fulltext #Search
@krohne enshrining some third-party rando in the signup flow is not the way to do this.
the way to do this is to have a standard way to explicitly mark posts as searchable, the same way that Mastodon and several other Fedi servers already have a `discoverable` flag that explicitly marks accounts as searchable. that way, *any* search engine has a way of knowing what people have volunteered for.
https://github.com/mastodon/mastodon/pull/23808 unfortunately, the effort to patch this into Mastodon has stalled out.
NOTE: This PR does not implement the search functionality itself, just a framework to express explicit consent for posts to be indexed Mastodon has historically refused to provide full-text search ...
@krohne if we don't build something like this, "is this post set to public visibility" is the only intent signal to work with, and searching all public posts surprises Mastodon users.
(and only Mastodon users. "public = searchable" is the rule for full-text search implementations on most other Fedi servers that have it, except for GotoSocial.)
@vyr
> the way to do this is to have a standard way to explicitly mark posts as searchable
Man, the problem I have with this is I don't want to mark my posts either universally searchable or not universally searchable. I want to be able to pick and choose which search engines I allow to index my content!
As a side note, part of why I would like to have that option is that I can imagine a little social movement where people in the Fediverse decide to make a point of not letting Google Search index their posts, gravitating some other search engine, thereby giving that search engine a commercial advantage over Google Search, at least for searching the Fediverse.
@siderea @krohne yeah well don't get any of your rhetoric on my gender, thanks, i just got it the way i like it π
anyway, controlling how posts get exposed to web scrapers like Google is a related but different issue. specifically, you first have to somehow have enough leverage with Google to get them to agree to whatever scheme you propose, because they don't care about ActivityPub as such. they only see web pages, and those web pages are rendered by a dozen kinds of Fediverse server, and right now, even clicking the "hide me from search engines box" doesn't work 100% on your local instance, let alone once your posts leave it.
@mattswift @krohne there's always the possibility of an "opt-either" onboarding UX. consider the following:
"i want to be visible" on the left half of the screen vs. "i want to be quiet" on the right. one click defaults.
left one turns on discoverable and searchable flags, sets your default visibility to public, and disables the opt-out for web crawlers.
right one leaves the flags off, sets your default visibility to unlisted, tells web crawlers to ignore you, hides your social graph, and requires follow request approval.
anyone who wants further customization can go digging for it.