#tuskydev
Live, measured metrics for the hashtag #tuskydev from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tuskydev
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 06:51 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 06:51 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:51 UTCEverything below is measured over the latest 40 public posts (spanning ~29236 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (38) · French (2)
Avg boosts / post: 6.3
Top of the latest posts
So according to crashlogs there is a crash in Tusky where it just crashes scrolling a timeline. It never happened to me so I'm looking for more information so I can fix it. If you encountered a crash that matches that description I'd like t
I'm seeing a crash reported A LOT in the Google Play console for Tusky 32.1. I have no idea how to reproduce it, but from the stacktrace it is somewhere in a timeline. Most crashes are on foldable or tablet sized devices and Android 16. If
The code to display attachements in a grid is one of the most complex parts in Tusky. There are different aspect ratios, blurhashes, focuspoints, ... I'm currently rewriting it in Compose and it is SHOCKINGLY EASY 😳 The old code to respect
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/tuskydev