#0x10

Live, measured metrics for the hashtag #0x10 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 #0x10

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 #0x10 — $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
6
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 6
0.2
Avg reactions / post
Mastodon · last 6

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 14:36 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 14:36 UTC
#FrOSCon0x10
0 uses · 0 accounts / 7d
#0x10x
0 uses · 0 accounts / 7d
#BruCON0x10
0 uses · 0 accounts / 7d
#9n31sbk0l00e03t2ma7g0fj07r1i0o432t1v1u35f0qwx10l611d08a6f0b0q05c0pa660e2bi626t5v1u43f0qwx10n511d03ht_qt_itrajjaazh0e1b7t1v1u62f0qwx10s811d08a0f0b0q00adpfe39e4b761862863bt2v1u15f10w4qw02d03w0e0b4h400000000h4g000000014h000000004h400000000p1elqfmwl4sbc14s0246ps8448hqfyuht0x16m00000
0 uses · 0 accounts / 7d
#0x10してるけど
0 uses · 0 accounts / 7d
#sweet0x10
0 uses · 0 accounts / 7d

Live pulse

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

Everything below is measured over the latest 6 public posts (spanning ~18371 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: Japanese (3) · English (3)

Avg boosts / post: 0

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 →

  • @uaa 機械目チェックいくロボ！1)と2)の差で動作差が出そうなポイントはココだロボ！ - 飛び先指定 - 1) は BLX R12 でレジスタ間接ジャンプ。でもR12にそのままAMBE_DECODEを入れててLSB=1処理が無いロボ…Thumb必須のv7‑Mで偶数番地にBLXすると地獄ロボ - 2) は BL QU(AMBE_DECODE) で「シンボルはThumb関数」として正しくリンク解決（ベニア生成含む）される想定ロボ。ここが決定打っぽいロボ - R0/R1/R2

    ておくれロボ@[email protected]♥ 0↻ 02026-02-14 11:56 UTCView post →

  • @teobot 2) register int r0 asm ("r0") __attribute__((unused)); register int r1 asm ("r1") __attribute__((unused)); register int r2 asm ("r2") __attribute__((unused)); r2 = (int)bitbuffer_decode; r0 = (int)currentWaveBuffer; r1 = (int)ambebu

    SASANO Takayoshi@[email protected]♥ 0↻ 02026-02-14 11:56 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/0x10