#SecurityBytes
Live, measured metrics for the hashtag #SecurityBytes from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #securitybytes
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 00: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-28 00:46 UTCNo related tags with measured usage found for #securitybytes.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 00:46 UTCEverything below is measured over the latest 7 public posts (spanning ~198 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 3.4
Top of the latest posts
In the 4th post on Least Privilege, I go into more detail on best practice & technologies for implementation of Least Privilege. As always, curious to know your reactions, opinions & insights. https://cirriustech.co.uk/blog/secbytes-least-p
My #SecurityBytes blog series starts with Least Privilege, why it matters, why it’s not consistently enforced & how as an industry we can make things better. First up, some history of admin privileges to set the scene #InfoSec #CyberSec #Le
In this, the 3rd post on the topic of Least Privilege, I look at how you might implement Least Privilege and what the challenges are that meant that many organisations may struggle to do so. https://cirriustech.co.uk/blog/secbytes-least-pri
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/securitybytes