#JHOVE
Live, measured metrics for the hashtag #JHOVE from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jhove
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-30 05:41 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-30 05:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 05:41 UTCEverything below is measured over the latest 40 public posts (spanning ~25702 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (35) · French (5)
Avg boosts / post: 1.4
Top of the latest posts
🚀 #JHOVE 1.34 is here! This update has fixed JPEG2000 codestream parsing, added support for PDF-2. Headers, and has better validation of document info dates for PDFs. Read more release notes here: https://openpreservation.org/news/jhove-1-
Incredible investigative #digipres blog on the #OPF website. We are so grateful this has been shared this with us! Do you have a file that won't render in Adobe Reader, but is deemed valid by validation tools like #JHOVE? Read to see how @B
Hey #digipres & #jhove specialists! I can't understand why TIFF-hul-61 is an error (https://github.com/openpreserve/jhove/wiki#tiff-hul-61). Value 6 for Compression is JPEG. But the TIFF 6.0 specification includes it as a valid compression
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/jhove