#SpecScriptShoutOut
Live, measured metrics for the hashtag #SpecScriptShoutOut from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #specscriptshoutout
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 23:21 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 23:21 UTCNo related tags with measured usage found for #specscriptshoutout.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:21 UTCEverything below is measured over the latest 21 public posts (spanning ~767 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (21)
Avg boosts / post: 1.3
Top of the latest posts
In 2023, we're #TwitterFree! If you've read a great unproduced spec script from another writer and want to let people on Mastodon about it, this is what #SpecScriptShoutOut is aimed at. The hashtag can be used any time, and the 2nd Thursday
We're working on the annual recap for #SpecScriptShoutOut. So many great scripts have been covered in 2022, and we look forward to celebrating them all one more time. And starting this year, it will be taking place right here on Mastodon in
A #SpecScriptShoutOut from Tom Schrack for #ENEMY, a feature script by Clint Williams (@ClintW3) which made the Nicholl Top 50 in 2022. (Originally posted on Twitter.)
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/specscriptshoutout