#zephyr
Live, measured metrics for the hashtag #zephyr from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #zephyr
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:24 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:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:24 UTCEverything below is measured over the latest 40 public posts (spanning ~3615 hours).
Posting hours (UTC) — busiest: 22:00
Languages: English (32) · German (4) · Russian (2) · French (1)
Avg boosts / post: 1
Top of the latest posts
My @igalia colleague Ricardo Cañuelo has just published a very interesting step-by-step guide on the design and implementation of a technical demo of his work on #Zephyr. Check it out! https://blogs.igalia.com/rcn/posts/20260317-why_dont_we
And now I have a choice to make... do I rewrite the stm32c5x.c handling of flash erase for #Zephyr to properly account for the EDATA flash (starting at 0x0840 0000), or just "lose" 64K of flash on the chip? So weird that ST submitted the co
I really need to work out a better way to include libraries into #Zephyr applications. My current setup (using projects in a West manifest, and then a bunch of CMake mumbo-jumbo feels wrong). Perhaps using FetchContent?
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/zephyr