#readme

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

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 #readme — $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.8
Avg reactions / post
Mastodon · last 40

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 06:12 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 06:12 UTC
#Readmeat
0 uses · 0 accounts / 7d
#readmetxt
0 uses · 0 accounts / 7d
#readmerryhell
0 uses · 0 accounts / 7d
#readmefirst
0 uses · 0 accounts / 7d
#readmedottext
0 uses · 0 accounts / 7d
#readmetosleep
0 uses · 0 accounts / 7d
#READMEs
0 uses · 0 accounts / 7d
#it33_readme
0 uses · 0 accounts / 7d
#readmeyou
0 uses · 0 accounts / 7d
#readmeproject
0 uses · 0 accounts / 7d
#readmeapoem
0 uses · 0 accounts / 7d
#TheReadmeProject
0 uses · 0 accounts / 7d

Live pulse

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

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

Posting hours (UTC) — busiest: 16:00

00:0012:0023:00

Languages: English (27) · Russian (5) · German (5) · Korean (1) · Chinese (Taiwan) (1) · French (1)

Avg boosts / post: 1

Top of the latest posts

  • RE: https://fosstodon.org/@Cockpit/116811005398344842 Nice. Feature suggestion for GitHub, if any product managers from GH are poking around: Feature the README first, don't bury it under the file display. How many people, going to github/o

    Joe Brockmeier@[email protected]♥ 13↻ 82026-06-25 14:26 UTCView post →

  • I had a moment of inspiration and created #ggg take a look (still #experimental #foss software) ggg: #guile #scheme #glyph #generator https://codeberg.org/jjba23/ggg Through #svg generation from #lisp we leverage a (wip) #dsl and apply some

    Josep Bigorra (jjba23)@[email protected]♥ 5↻ 72025-05-19 13:37 UTCView post →

  • Hot take: I tried the opposite of TDD. I wrote the README first. Then forced the code to obey it. A README that is also a runnable literate Haskell script: ./4_ch.md No build system. Just runghc. It turns out README-driven design is amazing

    someodd@someodd♥ 4↻ 02026-01-26 19:33 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/readme