#pla9
Live, measured metrics for the hashtag #pla9 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pla9
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-29 21:41 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-29 21:41 UTCNo related tags with measured usage found for #pla9.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 21:41 UTCEverything below is measured over the latest 3 public posts (spanning ~0 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
Once I feel that I am compliant (not many calls to implement) I will then get a Plan9/9front machine setup in (what I hope to be) my new lab (in the garage, like a true chad). (Gangsta Glenda courtesy of: https://fqa.9front.org/fqa1.html#1.
Currently, for now, I am testing by letting v9fs (the 9p driver in the Linux kernel), generate the traffic that I need to decode. This is useful because once I get the Tattach/Rattach done then I should be able to get to the more common I/O
As part of my introduction to Plan 9 I decided the best way to start in a more comfortable environment would be to implement a 9P protocol decoder (with a state machine), encoder and then a high-level client/server framework. #9front #pla9
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/pla9