#ifttt
Live, measured metrics for the hashtag #ifttt from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ifttt
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 07:29 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 07:29 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:29 UTCEverything below is measured over the latest 40 public posts (spanning ~5738 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (29) · Czech (5) · Japanese (2) · Italian (1) · German (1) · Chinese (1)
Avg boosts / post: 1.7
Top of the latest posts
IFTTT wasn't a terrible idea. "turn off the lights when I'm more than 1 mile from home" isn't a bad automation. But #IFTTT failed, mostly because it just didn't work reliably. Coordinating the logins and apps was difficult. If you changed a
I fired up a docker container with #n8n in it, and wowza. This thing makes #IFTTT look basic. I'm looking forward to spending some real time with it.
Mein Weg für die automatisierte Ausgabe der meistgeteilten Links hier auf social.heise.de ist kaputt. Ich fürchte, ich komme damit auch nicht weiter. Aber vielleicht hat hier jemand eine Idee? Ich brauche kontinuierlich die Links von hier:
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/ifttt