#0x20

Live, measured metrics for the hashtag #0x20 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #0x20

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.

$2,449.80/ year · 4-character #name
Claim #0x20 — $2,449.80/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
4
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 4
0.3
Avg reactions / post
Mastodon · last 4

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 11:44 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 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 11:44 UTC
#binrev0x20
0 uses · 0 accounts / 7d
#0x20leaks
0 uses · 0 accounts / 7d
#x20e0
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 11:44 UTC

Everything below is measured over the latest 4 public posts (spanning ~51087 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (3) · Polish (1)

Avg boosts / post: 0.3

Top of the latest posts

  • OK so ELR_EL3 is 0xe005a98 which is inside __dl___memmove_aarch64 "ldp x10, x11, [x4, #0x20]. I think this is the address the exception would resume at, which means the *previous* instruction generated the fault. That's ldp x8, x9, [x1, #0x

    Andrew Zonenberg@[email protected]♥ 1↻ 02025-11-29 12:48 UTCView post →

  • @helge For reference, in case it can help anyone else, putting a breakpoint in `init(0` and looking at the closest couple of stack frames, you'll see an entry like this: #2 0x000000010063df94 in implicit closure #2 in implicit closure #1 in

    Rick@[email protected]♥ 0↻ 02024-01-11 00:29 UTCView post →

  • Zwiększona odporność na fałszowanie DNS przez kodowanie bitu 0x20 ( https://nfsec.pl/security/6131 ) #dns #security #0x20

    Patryk Krawaczyński@[email protected]♥ 0↻ 12023-07-15 18:23 UTCView post →

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/0x20