#pocusky
Live, measured metrics for the hashtag #pocusky from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pocusky
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 07:50 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-07-27 07:50 UTCNo related tags with measured usage found for #pocusky.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:50 UTCEverything below is measured over the latest 12 public posts (spanning ~12660 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (12)
Avg boosts / post: 0
Used together with
Top of the latest posts
The thickness of the normal LV apex on echo is actually a slice thickness artefact. In reality, it’s extremely thin #echosky #pocusky RE: https://bsky.app/profile/did:plc:4ishw7rkrolkkkvqvkdcdgvl/post/3ml4wx5srcd2l
Good example that diastolic flattening is much more common than systolic in acute PE. #echosky #emimcc #pocusky RE: https://bsky.app/profile/did:plc:ypl3l3efpmvo25klknwnoevj/post/3mk65dbbkfc2r
Something that’s rarely if ever mentioned in guidelines and manuals about echocardiography is always asking the question «do the numbers add up?» This is not just central to divulging measurement error but also harder to find pathologies. #
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/pocusky