A couple days ago I updated https://search-lemmy.com/ to 0.4.0.

New features, that several people were asking for:

  • The UI has been overhauled and it should be much easier to find your home instance now.
  • Search itself has been overhauled. Increase search performance significantly. I also automatically search for related terms as well. You may now see fewer search results, but ideally they should be more relevant. You can also now include basic syntax like:
    • quotes: “some terms that must be together”
    • negative terms: cat -dog (shows posts about cats that don’t mention dogs)
    • either or: cat OR dog (shows posts about either cats or dogs). The default search behavior is now an implicit AND, but order doesn’t matter.
  • I’ve added several new filters that you can use including:
    • !safeoff – Disables safe search allowing NSFW posts to appear in the search results (NSFW is now hidden by default)
    • since:YYYY-MM-DD – shows only posts that have occurred since the specified date
    • until:YYYY-MM-DD – same as above but in reverse. It will only posts up to the given date.
  • I’ve removed the preferred-instance query parameter from the results URL so it should be easier to share links to search results now.
  • The date the post was created or last updated is now displayed in the search results.

Bug Fixes:

  • Site performance should now be stable. Fixed a bug related to the database pool that was causing the site to hang.
  • Fixed a bug that would cause broken links.
  • Fixed various bugs with the crawler causing posts to be missed.

Known Issues:

  • If you set your home-instance to a fairly small instance, the number of search results is also relatively small. Once (https://github.com/LemmyNet/lemmy/issues/3259) is resolved. I should be able to show links regardless of what your home instance is set to, allowing you to search the entire Fediverse.
  • Currently searching only looks at the post title and body. Comments aren’t indexed either. This also is dependent on the above issue on Lemmy itself.

Finally some things to note:

I’ve started to refactor the code to abstract away Lemmy from the actual search engine. As I now start to prepare to search other Fediverse instances like Kbin, and maybe even Mastodon, etc…

  • GodOfThunder@lemm.eeEnglish
    18·
    1 year ago

    I’ve saved this, but it would be nice to see the syntax somewhere in the search engine

  • Deez@lemm.eeEnglish
    3·
    1 year ago

    Thank you for making this!

    I don’t get any results no matter what I search for. The page refreshes, but no results (or errors) appear.

    Turning my adblockers off had no effect. Same behaviour in Safari and Firefox on iPadOS 16.5.x.

    Edit: Oops, I didn’t select an instance and the default instance (Ice Orchid) returned no results. Changing to my home instance fixed it. Maybe default should get changed to Lemmy.world or something big?

  • lchapman@programming.devEnglish
    2·
    1 year ago

    What about it I want to find the most populated community for a given search term, across the lemmiverse?

    • marsara9@lemmy.worldOPEnglish
      0·
      1 year ago

      Currently you can just search for posts. I don’t track anything like the number of members in a community etc… just the content of the post and how more or less accurate they are to your current query. I’m continuously trying to improve the page rankings though.

      I guess in theory you can perform the same search multiple times with different community:!some_community@some_instance filters to see which returns the most results, but ya, that wouldn’t be the most convenient. At the moment this tool though is about finding posts, but who knows what features I may add in the future.

        • marsara9@lemmy.worldOPEnglish
          2·
          1 year ago

          I’ve been seeing a few people ask for something like this recently, so I might try and see how hard it would be to build something to help find active communities.

      • miles@lemmy.worldEnglish
        0·
        1 year ago

        very cool, thanks for the feedback and the site! my question is more along the lines of whether someone interested in a topic would be able to find my community without knowing it existed in the first place?

        • marsara9@lemmy.worldOPEnglish
          2·
          1 year ago

          Just added a new feature that lets you search but it returns the number of matches per community. So you should be able to use that to find the most active communities based on your search result.

              • miles@lemmy.worldEnglish
                1·
                1 year ago

                cleared cache, your url still gives me no results. in the top right the dropdown as “Ice Orchid”. I’m not sure what that is

                • marsara9@lemmy.worldOPEnglish
                  2·
                  1 year ago

                  Here’s the landing page if you just go to https://www.search-lemmy.com/. I’m assuming that drop-down that you’re referring to is your home instance selector. Since you’re on lemmy.world I suggest you set that to well, lemmy.world. Then you can do your search and all of the results will take you directly to that post on lemmy.world (or whatever you set as your home instance).

                  Now you can also see that Find Communities button in the top right, you can click on it and it’ll take you to a similar page but instead of returning posts for search results, it will return a list of communities, based on how many matches it found. (as if you did a search on the normal page but instead just counted the number of results per community).

    • marsara9@lemmy.worldOPEnglish
      1·
      1 year ago

      This doesn’t change the behavior of the built-in search within Lemmy. But rather this is suppose to be a close approximation of using Google with adding reddit to the end of your query.

      The problem with the fediverse is that there are so many different instances you can’t really include them all in a search query and even if you could the links that Google would provide wouldn’t necessarily go to YOUR instance. This aims to fix that.