#FullTextSearch
Live, measured metrics for the hashtag #FullTextSearch from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fulltextsearch
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 05:00 UTC1 uses by 1 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 05:00 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:00 UTCEverything below is measured over the latest 40 public posts (spanning ~21420 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (31) · Russian (3) · German (1)
Avg boosts / post: 1.4
Top of the latest posts
💡 For the first time I just submitted a proposal for a new (small) feature in #django ; it's related to #fulltextsearch in #postgresql , especially for non-English websites/webapps . You can use Github reactions to let me know what you thi
Is there such a thing as using too many #hashtags in #Mastodon or in the #fediverse in general? I guess if you are doing it on every word that might be considered #spam or could violate your instance's rules. Perhaps I am worried over #neti
I have noticed that a while ago, several new Postgres extensions regarding text search have surfaced that all use BM25. Obviously if you read their documentation each one is the ultimate solution to all text search problems. Is anyone aware
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/fulltextsearch