#DBPedia
Live, measured metrics for the hashtag #DBPedia from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dbpedia
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-27 11:41 UTC1 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 11:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:41 UTCEverything below is measured over the latest 40 public posts (spanning ~25331 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (32) · German (4) · French (1) · Spanish (1) · Dutch (1) · Russian (1)
Avg boosts / post: 1.2
Top of the latest posts
J'ai trouvé deux sites d'archives départementales qui réutilisent Wikimédia pour enrichir les pages sur les communes. #wikimedia #wikidata #dbpedia #Archives #Archivistodons
Remarkably: ➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia. ➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.t
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/dbpedia