#NimSkull
Live, measured metrics for the hashtag #NimSkull from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nimskull
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 18:18 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 18:18 UTCNo related tags with measured usage found for #nimskull.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 18:18 UTCEverything below is measured over the latest 6 public posts (spanning ~886 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.2
Used together with
Top of the latest posts
So, well, I gave rust another chance earlier in the year, so I was thinking why not give go another chance as well. I'm not quite convinced by this, it's probably quite weird code as I'm not used to writing go, mostly writing #nimskull It j
I was having a small interaction with the #nimskull people last week, and they were very informative and had some good explanations of things in their issue, I really enjoyed it and it makes me feel even more like this is a great project :)
This was a really fun one, and one where I could work without having to know some fancy arguement before. We get a set of rules, and some objects and have to find out which objects are accepted. So we have some parts of this, first parsing
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/nimskull