#pfblocker
Live, measured metrics for the hashtag #pfblocker from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pfblocker
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 · mas.to (Mastodon public tags API) · fetched 2026-07-30 02:01 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-30 02:01 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-30 02:01 UTCEverything below is measured over the latest 4 public posts (spanning ~32431 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
Finally found the time to get #ipv6 going on my #pfsense behind #verizon #fios. That's working and of course, we get another infestation of ads... After some more fine tuning of #pfblocker, happy to say that the exterme test of canyoublocki
Getting a happy medium with #DNSBL on #pfblocker is proving somewhat challenging. The config for the past 6 months at home is to basically block the Steve_ADs list and the malware/phishing ones. Works a treat for me and most devices. Turns
A while back I decided to try #pfBlocker on #pfSense. I just enabled a handful of categories that appeared reasonable for the security of my devices. Today I ran into the first false positive block, and it was an interesting one: infosec.ex
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/pfblocker