#sntpclock
Live, measured metrics for the hashtag #sntpclock from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sntpclock
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-27 23:53 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-27 23:53 UTCNo related tags with measured usage found for #sntpclock.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:53 UTCEverything below is measured over the latest 2 public posts (spanning ~20882 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
@ska @zwol Indeed. One can get away with SNTP and a simple tree rather than more complex NTP more often than not in simple SoHo setups. Although the Windows hourly poll interval is actually a good practical choice. I experimented with daily
I have clarified the sntpclock manual slightly. This will be in the next release. http://jdebp.info/Softwares/djbwares/guide/commands/sntpclock.xml #djbwares #sntpclock
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/sntpclock