#websecurity
Live, measured metrics for the hashtag #websecurity from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #websecurity
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-09-10 23:03 UTC12 uses by 11 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-09-10 23:03 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-10 23:03 UTCEverything below is measured over the latest 40 public posts (spanning ~877 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (38) · Greek (2)
Avg boosts / post: 0.4
Top of the latest posts
New write-up: Reading JS Files Like an Attacker: Three Sources Still Worth Knowing My earlier DOM XSS articles focused primarily on sinks. This time I'm looking at the other half of the equation: Source → Sink I cover: • document.referrer •
Does an encrypted as well as signed web token make sense? Clearly, why are these almost none? Clearly, signed are unchangeable but also via HTTPS they say a lot about the user what (depending on the). It is not about security but about conf
New zero-day in WordPress? SafeLine WAF auto-blocks it—no signature update needed. Self-hosted, open source, trusted by 18,000+ security teams. SQLi, XSS, RCE? Neutralized. Your server, your data. Get 5% off: https://www.valtersit.com/deals
#websecurity across platforms
every network with a public tag surfaceFollow #websecurity 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/websecurity