#passwordpolicyfail
Live, measured metrics for the hashtag #passwordpolicyfail from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #passwordpolicyfail
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-10-01 04:52 UTC0 uses by 0 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-10-01 04:52 UTCNo related tags with measured usage found for #passwordpolicyfail.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-01 04:52 UTCEverything below is measured over the latest 3 public posts (spanning ~30975 hours).
Posting hours (UTC)
Languages: English (2) · German (1)
Avg boosts / post: 0.3
Top of the latest posts
Small rant about #passwordpolicyfail at #renfecercanias (Spanish rail division for suburban trains). So I installed Cercanías' Android app today, and this is what happened when trying to set up my account: 1. Using my email / password from
@dumbpasswordrules For context using a combination of 8 letters and numbers (Lloyds bank's minimum requirement) a Lloyds bank account can be hacked in roughly 2 minutes! If the average Lloyd's bank customer chooses an 11 character password
This is not a good sign, I expect 50 on the low end for maximum password length #passwordpolicyfail
#passwordpolicyfail across platforms
every network with a public tag surfaceFollow #passwordpolicyfail 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/passwordpolicyfail