#insecurebydesign
Live, measured metrics for the hashtag #insecurebydesign from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #insecurebydesign
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 21:51 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 21:51 UTCNo related tags with measured usage found for #insecurebydesign.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 21:51 UTCEverything below is measured over the latest 14 public posts (spanning ~50493 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (7)
Avg boosts / post: 0.9
Top of the latest posts
@sammachin For #homeassistant, sparkling design beats security every time. github.com/home-assistant/core/issues/105226 @homeassistant @frenck #insecurebydesign #security #privacy
Fun times, if I'm reading this right #minio decided to stop publishing new docker images one day before releasing their CVSS 8.8 privilege escalation. I understand the VC's want their money back but making it hard for people to do security
Of all the problems with email campaign HTTP redirects, one of the most annoying is the prevalence of insecure links, i.e. http:// I think this may account for 98.3% of all HTTP traffic outside the great firewall of China. From: <verizon-no
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/insecurebydesign