#digitalequipment
Live, measured metrics for the hashtag #digitalequipment from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #digitalequipment
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-08-01 16:17 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-08-01 16:17 UTCNo related tags with measured usage found for #digitalequipment.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-01 16:17 UTCEverything below is measured over the latest 24 public posts (spanning ~51444 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (21) · French (2)
Avg boosts / post: 1.8
Top of the latest posts
@grawity You’ve probably seen the (explosive!) HP OpenVMS “Disaster Proof” video: https://www.youtube.com/watch?v=bUwthF9x210 💥💥 💥💥 BTS: They had a thunderstorm rolling in during filming. #openvms #digitalequipment #disasterrecovery #re
MUDs and the ability to reload new server without dropping connections (a “hotboot”)… https://boston.conman.org/2025/02/11.2 …reminded me of an old RSX-11M application from an aeon ago, running part of a state government. The app was too bi
@jfmezei @gs DEC sought to create VAX/VMS to be consistent, across API and ABI, across docs, in consistent use of terminology and formats, command syntax, and other details. For its most popular era (the 1970s and 1980s), the doc was quite
#digitalequipment across platforms
every network with a public tag surfaceFollow #digitalequipment 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/digitalequipment