#ranges
Live, measured metrics for the hashtag #ranges from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ranges
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:15 UTC1 uses by 1 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:15 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:15 UTCEverything below is measured over the latest 40 public posts (spanning ~22358 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (34) · Russian (5) · Chinese (Taiwan) (1)
Avg boosts / post: 0.5
Top of the latest posts
AoC day 5. Part 1 was straightforward; the naive solution that checks every ID against every range is plenty fast. For part 2 I went with a three-step approach: Read provided ranges, merge adjacent/overlapping ranges, sum up the remaining (
C++20 ranges support piping collections into filter and transform, but sort has no native pipe syntax. This episode of Qt Widgets and more builds a pipeable sort implementation from scratch. Topics covered: - Why sort doesn't pipe natively
I just tagged stable v15 of the strong_type library for C++14 and higher. * CMake package is now ARCH_INDEPENDENT, as it should be. Thanks Patrick Kappl for the fix. * strong::range is much reworked and now compatible with std::ranges. Most
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/ranges