#proxmark3
Live, measured metrics for the hashtag #proxmark3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #proxmark3
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-28 18: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-28 18:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 18:33 UTCEverything below is measured over the latest 33 public posts (spanning ~58117 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (29) · German (3) · Russian (1)
Avg boosts / post: 0.4
Top of the latest posts
Last time I tried adding #MQTT support inside the #proxmark3 client I failed and got memory crashes... This time the story is different. #success
So I've been playing with some #RFID for a small project and purchased some cheap "Dual Chip" 13.56khz and 125khz fobs. The LF reads just fine, but the HF is never found on the #proxmark3 Did I just get "single" chip fobs or is there a tric
So, for my birthday, my wife bought me a Proxmark3, which is basically a swiss army knife for all things RFID. She also got me a sweet programmable RFID ring, so that I can carry out my nefarious activities, such as cloning access cards and
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/proxmark3