#litepub
Live, measured metrics for the hashtag #litepub from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #litepub
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-30 14:44 UTC0 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-30 14:44 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 14:44 UTCEverything below is measured over the latest 40 public posts (spanning ~55848 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (34) · French (2) · Afar (1) · enCy (1)
Avg boosts / post: 1
Top of the latest posts
What is the motivation for encouraging LitePub implementors to "supply a locally hosted version of the LitePub JSON-LD Context"? Is it just for people using full-out JSON-LD parsers? Won't this create problems for people using parsers that
The LitePub website has a lot of broken links (on their own site). How I understand LitePub protocol is — it is a protocol that was meant to work with ActivityPub, but is meant to be simple & light-weight. #activitypub #activitystreams #fed
Huh, can any #LitePub folk link me to the emojireact spec? I'm not easily finding it, but there's references in this code to http://litepub.social/ns#emojireact .
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/litepub