#epiverse
Live, measured metrics for the hashtag #epiverse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #epiverse
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 07:39 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 07:39 UTCNo related tags with measured usage found for #epiverse.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:39 UTCEverything below is measured over the latest 40 public posts (spanning ~9673 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (38) · French (2)
Avg boosts / post: 2.9
Top of the latest posts
New #epiverse #rstats blog post! "Lesser-known reasons to prefer apply() over for loops" https://epiverse-trace.github.io/posts/for-vs-apply/ The debate on for loops vs apply() often crystallizes around (misconceptions on) performance. But
How come you generally don't have to think about installing system dependencies when testing #rstats packages in the cloud (e.g., on GitHub Actions)? 🤔 Short answer: it's because the pak package 📦 is doing some amazing magic behind the sc
I love these interdisciplinary One Health projects that span topical and methodological expertise. My main contribution to this work was the development of a multinomial GAMM to jointly model the circulation dynamics and epidemiology of the
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/epiverse