#computationalarchaeology
Live, measured metrics for the hashtag #computationalarchaeology from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #computationalarchaeology
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-09-26 00:40 UTC1 uses by 1 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-09-26 00:40 UTCNo related tags with measured usage found for #computationalarchaeology.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-26 00:40 UTCEverything below is measured over the latest 40 public posts (spanning ~6118 hours).
Posting hours (UTC) — busiest: 08:00
Languages: German (21) · English (17) · Danish (2)
Avg boosts / post: 3.9
Top of the latest posts
And as a friendly reminder, we hold monthly meetings where we host amazing speakers, organize collectively-maintained projects, and discuss all things relating to scripting languages in archaeology! (we also sometimes spill out into other #
I finally got round to adding classic single radiocarbon calibration plots to my #Rstats package {c14}. I think they turned out pretty nice! https://c14.joeroe.io/reference/plot.c14_cal.html #Archaeology #ComputationalArchaeology #Radiocarb
📚 Plenty of research has been done to encourage better software engineering practices, among archaeological and non-archaeological researchers alike. We compiled a brief list of papers addressing challenges in this space, and we encourage
#computationalarchaeology across platforms
every network with a public tag surfaceFollow #computationalarchaeology straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/computationalarchaeology