Behind search for masto is a resource-hungry #java application called #elasticSearch. Sure you might be able to get Masto to run on a #raspberrypi4, but you won't be running elastic search with it.
Having recently moved my instance to a much more powerful system, I now run ES, and WOW what a difference being able to search post makes! Soooo many times I wanted to reference a toot that had scrolled by but had no way of finding it. Now I do!
Even though I've put some serious resource limits on ES, it's bar none the most resource intensive service running (out of around 25).
Please consider sending a few bucks to the #MastodonAdmin of your instance. Better yet, if you can afford it, sign up for a monthly donation. They need it.
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:
15-20 minutes to load last batch. As I mentioned before, one gots to be patient. Lol.
Slow search is not unique to iceshrimp in the fediverse. I have experienced similar things on a large friendica server.
I wonder how iceshrimp's search capabilites would hold up on a server 1000 users or more. Would iceshrimp even want to have software that supports such server size?
Just a note, iceshrimp may have only started to get slow for me after I loaded dozens if not hundreds of results initially.
@julia wouldn't it he better if :activitypub: clients were to properly handle #hashtags and if #discoverability wasn't useless because making it a hidden #OptIn setting means noone I know ever activated it successfully...
I think :mastodon: and other implementations should just have an option to display the # instead...
Sadly using hashtags is a necessarx evil because #FullTextSearch - even one's own posts - DOES NOT WORK!!!
passwords when you don’t enforce changing them every 2 months: Viy$Ehi8sy3&2WQ
passwords when you enforce changing them regularly: password01!?password02!?password03!?password04!?password05!?
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;)
As of today, I have 6% of 350k known users opted into search - looks like we are moving in the right direction 😊
In total numbers this means that we've gone from about 3k to 22k users opted into search in less than a week - an impressive uptake in such a short time.
Hello #SFBA!
It's great to see all the great features in Mastodon 4.2. This is a substantial upgrade, and we're excited to announce we're performing the upgrade on Thursday, September 28th! We arn't expecting down time, but as with all upgrades it's possible there will be some service interruptions starting at 8:00 PM.
We're 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"!
We do not support full text search yet, but it's on the list ⚡
Is your #Mastodon instance running version 4.2? Yes? Here's a helpful visual for those trying to figure out how to opt into making your public posts searchable.
We've just enabled Full Text search on buddyverse.xyz !
Here's the friendly request: If you ever notice our server working hard to meet your requests and you appreciate the effort, consider dropping a few bucks on my Buy Me a Coffee page. Your support goes a long way in keeping things running smoothly. ☕💙
#Mastodon 4.2 is rolling out across the social web! On our quest to make Mastodon more delightful and easy to use, we've overhauled search, sign-ups, cross-server interactions and a whole lot more:
@Mastodon#fulltextsearch i am a mastodon user who also happens to run a few websites. i have this feeling that searching being enabled in mastodon might be effectively creating a denial of service by hitting sites all at once. or something. i cant really explain! i am seeing hundreds of simultaneous hits to the exact same url on my site from mastodon instances all over. all seem to be at ~02:30 UTC. 🥴 wassup? help? is it just me -- which would be weird. #mastoadmin#mastodev
With the impending release of Mastodon 4.2.0, I wanted to highlight the new Public Profile page.
There are several new options here, and they WILL control whether your posts are part of the new full text search. This feature is OPT IN, so if you're wanting your posts to be included, you're going to have to manually give it the thumbs up. If you don't, well, keep on doing what you're doing.