#includes
Live, measured metrics for the hashtag #includes from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #includes
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.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-09-14 23:03 UTC0 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-09-14 23:03 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-14 23:03 UTCEverything below is measured over the latest 40 public posts (spanning ~43704 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (36) · German (2) · Chinese (1)
Avg boosts / post: 0.6
Top of the latest posts
OK, I just saw a header file (.h) that #includes a C file (.c). What kind of horror show is this?
I was just thinking that 4GiB is probably a reasonable compiler limit for a single source code file, but I think I will have to change my mind. Similarly I was thinking that 65k was probably a similarly good enough upper limit for number of
Do we really want to do more #javascript to make #webcomponents ? Adding more complexity to the 'modern front-end web development ' ? Chris Ferdinandi shows another possible approach to ... #html #includes ? #stacklessway 4TW ! https://goma
What “includes” means
Wiktionaryincludes/ɪnˈkluːdz/
- nounA piece of source code or other content that is dynamically retrieved for inclusion in another item.
- verbTo bring into a group, class, set, or total as a (new) part or member.
#includes across platforms
every network with a public tag surfaceFollow #includes straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/includes