#bookdown
Live, measured metrics for the hashtag #bookdown from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bookdown
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 12:39 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-07-27 12:39 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:39 UTCEverything below is measured over the latest 26 public posts (spanning ~55193 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (26)
Avg boosts / post: 0.7
Top of the latest posts
@[email protected] @ERDonnachie yeah this is a problem I ran into in my previous job. We generated user documentation using RMarkdown and the `bookdown` package because lots of the content was code-generated reference tables. But
@pokateo I keeping on learning about how to engineer a good #Python package, plus: finally got around to diving into #quarto (guess I managed to skip #bookdown) #GISChat
@analyst42 @chrisbeeley I used #distill for a public site and #bookdown for internal things I just can't share, like connection strings. It's surprising how often I get to share the links to public posts compared to internal links.
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/bookdown