#chrony

Live, measured metrics for the hashtag #chrony from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #chrony

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.

$520.70/ year · 6-character #name
Claim #chrony — $520.70/yr→
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
38
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 38
0.5
Avg reactions / post
Mastodon · last 38

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 08:07 UTC
0
07-21
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

0 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 08:07 UTC
#chronyd
0 uses · 0 accounts / 7d
#chronyntp
0 uses · 0 accounts / 7d
#chronyc
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:07 UTC

Everything below is measured over the latest 38 public posts (spanning ~64975 hours).

Posting hours (UTC) — busiest: 07:00

00:0012:0023:00

Languages: English (25) · German (7) · Chinese (Taiwan) (2) · Russian (1) · Portuguese (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

    @[email protected] has moved@[email protected]♥ 4↻ 12026-01-21 18:39 UTCView post →

  • Needed an #NTP server on a Raspberry Pi. To keep it light, I chose #OpenNTPD. Not a great idea. If your clock is off by more than 180 seconds, it won't adjust it; logs say adjtime failed: Invalid argument Now, according to the man page, it

    scy@[email protected]♥ 3↻ 32026-03-02 21:29 UTCView post →

  • Made progress on packaging #ntpd_rs by @trifectatech for @gentoo : ✅ proper hermetic Rust build ✅ cooked up OpenRC init scripts ✅ runs unprivileged as ntp:ntp ✅ operational #prometheus metrics exporter ✅ man pages Still a few rough edges bu

    Holger Hoffstätte@asynchronaut♥ 3↻ 12025-12-01 22:40 UTCView post →

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/chrony