#lilypond
Live, measured metrics for the hashtag #lilypond from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lilypond
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-30 10:38 UTC2 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-30 10:38 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 10:38 UTCEverything below is measured over the latest 40 public posts (spanning ~5182 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (28) · German (5) · French (4) · Spanish (1)
Avg boosts / post: 1.7
Top of the latest posts
I've been using Lilypond to write musical notation with code, and here I write about how to get a convenient, smooth experience while writing that code in Neovim! I'm definitely planning to stick with this, and I'll be writing about some mo
Beautiful article on #GNU #LilyPond "Lilypond Music-Notation Software in the Digital-Humanities Toolbox" -- Andrew A. Cashner https://dhq.digitalhumanities.org/vol/18/2/000573/000573.html #gnulilypond
Finally taking the plunge and learning Lilypond! It's kind of like LaTeX for sheet music. I'd been interested since the Finale debacle, and while Dorico has been nice, I'm finding that in many cases I prefer writing text files to working in
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/lilypond