#JScontact
Live, measured metrics for the hashtag #JScontact from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jscontact
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-28 02:59 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-28 02:59 UTCNo related tags with measured usage found for #jscontact.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 02:59 UTCEverything below is measured over the latest 4 public posts (spanning ~52133 hours).
Posting hours (UTC)
Languages: French (2) · English (2)
Avg boosts / post: 0.8
Top of the latest posts
RFC 9982: JSContact Version 2.0: A JSON Representation of Contact Data Voici la version 2 du format de représentation d'entités #JSContact. En fait, ce numéro de version est trompeur, il n'y a qu'un seul changement, le membre uid qui était
I just found out that the @ietf recently published JSContact yet another specification for storing contact data. It’s super interesting, though, and I am falling down the rabbit hole of all the links and related information about this. 👀 O
RT @[email protected] Plus d'informations sur #JMAP, #JSContact et #JSCalendar: https://jmap.io/ #IMAP #CardDAV #CalDAV #VCard #iCalendar #WebDAV https://twitter.com/LaMouetteODF/status/1576547767371337728
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/jscontact