#httpsignatures
Live, measured metrics for the hashtag #httpsignatures from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #httpsignatures
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.online (Mastodon public tags API) · fetched 2026-10-18 09:37 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.online (Mastodon public search API) · fetched 2026-10-18 09:37 UTCNo related tags with measured usage found for #httpsignatures.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-18 09:37 UTCEverything below is measured over the latest 15 public posts (spanning ~30157 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (12) · Japanese (1) · Catalan (1)
Avg boosts / post: 2.3
Top of the latest posts
We're excited to announce the release of #Fedify 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and
My #SolidProject client and server are now ready for efficient access control demos on #BigData using the HTTP WG's 's "Signing HTTP Messages". I can demo with a server publishing N resources (in this case, #LinkedData Event Stream (#LDES)
Re: @peertube/http-signature @chocobozzz@framapiaf.org I have a question for you... I'm seeing in Are we HS2019 yet? that Peertube and Misskey both use your package: @peertube/http-signature NodeBB currently rolls its own cavage-12 support
#httpsignatures across platforms
every network with a public tag surfaceFollow #httpsignatures 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/httpsignatures