#Esqueleto
Live, measured metrics for the hashtag #Esqueleto from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #esqueleto
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-28 15:19 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-28 15:19 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 15:19 UTCEverything below is measured over the latest 12 public posts (spanning ~49458 hours).
Posting hours (UTC) — busiest: 16:00
Languages: Spanish (7) · English (2) · Dutch (1)
Avg boosts / post: 1.3
Top of the latest posts
Los cráneos de los búhos son asimétricos, pues sus oídos están posicionados a distinta altura. Así, el sonido llega antes a uno que al otro y le permite situar mejor la fuente. #aves #birds #huesos #bones #esqueleto #skeleton
Estar muerto no es excusa para no hacer nada 💀 #fallout4 #short #gameplay #esqueleto #zurt https://youtube.com/shorts/4G-r-2vsl3M?feature=shared
Isn't it perplexing to see someone eagerly writing raw SQL when they could have used a type-safe embedded domain-specific language such as Esqueleto in Haskell? Why does anyone want to give up on composability and bug-checking? #SQL #eDSL #
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/esqueleto