#scritturecomplesse
Live, measured metrics for the hashtag #scritturecomplesse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #scritturecomplesse
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-31 21:41 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-31 21:41 UTCNo related tags with measured usage found for #scritturecomplesse.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-31 21:41 UTCEverything below is measured over the latest 40 public posts (spanning ~21616 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (22) · Italian (17)
Avg boosts / post: 2.3
Top of the latest posts
Online finalmente l'audio dell'incontro su SCRITTURE COMPLESSE, svoltosi alla libreria Tomo il 25 giugno scorso. Come sempre, tutti i file di 'pod al popolo' sono disponibili anche su archive.org. Buon ascolto -> http://slowforward.net/2026
pod al popolo, #098, audio completo della presentazione di (e del dibattito su) “scritture complesse”, [dia•foria, 2026 Il 25 giugno 2026, presso la libreria Tomo, nel contesto della rassegna “Fiori freschi”, si è svolta la presentazione di
oggi, 25 giugno, a roma, presso la libreria tomo: presentazione di “scritture complesse”, [dia•foria 2026 cliccare per ingrandire OGGI, giovedì 25 giugno, h. 18, Libreria Tomo, Roma, via degli Etruschi 4, nel contesto della rassegna “Fiori
#scritturecomplesse across platforms
every network with a public tag surfaceFollow #scritturecomplesse straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/scritturecomplesse