#usocket
Live, measured metrics for the hashtag #usocket from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #usocket
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 06:51 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 06:51 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:51 UTCEverything below is measured over the latest 4 public posts (spanning ~6927 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0
Top of the latest posts
@pkw in your wisdom, do you have some ideas on what I should actually be doing in this handler function. I also ended up sending my clim presentation as strings because the default (accept '(sequence t) :stream from-usocket) didn't have a m
#CommonLisp #usocket (about my beastie #gopher #server) gopher://beastie.sdf.org:7991/1/ In usocket, usocket:wait-for-input regards an EOF as an input, so this makes it to my #'read-char-no-hang . Confusingly, read-char-no-hang's correct EN
Alright! Something has managed to take down my gopher server running on beastie. Time to investigate. #CommonLisp #Bug #gopher #usocket Resolved! (ad hoc testing) I assumed wrongly that #'usocket:wait-for-input always returned a number (uns
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/usocket