#xcover

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

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.

$520.70/ year · 6-character #name
Claim #xcover — $520.70/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
3
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 3
0
Avg reactions / post
Mastodon · last 3

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 01:09 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 01:09 UTC
#GalaxyXCover6Pro
0 uses · 0 accounts / 7d
#XCoverPro
0 uses · 0 accounts / 7d
#GalaxyXCover
0 uses · 0 accounts / 7d
#GalaxyXcover5
0 uses · 0 accounts / 7d
#xcover5
0 uses · 0 accounts / 7d
#SamsungGalaxyXCover6Pro
0 uses · 0 accounts / 7d
#xcover6pro
0 uses · 0 accounts / 7d
#xcover7
0 uses · 0 accounts / 7d

Live pulse

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

Everything below is measured over the latest 3 public posts (spanning ~3567 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (3)

Avg boosts / post: 0

Top of the latest posts

  • @officialaptivi.wordpress.com Samsung goes a long way to systematically omit to mention their X-cover line to the general public. I wonder why... ? I guess maybe because devices optimized for longevity, rugged built, which have removable ba

    Matjö@[email protected]♥ 0↻ 02026-07-08 06:53 UTCView post →

  • Was adding stripped binary support to #xcover with no debug info. So I started playing with the Go disassembler and pulled the implementation out into #ResurGo: a Go library for prologue detection + call site analysis, supporting x86_64 and

    maxgio92@[email protected]♥ 0↻ 02026-02-24 06:51 UTCView post →

  • Now #xcover supports stripped Go binaries. Take a look here: http://github.com/maxgio92/xcover?tab=readme-ov-file#stripped-binaries I'll cut a new release soon.

    maxgio92@[email protected]♥ 0↻ 02026-02-09 15:57 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/xcover