#DBpediaLive
Live, measured metrics for the hashtag #DBpediaLive from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dbpedialive
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 19:39 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 19:39 UTCNo related tags with measured usage found for #dbpedialive.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 19:39 UTCEverything below is measured over the latest 3 public posts (spanning ~67318 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Top of the latest posts
@vrandecic, At the current time, we don't know what's holding up the #DBpediaLive effort -- hence the release of snapshots. I think this is a question for our colleagues in Leipzig :) /cc @pvk
#DBpedia is read-only. #DBpedia-Live is read-write (but you have to edit #Wikipedia docs). #Wikidata is read-write 4 the crowd. #LinkedData
How #DBpedia reflects changes to #Wikipedia via #DBpediaLive : #LinkedData #SPARQL #NewSQL #SemanticWeb #BigData
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/dbpedialive