#zip64
Live, measured metrics for the hashtag #zip64 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #zip64
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 14: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 14:46 UTCNo related tags with measured usage found for #zip64.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:46 UTCEverything below is measured over the latest 5 public posts (spanning ~18427 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Top of the latest posts
I would rather NOT rewrite our .zip archive code to do the «unpack in separate directory and then remove» thing. So does anybody know of a different C++ library to access zip archive contents directly that DOES support #Zip64? #askFedi #fed
Oh well that's just peachy. #EUMETSAT switched to #Zip64 for its zipped data archives even when standard zip worked fine (I assume for consistency with situations where it didn't?), and #Zipios, the C++ library we're using to access the fil
#libzip 1.11.4 has been released (#LZMA / #ZIP / #Zip64 / #zstd / #Zstandard / #bzip2 / #AES / #PKWARE / #FileArchiver / #DataCompression) https://libzip.org/
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/zip64