#Itemsys
Live, measured metrics for the hashtag #Itemsys from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #itemsys
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-27 12:09 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-27 12:09 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:09 UTCEverything below is measured over the latest 5 public posts (spanning ~1764 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.6
Top of the latest posts
More work towards a functional #FoundationOS #Itemsys -based syscall interface. After a lot of work redoing the data structures behind items and actors (Unix: files and processes), I got the (currently userspace) kernel starting again, and
Working on item interface methods for inserting, deleting, and clearing data in item byte arrays. [Unix terminology approximation: working on syscalls for file truncation and more] The first idea was: Delins(offset uint64, delete_count, ins
#Itemsys #FoundationProject What I'm working on presently is issues with item driver singletons. Foundation allocates one item driver per open item. When an item tries to open another item at a given path, the system will start the driver p
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/itemsys