#solved
Live, measured metrics for the hashtag #solved from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #solved
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-28 02:23 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-07-28 02:23 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 02:23 UTCEverything below is measured over the latest 40 public posts (spanning ~11677 hours).
Posting hours (UTC) — busiest: 05:00
Languages: English (35) · Czech (1) · Lithuanian (1) · German (1) · Italian (1)
Avg boosts / post: 0.5
Top of the latest posts
boot -s, zfs mount -a, zfs set readonly=off zroot, comment out kld_load i915kms from rc.conf, reboot, complete make installworld, reboot, git pull /usr/ports, pkg delete drm-kld, portmaster graphics/drm-latest-kld ., enable kld_load i915s i
#Identification #Inquiry found on berries. I suspect it's some kind of #Moth #larvae but not 100% sure (Edit: #Solved #Evergestis #Rimosalis)
I have three .avi files that have identical size but different md5sum. A simple binary diff tells me that there are a couple of single-byte differences. Is there some kind of tool that would allow me to tell what those differences amount to
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/solved