#ntpd
Live, measured metrics for the hashtag #ntpd from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ntpd
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 12:21 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 12:21 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:21 UTCEverything below is measured over the latest 26 public posts (spanning ~58873 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (20) · German (2) · Spanish (1) · French (1)
Avg boosts / post: 0.5
Top of the latest posts
NTP in practice. Mostly it works. Time to time it's like 8 hours off. Internet connection is working. I already debugged unreliable NTP once and replaced the unreliable "ntp" NTP daemon with much more reliable "chrony" NTP daemon. But still
ntpd_sync_on_start – missing from bsdconfig(8) in FreeBSD. A bug? bsdconfig startup_rcvar #FreeBSD #ntpd #date #time #bug
Secure time synchronization with NTS To set the correct time on computers, usually NTP (Network Time Protocol) is used. However NTP is an insecure time synchronization protocol and allows a man-in-the-middle to shift time on an NTP client.
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/ntpd