#utf
Live, measured metrics for the hashtag #utf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #utf
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-11-13 10:56 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-11-13 10:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-13 10:56 UTCEverything below is measured over the latest 40 public posts (spanning ~28948 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (31) · German (4) · Chinese (Taiwan) (3) · French (1) · Polish (1)
Avg boosts / post: 0.7
Top of the latest posts
🆕 blog! “A small collection of text-only websites” A couple of years ago, I started serving my blog posts as plain text. Add .txt to the end of any URl and get a deliciously lo-fi, UTF-8, mono[chrome|space] alternative. Here's this post in
It is again a rainy day so i made an #Unicode #UTF-8 editor on #AmigaOS3... #Amiga and i can convert most used encodage, and i can print tons of funny #emoji with function keys. Thanks #FreeType lib also and linux ttf collection. There is a
Another curious #portability pitfall: #UTF-16, UTF-32, UCS-2 and UCS-4 encoding are byte order dependent. That is, they can either be encoded as big endian or little endian. #Python uses the host byte order when encoding, and writes a Byte
#utf across platforms
every network with a public tag surfaceFollow #utf 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/utf