#pak
Live, measured metrics for the hashtag #pak from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pak
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 11:14 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-27 11:14 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:14 UTCEverything below is measured over the latest 40 public posts (spanning ~18640 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (30) · German (5) · Dutch (1) · Italian (1) · Spanish (1)
Avg boosts / post: 0.7
Top of the latest posts
Anyway here's that blogpost about using small shell wrappers for #pak and #renv and also #Positron and project management and whatnot for the #rstats crowd: https://blog.jemu.name/2025/03/r-usability-gimmicks/
Unfortunately, re-installing a whole renv library is incredibly slow. However, the renv.config.pak.enabled option speeds it up by a ridiculous margin by installing packages in parallel: https://rstudio.github.io/renv/reference/config.html#r
Ever since I started using #pak for basically all my #rstats package installation needs, I noticed dropped my habit of occasionally running `remotes::update_packages()` in my general R installation --- I've looked to see if pak has a simila
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/pak