We're the creators of Lemmy, Ask Us Anything. *Starts Monday, 7 Aug, 1500 CEST*

Dessalines@lemmy.mlmod to Announcements@lemmy.ml – 1373 points –

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

702

You are viewing a single comment

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.

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.

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.