#computationalmusicology
Live, measured metrics for the hashtag #computationalmusicology from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #computationalmusicology
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-08-02 20:35 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-08-02 20:35 UTCNo related tags with measured usage found for #computationalmusicology.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-02 20:35 UTCEverything below is measured over the latest 40 public posts (spanning ~12575 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (40)
Avg boosts / post: 1.5
Top of the latest posts
New year, new country, new #introduction. Having obtained my #PhD in #computationalmusicology in 🇨🇭 last year, I am now pursuing an academic career in #musicresearch in Linz 🇦🇹. Most music genres and styles have fantastic specimens but
On 13–14th of February 2025, I organised a #Hackathon on #RomaniChords that explored various methodological avenues for my #MSCA project’s data acquisition. Here’s a short thread summarising what we dealt with and achieved during these days
#AcademicJob | #PostDoc | #PhDStudentship 📍University of Jyväskylä, Finland The Centre of Excellence in Music, Mind, Body & Brain plans to recruit 6–9 postdoctoral researchers and 4–7 PhD students for 2027–2029. Projects span music and emo
#computationalmusicology across platforms
every network with a public tag surfaceFollow #computationalmusicology 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/computationalmusicology