#ifdefs

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

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 #ifdefs — $520.70/yr→
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0.4
Avg reactions / post
Mastodon · last 40

Day-by-day usage

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

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-27 11:40 UTC

No related tags with measured usage found for #ifdefs.

Live pulse

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

Everything below is measured over the latest 40 public posts (spanning ~31378 hours).

Posting hours (UTC) — busiest: 20:00

00:0012:0023:00

Languages: English (37) · German (2) · Esperanto (1)

Avg boosts / post: 0.3

Top of the latest posts

  • My week: https://lists.haxx.se/pipermail/daniel/2026-January/000143.html (email sent to 486 subscribers!) bug-bounty and hackerone, exposing silly, asking me, rate limiting, features, DNS and curl, #ifdefs

    daniel:// stenberg://@[email protected]♥ 13↻ 32026-01-16 21:44 UTCView post →

  • @bruteforce From a user's standpoint, sure, why not, if it's doing the job for you then go ahead. From a developer's standpoint, I have my reservations about socat. The reason why I'm advocating for one super-[client|server] per socket type

    Laurent Bercot@[email protected]♥ 1↻ 02024-05-10 20:55 UTCView post →

  • @whenning @timbray Not for #ifdefs they won't.

    @[email protected] has moved@[email protected]♥ 1↻ 02023-12-13 01:04 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/ifdefs