#svcs
Live, measured metrics for the hashtag #svcs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #svcs
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-07-27 20:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 20:45 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 20:45 UTCEverything below is measured over the latest 5 public posts (spanning ~14306 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Top of the latest posts
Anyone understand #ContextVars in #python ? I'm trying to add support to #svcs so that when there isn't a web framework with a context to glom onto, that you can use the thread/thread.local/ContextVars and an alternative to the Application/
Call it "first-mover advantage" -- or disadvantage, depending on your POV -- my #Django / #svcs integration apparently just barely beat @ubernostrum to the punch on the name on PyPi. Fortunately, they're a good sport and collaborative, and
During my work hours, and with company resources, I made a simple but useful library to get logging very easily set up for FastAPI projects, using structlog and with integration with svcs. I think that would be quite useful for many folks,
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/svcs