#xpman
Live, measured metrics for the hashtag #xpman from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #xpman
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-07-27 12:21 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-07-27 12:21 UTCNo related tags with measured usage found for #xpman.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:21 UTCEverything below is measured over the latest 40 public posts (spanning ~28522 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (40)
Avg boosts / post: 1.5
Top of the latest posts
@marick One theory posited during November's #xpman lean coffee is: that a codebase gradually increases in size until it is too large/complex to be managed by the design/architecture patterns that are well understood by its developers. The
Don't forget that XP Manchester is back this week! That's right, your favourite lean coffee morning: Thursday 9th Feb, doors open 0730 GMT for a 0745 start; finish at 0845. Joining instructions can be found at https://www.meetup.com/xp-manc
It's #xpman on Thursday at Code's offices, with a hands on refactoring session informed by Connascence https://www.eventbrite.co.uk/e/using-connascence-to-drive-refactoring-tickets-1982768021527
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/xpman