#jinja
Live, measured metrics for the hashtag #jinja from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jinja
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 20:52 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 20:52 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:52 UTCEverything below is measured over the latest 40 public posts (spanning ~13365 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (30) · Russian (5) · French (2) · German (1) · Finnish (1)
Avg boosts / post: 1
Top of the latest posts
🚀 𝗖𝗮𝗹𝗹𝗶𝗻𝗴 𝗮𝗹𝗹 𝗛𝗼𝗺𝗲 𝗔𝘀𝘀𝗶𝘀𝘁𝗮𝗻𝘁 𝘁𝗲𝗺𝗽𝗹𝗮𝘁𝗲 𝘄𝗶𝘇𝗮𝗿𝗱𝘀! 🧙♂️ I’m working on extending the template engine with some new functions, filters, and tests, for example: ✅ flatten(list_of_lists) – Flattens nested li
In order to fix a Jinja security issue (upgrade to 3.1.6 today!) I had to figure out a clever way to improve Python's `hasattr`: https://davidism.com/python-jinja-hasattr/ #python #jinja
Like you, @carlton, I'm still recovering from the intense days we've had. I was able to publish the post timeline so quickly because I automated the process with Python, Pelican, Jinja and Mastodo.py ... the main job was just publishing pos
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/jinja