#base60
Live, measured metrics for the hashtag #base60 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #base60
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-28 18:57 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-28 18:57 UTCNo related tags with measured usage found for #base60.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 18:57 UTCEverything below is measured over the latest 4 public posts (spanning ~17323 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1.5
Top of the latest posts
@acsawdey @foone noooo no no, not arbitrary 😂 you gotta have highly composite numbers Each base-60 digit requires six bits, with a wastage of four redundant values (per every power of 60) Now you could use that for error correction, or som
This fine paper is free. The whole issue is also available to download, free. https://www.sciencedirect.com/science/article/pii/S0315086017300691#se0120 #Archaeology #Ancient #Babylonian #History #Babylon #Trigonometry #Base60 #Archeology #
Can you image if clocks (which use base 60 numbers) would display the time in base60 -> IE: It's 16:15:00 UTC which would be G:F:0 UTC in base60 I need to head to the store - it's GF LOL. Yeah I can see why that wouldn't have taken off. #Ti
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/base60