#nameCollision
Live, measured metrics for the hashtag #nameCollision from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #namecollision
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-28 03:37 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-28 03:37 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 03:37 UTCEverything below is measured over the latest 4 public posts (spanning ~7541 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0
Top of the latest posts
Really, SASE is "Secure Access Service Edge"? SASE has a long history as Self-Addressed Stamped Envelope, but I suppose those days are largely history. #namecollision #initialisms
@t73fde Re: Namenskollisionen / #NameCollision. The localhost #FederatedWiki server tells you if the page already exists. In case of a collision, the client decides what changes need to be made to the history (keyword: journal) to bring the
New post: Notes: beginner's guide to the indie web https://beesbuzz.biz/blog/chatter/12477-beginners-guide-to-the-indie-web #IndieWeb #Tumblr #NameCollision
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/namecollision