#lossy
Live, measured metrics for the hashtag #lossy from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lossy
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 07:27 UTC2 uses by 2 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 07:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:27 UTCEverything below is measured over the latest 17 public posts (spanning ~46848 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (16)
Avg boosts / post: 0.5
Top of the latest posts
@OpenComputeDesign Remember when we were talking about #audio #lossy #compression earlier? This is NUUUUUTS: https://bellard.org/tsac/
R.L. Dane :Debian: :OpenBSD: :FreeBSD: 🍵 :MiraLovesYou:@[email protected]♥ 1↻ 02025-10-01 17:37 UTCView post →Since the #PNG spec is getting some updates, I was thinking... you know what would be sick? Baking classic #lossy compression right into PNG. I don't mean #JPEG or anything like that. Not even the #LossyPNG scheme I enjoy using where I redu
R.L. Dane :Debian: :OpenBSD: :FreeBSD: 🍵 :MiraLovesYou:@[email protected]♥ 1↻ 02025-07-07 17:00 UTCView post →Exploring Hidden JPEG Features https://fed.brid.gy/r/https://hackaday.com/2026/07/24/exploring-hidden-jpeg-features/
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/lossy