#johnousterhout
Live, measured metrics for the hashtag #johnousterhout from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #johnousterhout
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 · mastodon.online (Mastodon public tags API) · fetched 2026-07-31 19:21 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-31 19:21 UTCNo related tags with measured usage found for #johnousterhout.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-31 19:21 UTCEverything below is measured over the latest 5 public posts (spanning ~28929 hours).
Posting hours (UTC)
Languages: Spanish (3) · Dutch (1) · English (1)
Avg boosts / post: 0.2
Top of the latest posts
Antes de que “la nube” fuera una palabra cotidiana, 𝗦𝗽𝗿𝗶𝘁𝗲 ya exploraba una idea poderosa: muchas máquinas, un solo entorno. Desde hace 30 años no se veía una instalación clúster de Sprite, hasta que el usuario @spijdar hizo lo impens
Su propuesta incluía imagen única de sistema, migración de procesos, alto rendimiento en archivos mediante caché cliente-servidor y experimentos que influirían en áreas como los sistemas de archivos log-structured, RAID, recuperación ante f
En los años 80, mientras UNIX dominaba laboratorios y estaciones de trabajo, en Berkeley nacía 𝗦𝗽𝗿𝗶𝘁𝗲: un sistema operativo experimental diseñado para pensar en red desde su núcleo. Desarrollado por el grupo de John Ousterhout en la U
#johnousterhout across platforms
every network with a public tag surfaceFollow #johnousterhout 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/johnousterhout