#base64
Live, measured metrics for the hashtag #base64 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #base64
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 · mastodon.online (Mastodon public tags API) · fetched 2026-07-27 11:49 UTC2 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-27 11:49 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 11:49 UTCEverything below is measured over the latest 40 public posts (spanning ~9363 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (33) · Russian (3) · Chinese (Taiwan) (2) · Lithuanian (1)
Avg boosts / post: 2
Top of the latest posts
I thought my colleague was an alien who decoded base64 strings on the fly, but he wasn't. It turns out there's a neat little trick to know that you're looking at a base64 encoded JSON object. https://ergaster.org/til/base64-encoded-json/ #s
So yeah, it's official, my #BMW is gone. I'm done with it. I wish it the best of luck, let this bastard ruin some more lives before it hits a trash compactor. Aaaanyway... I think the most logical step would be the next #base64 number after
🔌 base64-cli: Dedicated CLI for base64 encoding and decoding operations 📦 npm 🔗 https://github.com/javimosch/supercli #base64-cli #supercli
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/base64