#notifysend
Live, measured metrics for the hashtag #notifysend from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #notifysend
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-31 12:24 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-31 12:24 UTCNo related tags with measured usage found for #notifysend.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-31 12:24 UTCEverything below is measured over the latest 2 public posts (spanning ~0.7 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
The script uses #notifySend to inform the user to which state the iio-sensor-proxy is altered to (enabled or disabled). Otherwise it would be guessing for the user if anything changed, and what the current setting is 🤔 Maybe I should uploa
I'm so close to next step with #autorotate_sam but sometimes you run into snags you wouldn't expect (at least on #NixOS ). Apparently with #NotifySend you can have the "connection" being "closed" when you run the script as root, therefor as
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/notifysend