This only applies in #Mastodon. #Misskey and its forks like #Sharkey have #fulltextsearch too and they will ignore your "#privacy setting" for every post it has ever seen from you. And IIRC Misskey did implement full-text search way earlier than Mastodon has started debating about it. :sagume_think:
Why did this debate of full-text search arose again? :seija_coffee:
I've noticed a lot of chatter about setting up Elasticsearch for Mastodon 4.2's new full text search over the last few days, including what hardware is required, how difficult is it, etc.
So I thought I’d write down my experience, including the hardware I'm running Elasticsearch on for my single user instance:
I just checked, and it appears that only about 1% of all 300k Mastodon users that my instance knows about currently have opted into full text search 😢
Really hoping that number will increase!
Also, does anyone know how Mastodon indexes users from non-Mastodon fediverse servers? These presumably don't have the indexable flag set. I hope Mastodon still indexes those, given that pretty much all other Fediverse software indexes all users?!
(edit: been asked a few times how i got those numbers: Two simple SQL queries: select count(*) from accounts; followed by select count(*) from accounts where indexable = true;)
this is nice, new #fulltextsearch will include the exclusion operator with (-) for example ". -has:link -has:media" in search will only fetch text only results, and exclude any posts with links and images/ videos/ audios.
✨ Opt-in indexable search support has landed in Pixelfed!
This means we'll be compatible with Mastodon's new #fullTextSearch feature, and it is opt-in so you have to navigate to Settings -> Privacy and then enable "Include public posts in search results"!
Yeah good point by @cendawanita about permissions (or lack thereabouts) for #kbin et al to scrape the #fediverse and put posts/toots into magazines. It feels like so many #Mastodon admins are blind to how the fediverse beyond Masto software & the Masto API actually works.
Seeing such folks write lengthy posts about defederating Masto instances running Vyr's search patch while the rest of the fedi has #FullTextSearch and the #Threadiverse scrapes it with next to no backlash. It's like folks don't know that there's a bigger problem with #ActivityPub re #privacy and #safety than Website Boy's latest antics, and we need to push for #FediverseSafety and privacy flags at a ActivityPub protocol level. Until then, everything is just a non-binding, non-enforceable agreement about cultural norms that there's seems no consensus on; and definitely no focus on minority safety, rather features some will claim are wanted by a majority.
Folks should take a look at the #fullTextsearch function that Eugen is proposing for #Mastodon and how closely it resembles the #search patch of the woman who he kicked off the GitHub a couple of months ago. Also, her patch was more configurable that the thing he's bringing to main that has zero attribution of her work. #fediverse#mastodev#MastoDevs
this enables full-text search for posts you haven't interacted with, as well as full-text search for accounts, and includes several advanced filtering operators and parser fixes.