#ConstantTime
Live, measured metrics for the hashtag #ConstantTime from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #constanttime
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 22:29 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 22:29 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 22:29 UTCEverything below is measured over the latest 4 public posts (spanning ~35790 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1.3
Top of the latest posts
@MishaVelthuis : there may be a delay because humans prefer analysing higher level source code. OTOH, with my very limited knownledge of AI/LLM's, I bet that reverse engineering software (such as IDA Pro, https://en.wikipedia.org/wiki/Inter
Security is hard. The TL;DR is: Do not lose possesion of your private key. Addendum: This is from a year ago to be clear. But, there are many people that have older Yubikeys that Can Not be fixed. https://ninjalab.io/eucleak/ The attack req
While this is a low threat, it could have been defended against at basically no cost. hXXps://research.kudelskisecurity.com/2017/01/16/when-constant-time-source-may-not-save-you/ https://arstechnica.com/security/2024/09/yubikeys-are-vulnera
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/constanttime