#aiocoap
Live, measured metrics for the hashtag #aiocoap from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #aiocoap
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-27 14:55 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 14:55 UTCNo related tags with measured usage found for #aiocoap.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 14:55 UTCEverything below is measured over the latest 12 public posts (spanning ~23872 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (12)
Avg boosts / post: 0.3
Top of the latest posts
We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet.
Development of aiocoap, my Python CoAP library, is approaching its next breaking release. If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, eit
Thanks to @pyodide and @ProjectJupyter, using #CoAP is becoming more accessible: The latest version of the #aiocoap documentation has examples that can be run directly from the documentation, and access CoAP peers through a WebSocket-to-UDP
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/aiocoap