#shouldhaveknownbetter
Live, measured metrics for the hashtag #shouldhaveknownbetter from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #shouldhaveknownbetter
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-29 14:38 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-29 14:38 UTCNo related tags with measured usage found for #shouldhaveknownbetter.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 14:38 UTCEverything below is measured over the latest 3 public posts (spanning ~23680 hours).
Posting hours (UTC)
Languages: English (2) · German (1)
Avg boosts / post: 0
Top of the latest posts
As rabbit holes go... … deciding to install FreeBSD on an old Intel iMac and then trying to get a desktop environment working is quite a good one 🤦🏼♂️. #shouldhaveknownbetter
@jerry I believe this is an #InheritRisk working in the #EnterpriseSpace, especially the #FediSpace (regardless of which country you work in). While this sucks generally, it appears on the surface that this could have been avoided by simply
Tonight I thought that if I measured twice, took my time and thought hard about it - then I could do a bit of sewing on my #AgileTD costume without using a prototype. Want to guess who needs to remove and redo three big seams? #ShouldHaveKn
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/shouldhaveknownbetter