A form of toot search has been requested since April 2017, multiple times:
I have announced that am going to implement it with constraints that won't let it be used for abuse on Dec 20 2017, then again on Dec 31:
During implementation I seeked feedback #onhere, submitted PR on Feb 3 2018:
Then announced it in a progress report on Feb 21:
The biggest issue with ElasticSearch (that was the only issue raised during all that time) is that it takes a lot of RAM and it's an extra dependency. So it was made completely optional, not everyone wants to deal with that.
It (quite obviously) only operates on data that was in the PostgreSQL database anyway. It took 78 lines of code (mostly one file) to add the indexing (which is part of the reason it was chosen - ease of integration).
@Gargron and it makes search on mastodon.social blazingly fast !!😸
@Gargron but how does it work???
@Gargron if i search for something i've written, nothing is returned.
@hirojin We don't have it
@Gargron I was thinking of using something smaller, perhaps Bleve (written in Go, much lower memory use) with Mastodon, if that's possible. Could be worth looking at
@Gargron there's no pleasing some people! No objections here to either its implementation or the integration process. Thanks.
@Gargron doing it in pgsql takes 5lines of code and maybe 10 of stored procedures... I proposed on the issue to help have an alternate implementation for those who don't need/want ES. Nicely ignored ;)
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!