#x264
Live, measured metrics for the hashtag #x264 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #x264
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 20:46 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 20:46 UTCNo related tags with measured usage found for #x264.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:46 UTCEverything below is measured over the latest 27 public posts (spanning ~51865 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (22) · German (3) · American English (1)
Avg boosts / post: 0.7
Top of the latest posts
"[...] feel free to hang out in #x264 where we discuss a wide variety of topics that are, in fact, totally x264-related like touhou and starcraft [...]" https://wiki.videolan.org/X264asm/The English equivalent of "Is it #anime? How do I pat
Trying to setup #Radarr and #Sonarr to stick to #x264 because my relatives have shit systems and wow, simply being able to choose your codec would be so much easier than the byzantine nightmare they have implemented
I have a weird behaviour of #ffmpeg on #NetBSD: when transcoding a video (either from an existing video or from still frames, doesn't matter) with #x264, everything is fine. But when I encode with #x265, the ffmpeg process sets itself to ni
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/x264