#ed1
Live, measured metrics for the hashtag #ed1 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ed1
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 · mas.to (Mastodon public tags API) · fetched 2026-07-28 15:00 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-28 15:00 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-28 15:00 UTCEverything below is measured over the latest 13 public posts (spanning ~29137 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (11) · Spanish (1) · German (1)
Avg boosts / post: 1.2
Top of the latest posts
My #ed(1) hot take is that more people should use edbrowse for some daily tasks. I think it's good for building a better web. The web may be fully over (WASM! WebSerial!) but things like edbrowse forces us to ask questions about how we want
@ed1conf we need a unified hashtag for all ed(1)-posting. Using #ed is too generic, while #ed1 is under-represented. Ideas?
I’m slightly worried that my #ed1 scripts use a non-#POSIX behavior of newlines in s-ubstitutions inside g-lobal command list. (I even had one implementor point it out to me.) But both major ed(1) implementations (GNU and OpenBSD) support t
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/ed1