#COLRv1
Live, measured metrics for the hashtag #COLRv1 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #colrv1
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 19:28 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 19:28 UTCNo related tags with measured usage found for #colrv1.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 19:28 UTCEverything below is measured over the latest 10 public posts (spanning ~30898 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 2.2
Top of the latest posts
Variable #COLRv1 fonts are now supported in the latest Chrome 108! https://developer.chrome.com/blog/new-in-chrome-108/#colrv1-support
I had to check this out myself. Customising COLRv1 fonts in Affinity 3.2 Everyone, please have a very colourful and fine day! #Affinity #COLRv1 Cc: @justvanrossum @typearture
So I was trying to detect browser support for COLRv1 font palettes. I thought this would work: .colrv1-supported-area { display: none; } @supports (font-palette: --1) { .colrv1-supported-area { display: block; } } But it does not. The .colr
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/colrv1