#HollowByte

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

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.

$23.52/ year · 10-character #name
Claim #hollowbyte$23.52/yr
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
1
Uses / 7 days
Mastodon
1
Accounts / 7 days
Mastodon
13
Recent posts
Mastodon
~0.1/hr
Recent pace
Mastodon · last 13
0.2
Avg reactions / post
Mastodon · last 13

Day-by-day usage

measured · mastodon.social (Mastodon public tags API) · fetched 2026-07-27 08:20 UTC
1
07-21
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 08:20 UTC

No related tags with measured usage found for #hollowbyte.

Live pulse

measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 08:20 UTC

Everything below is measured over the latest 13 public posts (spanning ~119 hours).

Posting hours (UTC) — busiest: 18:00

00:0012:0023:00

Languages: English (9) · French (2) · Catalan (1) · Italian (1)

Avg boosts / post: 0.4

Top of the latest posts

  • The "HollowByte" report got a good deal of attention this past week. There were fair questions in it, so we looked into it properly and wrote up what we found. We reproduced their own scenario. The memory growth is bounded - it plateaus and

    Anton Arapov@[email protected]132026-07-22 18:17 UTCView post →
  • 11 bytes. That's all it takes. A newly disclosed OpenSSL "HollowByte" flaw lets attackers trigger a Memory Exhaustion DoS during the TLS handshake, forcing vulnerable servers to allocate up to 131 KB of heap memory from just an 11-byte mali

    thecybersecguru@[email protected]112026-07-19 06:51 UTCView post →
  • OpenSSL Silently Fixes ‘HollowByte’ DoS Vulnerability https://www.securityweek.com/openssl-silently-fixes-hollowbyte-dos-vulnerability/ #infoSec #hollowbyte #openssl

    David C.@[email protected]002026-07-21 16:09 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/hollowbyte