#websockets
Live, measured metrics for the hashtag #websockets from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #websockets
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-09-12 07:04 UTC1 uses by 1 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-09-12 07:04 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-12 07:04 UTCEverything below is measured over the latest 40 public posts (spanning ~2913 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (28) · Spanish (4) · Russian (3) · Romanian (1) · Chinese (Taiwan) (1) · Swedish (1)
Avg boosts / post: 0.8
Top of the latest posts
been also rewriting #SparkleShare's notification service in #Rust. it allows clients to instantly notify each other of changes, since ssh/git polling is heavy and slow. also using HTTPS, though no private data is sent. using #WebSockets thi
Very excited about the new stateful components model in Kitten¹ that I’m looking forward to releasing this week (finally) and the amount of visibility you can now get into the flow of your Kitten apps in the Kitten Interactive Shell (REPL)²
«HTML over WebSockets: real-time SPAs with barely any JavaScript» Building a SPA usually means a JS framework, a JSON API, and two codebases forced to agree on a contract; there is another way that skips all three, and it is not new. https:
What “websockets” means
WikipediaWebSocket is a computer communications protocol, providing a bidirectional communication channel over a single Transmission Control Protocol (TCP) connection. The protocol was standardized by the IETF as RFC 6455 in 2011. The current specification allowing web applications to use this protocol is known as WebSockets. It is a living standard maintained by the WHATWG and a successor to The WebSocket API from the W3C.
“WebSocket” on Wikipedia (CC BY-SA) →#websockets across platforms
every network with a public tag surfaceFollow #websockets straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/websockets