#lwan
Live, measured metrics for the hashtag #lwan from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lwan
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 20:18 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 20:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:18 UTCEverything below is measured over the latest 4 public posts (spanning ~18582 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1
Used together with
Top of the latest posts
Just blogged: a new hash table for #lwan https://tia.mat.br/posts/2026/05/06/a-new-hash-table-for-lwan.html (I even drew diagrams! I'm usually too lazy to fight pikchr or even open drawio.)
Just blogged: more async/await in #lwan in which I briefly describe the improvements I've made to my toy web server since my last blog post on the subject of its homebrewed async/await runtime. https://tia.mat.br/posts/2026/04/26/more-async
Just pushed #Landlock support to #lwan! This should significantly improve its security (can't call exec*(2), can't bind to ports other than those in the config file, can't read files outside where they should be served, etc). I still need 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/lwan