#d0d0d0
Live, measured metrics for the hashtag #d0d0d0 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #d0d0d0
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 · mas.to (Mastodon public tags API) · fetched 2026-10-12 06:39 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-12 06:39 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-12 06:39 UTCEverything below is measured over the latest 5 public posts (spanning ~26312 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Top of the latest posts
@revk Messing around a bit; #d0d0d0 for text colour causes less ghosting and meets WCAG AA requirements. All options but #ffffff fail wcag AAA though as that's only 7.68:1 which is just over the threshold (7:1)
For the "it's the law tho" crowd, here's a fix: APCA to WCAG 2 Backwards Compatibility Chart For 4.5:1 Backwards 4.5:1 is achieved when: IF the lightest color is darker than #d0d0d0 OR the darkest is darker than #595959 THEN Lc ±60 exceeds
Base Color : E05D83 Mode : monochrome-dark #9D2145 #B5254F #CD2959 #D83A68 #DD517A #A6A6A6 #B4B4B4 #C2C2C2 #D0D0D0
#d0d0d0 across platforms
every network with a public tag surfaceFollow #d0d0d0 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/d0d0d0