#schedulesdirect
Live, measured metrics for the hashtag #schedulesdirect from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #schedulesdirect
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 · mas.to (Mastodon public tags API) · fetched 2026-07-28 07:00 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-28 07:00 UTCNo related tags with measured usage found for #schedulesdirect.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-28 07:00 UTCEverything below is measured over the latest 6 public posts (spanning ~20837 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 1.3
Used together with
Top of the latest posts
always makes me sad when I see such terrible authentication mechanisms: https://github.com/SchedulesDirect/JSON-Service/wiki/API-20141201#obtain-a-token This implies that either the server has the password in clear, or just stores sha1 hex
If you use the live TV function along with Schedules Direct, this should fix the issue causing your SD account to be blocked. #Jellyfin #SchedulesDirect https://mastodon.online/@jellyfin/113869847662707469
#SchedulesDirect emailed me that mandatory lineup changes needed due to their provider update. If you rely on Schedules Direct for your TV lineup, you need to take action before December 11th or your TV listings will be wrong. If you use US
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/schedulesdirect