#m1s
Live, measured metrics for the hashtag #m1s from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #m1s
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:27 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:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 06:27 UTCEverything below is measured over the latest 2 public posts (spanning ~13023 hours).
Posting hours (UTC)
Languages: Russian (1) · English (1)
Avg boosts / post: 0
Top of the latest posts
Изучаем RISC-V с платой Sipeed M1S Наконец-то появилось время и желание пощупать и опробовать в деле давно купленную отладку от Sipeed на базе RISC-V SoC BL808. Попутно я решил собрать материал по теме и поделиться с читателями своим опытом
Really intrigued by the tiny multi-CPU + AI-acceleration #IoT boards that seem to be hitting the market, e.g. the #0x64 (https://wiki.pine64.org/wiki/Ox64) from @PINE64 and the #M1s from #Sipeed, both of which use the same #RISCV SoC. The M
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/m1s