#Defuse
Live, measured metrics for the hashtag #Defuse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #defuse
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 21:55 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 21:55 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 21:55 UTCEverything below is measured over the latest 10 public posts (spanning ~18082 hours).
Posting hours (UTC)
Languages: English (8) · Russian (2)
Avg boosts / post: 1.4
Top of the latest posts
Looking forward to speaking at Defuse – Design for Use in Dublin on November 10th about breaking the rules and doing things differently (and yes, the Small Web). Mark it on your calendars and come along if you’re free. https://defuse.ixd.ie
Поиск потенциальных уязвимостей в коде, часть 2: практика В прошлый раз мы ознакомились с общими подходами в поиске уязвимостей безопасности в приложениях. В этот раз спустимся ближе к земле и посмотрим на то, как мы реализовали эти механиз
Поиск потенциальных уязвимостей в коде, часть 1: теория Риски наличия уязвимостей безопасности всем известны: нарушение работы приложения, потеря данных или их конфиденциальности. В этой статье мы посмотрим на наглядных примерах фундаментал
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/defuse