#cron
Live, measured metrics for the hashtag #cron from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cron
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 09:49 UTC3 uses by 3 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 09:49 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:49 UTCEverything below is measured over the latest 40 public posts (spanning ~3362 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (25) · Russian (6) · Spanish (2) · German (2) · French (2) · Italian (1)
Avg boosts / post: 0.6
Top of the latest posts
I don't know if I've ever shared my cron package idea here, but in searching through my records here it is again. Mightocrondria: cron jobs that might or might not actually run, set the normal frequency, the thing to run, and a chance that
Special thanks to @amureki for better #Sentry support in #Django CronTask. Thanks @getsentry for replying so quickly to our questions. https://github.com/codingjoe/django-crontask #python #django #cron #task #foss
I'm back with another #FreeBSD question, specifically about `periodic`. I'd like to use `periodic daily` to occasionally scrub my ZFS pools by setting `daily_scrub_zfs_enable` to `"YES"` in `/etc/periodic.conf`. This works great on a server
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/cron