#eventmarkup

Live, measured metrics for the hashtag #eventmarkup 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 #eventmarkup

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.

$10.85/ year · 11-character #name
Claim #eventmarkup$10.85/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
3
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 3
0
Avg reactions / post
Mastodon · last 3

Day-by-day usage

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

0 uses by 0 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 21:46 UTC

No related tags with measured usage found for #eventmarkup.

Live pulse

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

Everything below is measured over the latest 3 public posts (spanning ~182 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: German (2) · English (1)

Avg boosts / post: 0

Used together with

Top of the latest posts

  • @gvogeler For contested dates that are clearly refering to the same `event` I see the point for having a series of different dating assertions without thinking of these as different related events refering to the same concept… For person, t

    Stephan Kurz@[email protected]002024-02-28 22:34 UTCView post →
  • @gvogeler following up on this: The other entity elements (person, place, org etc) do not allow a parentless `date` either. The only kind-of-exception is `birth` and `death`, which are syntactic sugar/special cases of `event`. The takeaway

    Stephan Kurz@[email protected]002024-02-22 08:54 UTCView post →
  • @type (master of events 😀 ) https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html deliberately does not allow nesting a <date>? #TEIXML #eventmarkup

    GVogeler@[email protected]002024-02-21 08:18 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/eventmarkup