#ntpdate
Live, measured metrics for the hashtag #ntpdate from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ntpdate
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 13:33 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 13:33 UTCNo related tags with measured usage found for #ntpdate.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:33 UTCEverything below is measured over the latest 5 public posts (spanning ~50032 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Top of the latest posts
Remember ntpdate? If you run BSD it's there still https://man.freebsd.org/cgi/man.cgi?ntpdate It was also standard in my Linux distribution of Mandrake / Mandriva & early Debian For reasons unknown I don't see it anymore. I just needed to i
saving this for later $ sudo service ntp stop $ sudo ntpdate -s time.nist.gov $ sudo service ntp start #linux #ntpdate
Local #FreeBSD (v14.3-RELEASE) "/etc/rc.conf" has ... ntpd_enable="YES" ntpd_sync_on_start="YES" ... which did not make "ntpd(8)" to run due to "clock offset exceeds panic threshold" with any of: cold boot; "exit" after "shutdown now"; "ser
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/ntpdate