#contactbook
Live, measured metrics for the hashtag #contactbook from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #contactbook
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 16:47 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 16:47 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:47 UTCEverything below is measured over the latest 3 public posts (spanning ~605 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Top of the latest posts
I cleaned up this thread about decentralized contact book in a blog post here: https://blogue.narf.ca/2023/09/federated-contact-book/ I'm very open to receiving feedback. What is preventing this from existing? This is a old problem; why don
I wish there would be a way to share that workload. If each of us maintain our own contact infos and make sure to keep it up to date, just like we did on Facebook back in the days, then that's a lot less duplicated efforts! In a group of 10
Each of us has the burden of maintaining our contact books. That's a lot of duplicated efforts! In a group of 10 people, each of us as to maintain 9 contacts. That's 10 x 9 = 90 duplicated efforts! #decentralizedContacts #contactBook
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/contactbook