#yacy
Live, measured metrics for the hashtag #yacy from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #yacy
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 08:10 UTC1 uses by 1 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 08:10 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:10 UTCEverything below is measured over the latest 40 public posts (spanning ~1434 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (33) · Russian (3) · Spanish (2) · German (1) · French (1)
Avg boosts / post: 0.5
Top of the latest posts
I launched my first few crawls overnight, and there's so much I want to say. Let's start with a few numbers. First of all, YaCy is finally an application which puts some load on my Homelab. See picture 1. It peaked at around 4GB of RAM, eve
New blog post: https://blog.mei-home.net/posts/yacy-part-1-deployment/ This is the first post in what's very likely going to be a whole series about the YaCy distributed P2P search engine. In this initial post I describe YaCy a bit and go t
Overall, I'm still not sure what to think about YaCy. It does now somewhat okayish find info about e.g. Ceph Rook. And that is not nothing, quite regularly I know which site to look at, but not which page when I'm doing a search. But also,
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/yacy