#BabbleSim
Live, measured metrics for the hashtag #BabbleSim from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #babblesim
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 06: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-28 06:31 UTCNo related tags with measured usage found for #babblesim.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 06:31 UTCEverything below is measured over the latest 3 public posts (spanning ~13793 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 1.7
Used together with
Top of the latest posts
Started playing with #BabbleSim integration in @zephyr for @zmk. Got the basics working, so I can actually simulate and test all our BLE code like we do right now for our behavior code. Going to be a huge help as I work on this refactor to
This week, I'm once again reminded of how awesome the POSIX support in @zephyr is for development, especially combined with the #BabbleSim support. I was able to add several integration tests that fully exercise our #bluetooth split support
Ok, so #BabbleSim integration in @zephyr is *really* cool. PR up for @zmk to add some BLE integration tests leveraging it, as preparation for the upcoming State Machine Framework refactor I have planned for that code: https://github.com/zmk
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/babblesim