#bithack
Live, measured metrics for the hashtag #bithack from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bithack
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 07:02 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 07:02 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 07:02 UTCEverything below is measured over the latest 3 public posts (spanning ~8470 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 2.7
Used together with
Top of the latest posts
Since @lritter mentioned a favourite #bithack yesterday, I'm inspired to mention mine. I once had to calculate the mean, rounded down, of two 32-bit integers, in _original_ Thumb assembler, avoiding integer overflow. In _Arm_ asm it's easy:
Here's an informal and (hopefully simple to understand) by-example derivation of "next larger integer with same popcount" implementation that saturates to known when none exists. From there builds "closest smaller integer", "at runtime sele
My insufferable brain keeps repeating to me (for the past week) that if 'x' has popcount 'p' then bit_gather(~0,x) is the integer with the lowest 'p' bits set. Maybe this post will make it stop. (edit: PEXT on intel) #bithack #popcount
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/bithack