#anvilope
Live, measured metrics for the hashtag #anvilope from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #anvilope
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-28 07:18 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-28 07:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 07:18 UTCEverything below is measured over the latest 15 public posts (spanning ~9413 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (15)
Avg boosts / post: 0.2
Top of the latest posts
Thinking about the future of #anvilope and whether I want it to be configured through config files on disk or through the web UI that doesn't exist yet. About all I know so far is that the "why not both" way home assistant does it is annoyi
After finishing some refactors and improvements, I've updated my #anvilope testbed machine with gemma 4 E2B. It's been running for about two days, and going just off feels the results seem quite nice. The categorizing seems pretty similar t
Mocking up some UI for a future #anvilope web dashboard and I am so rusty at design. Email has so many fields, and you need to ruthlessly prioritize what gets displayed. This is still too cluttered for my liking, but I've already axed some
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/anvilope