#include_next

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

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.

$5.00/ year · 12-character #name
Claim #include_next$5.00/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
13
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 13
0.8
Avg reactions / post
Mastodon · last 13

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 04:27 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 04:27 UTC

No related tags with measured usage found for #include_next.

Live pulse

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

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

Posting hours (UTC) — busiest: 00:00

00:0012:0023:00

Languages: English (12) · German (1)

Avg boosts / post: 0.2

Top of the latest posts

  • Sigh, Ruby. I just wanted to write a blog post, I didn't want to have to reinstall all of the Ruby dependencies because the installed gems no longer work with my system Ruby, and then discover that the new ones don't compile. EDIT: It looks

    David Chisnall (*Now with 50% more sarcasm!*)@[email protected]1012026-02-04 14:22 UTCView post →
  • C extensions, portability, and alternative compilers ---- - 14 minutes ago | 5 points | 0 comments - URL: https://lemon.rip/w/6-c-extensions-compilers/ - Discussions: https://news.ycombinator.com/item?id=48267126 - Summary: Writing a new C

    hnbot@[email protected]002026-05-25 14:30 UTCView post →
  • @Sobex Both are provided in the search paths. If you do clang -vvv then it will list the search locations. The builtin ones that overlap standard ones all #include_next the standard ones. If they're somehow incompatible, please file a bug.

    David Chisnall (*Now with 50% more sarcasm!*)@[email protected]002025-11-19 15:22 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/include_next