#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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 07:32 UTC6 uses by 6 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 07:32 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:32 UTCEverything below is measured over the latest 40 public posts (spanning ~4999 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (40)
Avg boosts / post: 0.9
Top of the latest posts
Check out "Low Level Software Security for Compiler Developers", an open source book. Looks good, systematic - not only for compiler developers but anyone interested in infosec and cyber. I wished I had known this last time I was asked abou
This week on #OpenSourceSecurity I chat with @djc and @ctz about #Rustls. A lot has happened with Rustls in the last few years (and there's a lot more to come). Writing a TLS implementation is incredibly complicated, even when you don't hav
People often claim that memory-safe languages eliminate the class of memory bugs, but that is not true and can give less experienced devs a false sense of security. You can violate borrow checker at runtime in Rust with zero unsafe blocks.
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