#nanostores
Live, measured metrics for the hashtag #nanostores from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nanostores
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-30 09: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 · fosstodon.org (Mastodon public search API) · fetched 2026-07-30 09:55 UTCNo related tags with measured usage found for #nanostores.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 09:55 UTCEverything below is measured over the latest 4 public posts (spanning ~8963 hours).
Posting hours (UTC)
Languages: English (3) · Italian (1)
Avg boosts / post: 0
Top of the latest posts
After spending the whole day reversing @sitnik_en's logux, I finally figured out how they solve the problem of the log store. They don’t, lol. There are some mentions of Redis in the commercial version, though. I spent a bit too much time o
#Nanostores feels technologically better but the documentation is so bad that I just have to read the source. This is the second frontend library where I stumble on absolutely abysmal docs (first one's datascript) made in Russia. Were there
I’ve reached enough complexity in my hobby app where valtio becomes a liability. Having a single global mutating state felt weird and yeah, it scales weird. The question is, of course, what lesson did I learn? Probably that cljs had extreme
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/nanostores