#newoldimac
Live, measured metrics for the hashtag #newoldimac from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #newoldimac
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 00:22 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 00:22 UTCNo related tags with measured usage found for #newoldimac.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 00:22 UTCEverything below is measured over the latest 40 public posts (spanning ~565 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (40)
Avg boosts / post: 0.3
Top of the latest posts
success. docker restart does not jeopardize anything as long as a volume is specified at runtime to preserve the data. successfully restarted with new conf file and we're now green across the board and hopefully tuned for the slightly large
and bam. Done! That was pretty painless. I now have 5 docker containers running under colima on my 2017 #newOldiMac running macOS Ventura (v13.7.8) #footiMac is only doing the front-end nginx stuff now! For basically a 2 person instance (hi
just tweaked/upped web concurrrency and max threads settings in my .env.production settings for Mastodon to give #footiMac a few more processes to handle requests and things are humming along nicely. I think a big takeway for me on this #se
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/newoldimac