#memorysafety
Live, measured metrics for the hashtag #memorysafety from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #memorysafety
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-11-12 05:56 UTC1 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-11-12 05:56 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-12 05:56 UTCEverything below is measured over the latest 40 public posts (spanning ~3011 hours).
Posting hours (UTC) — busiest: 03:00
Languages: English (37) · Japanese (2) · German (1)
Avg boosts / post: 1.8
Top of the latest posts
The recording (and transcript, for the sensible people who don't want to listen to me speaking) of my March QCon talk is online! If you want to understand how CHERI works and the relationship between memory safety and compartmentalisation,
David Chisnall (*Now with 50% more sarcasm!*)@[email protected]♥ 34↻ 242026-08-13 08:46 UTCView post →The German Federal Office for Information Security (@bsi) and the Sovereign Tech Agency are endorsing the statement “Improving Europe's cybersecurity posture through #memorysafety,” which calls for more support for the large-scale adoption
It's great to see both the Sovereign Tech Agency and the German Federal Office for Information Security (BSI) supporting the call for #MemorySafety incentives in EU cybersecurity policies! Read more about their vision here: https://www.sove
#memorysafety across platforms
every network with a public tag surfaceFollow #memorysafety straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/memorysafety