#woff
Live, measured metrics for the hashtag #woff from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #woff
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 · mastodon.online (Mastodon public tags API) · fetched 2026-07-27 20:15 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-27 20:15 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 20:15 UTCEverything below is measured over the latest 23 public posts (spanning ~40684 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (11) · French (8) · Japanese (1) · German (1) · Luxembourgish (1) · Welsh (1)
Avg boosts / post: 0.2
Top of the latest posts
@jecture nodds in agreement the correct way is to use CSS and define a WebFont instead, so that any Browsers that can will render it properly, and those that can't (or setup not to) will render it as normal text instead. Cuz accessibility i
7- and 14-segment fonts "DSEG" https://www.keshikan.net/fonts.html #ycombinator #フリーフォント #7セグメント #14セグメント #7SEG #14SEG #デジタル数字 #デジタル時計 #LED #7SEGG_CHAN #TTF #WOFF #JavaScript
Dear #LazyWeb: Is there still a good reason to have separate "Web Font" file formats vs Desktop? Like, if I can load an OTF font in my CSS, what purpose does this distinction serve? Is this just standards proliferation, or some sort of para
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/woff