#fserve
Live, measured metrics for the hashtag #fserve from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fserve
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-10-11 11:36 UTCNo measured public usage for #fserve in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-11 11:36 UTCNo related tags with measured usage found for #fserve.
Live pulse
measured · Mastodon tag timeline · fetched 2026-10-11 11:36 UTCNo recent public posts found for #fserve on Mastodon. Nothing measured, so nothing shown.
What “fserve” means
WikipediaDirect Client-to-Client (DCC) is an IRC-related sub-protocol enabling peers to interconnect using an IRC server for handshaking in order to exchange files or perform non-relayed chats. Once established, a typical DCC session runs independently from the IRC server. Originally designed to be used with ircII it is now supported by many IRC clients. Some peer-to-peer clients on napster-protocol servers also have DCC send/get capability, including TekNap, SunshineUN and Lopster. A variation of the DC
“Direct Client-to-Client” on Wikipedia (CC BY-SA) →#fserve across platforms
every network with a public tag surfaceFollow #fserve 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/fserve