#webarch

Live, measured metrics for the hashtag #webarch from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #webarch

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.

$240.06/ year · 7-character #name
Claim #webarch — $240.06/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
1
Uses / 7 days
Mastodon
1
Accounts / 7 days
Mastodon
2
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 2
0.5
Avg reactions / post
Mastodon · last 2

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 23:02 UTC
0
07-21
1
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

1 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 23:02 UTC
#webarchiving
2 uses · 2 accounts / 7d
#webarchive
1 uses · 1 accounts / 7d
#webarchives
1 uses · 1 accounts / 7d
#WebArcheology
0 uses · 0 accounts / 7d
#webarchivierungsaustausch
0 uses · 0 accounts / 7d
#webarchivierung
0 uses · 0 accounts / 7d
#webarchitecture
0 uses · 0 accounts / 7d
#WebArchivingWednesday
0 uses · 0 accounts / 7d
#webarchival
0 uses · 0 accounts / 7d
#webarchvies
0 uses · 0 accounts / 7d
#webarchivelu
0 uses · 0 accounts / 7d
#webarchivingpets
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:02 UTC

Everything below is measured over the latest 2 public posts (spanning ~24726 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (2)

Avg boosts / post: 1

Top of the latest posts

  • Spatial Data On The Web Best Practices [OGC / W3C] -- https://www.w3.org/TR/sdw-bp/ <-- shared technical resource -- “This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies

    💧🌏 Greg Cocks@[email protected]♥ 1↻ 02023-09-25 22:41 UTCView post →

  • Plone CMS Case Study: High-Scale Headless Architecture with Plone 6 The Canton of Basel-Landschaft platform baselland.ch handles 100K–350K Plone REST API requests daily, backed by Plone 6 Blicca/Classic, Cloudflare, Elasticsearch, and Redis

    Plone@[email protected]♥ 0↻ 22026-07-22 05:09 UTCView post →

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/webarch