#historicalresearch
Live, measured metrics for the hashtag #historicalresearch from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #historicalresearch
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-29 16:56 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-29 16:56 UTCNo related tags with measured usage found for #historicalresearch.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:56 UTCEverything below is measured over the latest 40 public posts (spanning ~16695 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (34) · French (3) · German (1) · Italian (1)
Avg boosts / post: 0.7
Top of the latest posts
I've been adding historical information and documents into Logseq for the past few weeks. I just add a little bit each evening, and create back-links, and proofread things. It parallels nicely with my work in QGIS. What a really interesting
Glad to have the opportunity to join online the conference on #DataEthics for #HistoricalResearch A first poll did already show the 🔑 word for the next days: transparency, responsibility, accessibility, data bias, power + care ➡️ Looking f
(Stories of people) In 1977, he found old documents of his grandfather. The documents were proof of purity of origin. It was necessary to have such documents during Protectorate of Bohemia and Moravia. An idea of creating his own family tre
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/historicalresearch