Conversation

Notices

1. Embed this notice
   Renaud Chaput (renchap@oisaur.com)'s status on Friday, 25-Aug-2023 04:41:22 JST Renaud Chaput

   Full text search has been merged in #Mastodon `main` branch, and will be in the next (and final?) 4.2.0 beta 🎉

   It is opt-in, so it will take some time to be filled with people content as they enable their profile to be indexed, but this was one of the most wanted Mastodon features for some time.

   We plan to deploy it to mastodon.social and mastodon.online in the coming days to have a bit more feedback on it and see how it behaves in the wild.

   • Gianni Rosato repeated this.
   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Friday, 25-Aug-2023 08:22:49 JST Renaud Chaput

     in reply to

     To opt into your content being searchable, once your instance is upgraded to support this feature, head to the your profile, and the new “Privacy and reach" tag, then tick the "include public posts in search”.

     We will try to ensure users know this setting exists, nothing 100% defined yet, but we may add a dismissible banner asking to review your privacy settings page.

     海豹打油? repeated this.
   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Friday, 25-Aug-2023 10:24:55 JST Renaud Chaput

     in reply to

     Full-text search allows you to search for words in the content of statuses (if your instance has ElasticSearch configured), compared to the current version which only allows searching for hashtags.

     In addition, you get a whole lot of search modifiers for advanced search (no UI for those yet):

     has:image / has:video / has:audio / has:media
     has:poll / has:link / has:embed
     is:sensitive / is:reply
     language:en
     from:account
     before:2023-08-08
     after:2023-08-08
     during:2023-08-08

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Friday, 25-Aug-2023 14:52:15 JST Renaud Chaput

     in reply to

     • Berkubernetus
     • Bart Louwers

     @bart @fuzzychef The current search implementation relies on the Chewy Ruby gem, which uses Elastic's Ruby client under the hood. So we "officially" only support ES, but I know some instances are using OpenSearch without any issues.

   • Embed this notice
     Bart Louwers (bart@floss.social)'s status on Friday, 25-Aug-2023 14:52:16 JST Bart Louwers

     in reply to

     • Berkubernetus

     @renchap @fuzzychef Have you looked at OpenSearch as a FOSS ElasticSearch alternative? https://opensearch.org/

     Edit: Looks like the answer is yes, it is compatible. ❤️ https://github.com/mastodon/mastodon/pull/22422

     藤井太洋, Taiyo Fujii repeated this.
   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Friday, 25-Aug-2023 14:52:42 JST Renaud Chaput

     in reply to

     • Berkubernetus

     @fuzzychef Correct, this rely on ElasticSearch

   • Embed this notice
     Berkubernetus (fuzzychef@m6n.io)'s status on Friday, 25-Aug-2023 14:52:43 JST Berkubernetus

     in reply to

     @renchap so this is ES-based, rather than using the already-required Postgres instance, correct?

     So "lightweight FTS" without adding ES is still an unimplemented feature.