Norm
d79c92f9c6
ci/woodpecker/pr/build-amd64 Pipeline is pending
Details
ci/woodpecker/pr/build-arm64 Pipeline is pending
Details
ci/woodpecker/pr/docs Pipeline is pending
Details
ci/woodpecker/pr/test Pipeline is pending
Details
Currently, Akkoma sorts by published date first before everything else. This however makes search results pretty bad since Meilisearch uses a bucket sort algorithm in order of the ranking rules specified: https://www.meilisearch.com/docs/learn/core_concepts/relevancy#behavior Since the `published` attribute is a unix timestamp, the resulting buckets are pretty small so the other rules essentially have little to no effect on the rankings of search results. This fixes that issue by moving the `published:desc` rule further down so it still sorts by date, but only after considering everything else. AFAIK attribute and sort doesn't really affect results for Akkoma since the only attribute considered is the `content` attribute and the `sort` parameter isn't used in Akkoma searches. Everything else is made to match more closely to Meilisearch's defaults. |
||
|---|---|---|
| .. | ||
| ecto | ||
| search | ||
| activity.ex | ||
| app.ex | ||
| benchmark.ex | ||
| config.ex | ||
| count_statuses.ex | ||
| database.ex | ||
| diagnostics.ex | ||
| digest.ex | ||
| docs.ex | ||
| ecto.ex | ||
| email.ex | ||
| emoji.ex | ||
| frontend.ex | ||
| instance.ex | ||
| notification_settings.ex | ||
| openapi_spec.ex | ||
| refresh_counter_cache.ex | ||
| relay.ex | ||
| robots_txt.ex | ||
| search.ex | ||
| uploads.ex | ||
| user.ex | ||