#lightclock
Live, measured metrics for the hashtag #lightclock from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lightclock
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-11-14 13:11 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-11-14 13:11 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-14 13:11 UTCEverything below is measured over the latest 2 public posts (spanning ~262 hours).
Posting hours (UTC)
Languages: German (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
Special Relativity: When you move a clock, it is slower as when it just sits there. When stopped, it runs with the normal speed again. (All relative to the non-moving observer.) How's that? There are explanations out there, but wrote it dow
How does the Twin Paradox work in Special Relativity? There are gazillion more or less correct and useful descriptions out there. Everyone has their preferred one. Like in University many years ago, I grok things best if I describe them in
#lightclock across platforms
every network with a public tag surfaceFollow #lightclock straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/lightclock