#jpegxl
Live, measured metrics for the hashtag #jpegxl from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jpegxl
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-29 21:33 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-29 21:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 21:33 UTCEverything below is measured over the latest 40 public posts (spanning ~4607 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (29) · German (6) · Italian (2) · Russian (1) · French (1)
Avg boosts / post: 0.7
Top of the latest posts
With the speed around #JpegXL picking up (now in #Firefox and #Chrome nightlies), I'm wondering what good use of an #HTML srcset would be there. As JXL's progressive compression is good, we don't need different files in the srcset (so there
Progress in #Firefox for #JpegXL: While the latest nightly for Android still needs image.jxl.enabled=true in about:config, it now renders https://jpegxl.info/resources/jpeg-xl-test-page.html without any visible errors. One day…
Mozilla enabled JPEG-XL support in Firefox nightly. https://hg-edge.mozilla.org/integration/autoland/rev/38c3fcb6e06d #mozilla #firefox #jpegXL
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/jpegxl