#MeiliSearch
Live, measured metrics for the hashtag #MeiliSearch from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #meilisearch
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 17:31 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 17:31 UTCNo related tags with measured usage found for #meilisearch.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 17:31 UTCEverything below is measured over the latest 40 public posts (spanning ~18124 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (32) · Chinese (Taiwan) (1) · Russian (1) · German (1)
Avg boosts / post: 1
Top of the latest posts
I Ditched Elasticsearch for Meilisearch. Here's What Nobody Tells You "Then I spent one afternoon replacing it with Meilisearch. My p99 search latency went from 180ms to 12ms. My infrastructure bill dropped to $14/month. My configuration we
Progress [104/109][95%] for Go packaging of Forgejo in #Guix https://codeberg.org/guix/guix/pulls/9867 #forgejo needs #meilisearch a search engine written in Rust, hopefully Guix has an improved packaging model for that
I'm using #Meilisearch on @hollo, but it frequently dies due to #OOM. Am I doing something wrong, or is this a bug in Meilisearch?
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/meilisearch