#sdd
Live, measured metrics for the hashtag #sdd from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sdd
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 13:31 UTC2 uses by 2 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 13:31 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:31 UTCEverything below is measured over the latest 40 public posts (spanning ~13534 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (27) · Russian (7) · German (2) · Italian (1) · French (1) · Japanese (1)
Avg boosts / post: 0.4
Top of the latest posts
Replacing my #raspberrypi 4B server with a #thinkcentre m93p. The #thinkcentre has more ram, a 512 GB #sdd and can handle external drives far better than the #raspberry does. Finally, also lucky to get rid of #rasberrypios in favor of #debi
I've got a bunch of blog articles in the pipeline in which I'll explore different aspects. Stay tuned if this sounds interesting. I'm also working on a #SDD for #Django Course through my company #Prelude. Feel free to ping me if you want me
So I moved all LXCs to another #Proxmox node. The problematic drive’s usage has returned to normal, but another node where containers were moved is still fine. Looks like the issue is in a WD Green SSD on that node. It took 1429 hours to re
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/sdd