#itakom_conf
Live, measured metrics for the hashtag #itakom_conf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #itakom_conf
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 22: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 22:41 UTCNo related tags with measured usage found for #itakom_conf.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 22:41 UTCEverything below is measured over the latest 8 public posts (spanning ~64 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 1.3
Used together with
Top of the latest posts
The ITAKOM site is now giving an error message saying that it can’t cope The organisers have also just acknowledged the problem via the conference app: ‘Our apologies to online delegates for the problems we are experiencing; we are working
Keeping the rest of my toots about #itakom_conf over on @[email protected] (I’ll try to use the hashtag if you’re interested in following along) Not at the venue yet – hoped to stream the first session of interest, but techn
From glancing at the … ahem … tweets shared in the ITAKOM app, it looks as though online conference participants are having trouble connecting (it’s not just me) I have trouble connecting with *reality* at such an early hour, so thought I m
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/itakom_conf