#utf16le
Live, measured metrics for the hashtag #utf16le from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #utf16le
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-27 13:34 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-27 13:34 UTCNo related tags with measured usage found for #utf16le.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:34 UTCEverything below is measured over the latest 3 public posts (spanning ~5979 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Top of the latest posts
Preparing to dive into the arcane world of #git, #utf8, #utf16le, and #BOM. If you don’t hear from me, send a search party. Why does Windows make working with text so hard?
Released v0.6.1 just fixing one stupid little regression from refactoring: The terminfo writer must never be used when output does *not* go to stdout 🙈 So far so good, I just thought there was yet another bug, testing redirected output on
New pre-release of dos2ansi: v0.2 * Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached * Selectable input #codepage (so far only #cp437, #cp850 and #cp858) * Selectable output format, #utf8, #utf16 or #utf16le, with or wi
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/utf16le