this post was submitted on 06 Aug 2023
1458 points (98.9% liked)

Announcements

22776 readers
1 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
 

This is an opportunity for any users, server admins, or interested third parties to ask anything they'd like to @nutomic@lemmy.ml and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today.

Note: This will be the thread tmrw, so you can use this thread to ask and vote on questions beforehand.

Original Announcement thread

you are viewing a single comment's thread
view the rest of the comments
[–] Anaralah_Belore223@lemmy.world 21 points 1 year ago (2 children)
[–] dessalines@lemmy.ml 5 points 1 year ago (1 children)

You'll have to open an issue for it. As long as there's some way to translate the search operators into postgres statements, it'd be doable.

OK. See you on Github...

[–] Limeey@lemmy.world 5 points 1 year ago (1 children)

It would be better to replicate the db into a purpose built search engine like elasticsearch or TypeSense, and then modify the UI to use that. It's dumb for lemmy to implement a search engine when there are better more supported systems out there. This isn't really a lemmy feature, imo, outside of supporting deployments using those types of products.

[–] dan@upvote.au 4 points 1 year ago

Lemmy would still need to provide the UI for searching, and handle keeping Elasticsearch up-to-date.

A dependency on Elasticsearch would significantly increase RAM usage though, so if Lemmy were to add support for it, it should be optional.