#HexRays
Live, measured metrics for the hashtag #HexRays from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hexrays
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 · mastodon.online (Mastodon public tags API) · fetched 2026-11-01 01: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 · mastodon.online (Mastodon public search API) · fetched 2026-11-01 01:57 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-01 01:57 UTCEverything below is measured over the latest 40 public posts (spanning ~29886 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (39) · Basque (1)
Avg boosts / post: 1
Top of the latest posts
Has anyone else ever run into this #hexrays glitch? It seems to struggle with the stack frame on these functions in a MSVC2008 built binary with SEH. The prologue of the function seems to combine a traditional ```push ebp sub esp, <size>```
IDA 9.4 Beta 1 has been published (with some features of my own on it): https://docs.hex-rays.com/release-notes/9_4beta #hexrays
Meanwhile #IDA Pro: "Oops! internal error 1783 occurred." #idapro #reverseengineering #hexrays #gdbserver #qemu
#hexrays across platforms
every network with a public tag surfaceFollow #hexrays 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/hexrays