#dotconfig
Live, measured metrics for the hashtag #dotconfig from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dotconfig
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-28 01:29 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-28 01:29 UTCNo related tags with measured usage found for #dotconfig.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 01:29 UTCEverything below is measured over the latest 3 public posts (spanning ~6204 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Top of the latest posts
For example, just one of my #DotConfig files currently in flux is my #HelixEditor and #MicroEditor configurations (which I want to be able to use on remote servers and clusters), as I fine tune the keyboard mappings - using scp to sync asso
After a bunch of scp/rsync commands between systems to synchronise configurations, I think maybe I should just put my ~/.config folder under version control (and set .gitignore to avoid recording the private keys or anything else sensitive
Just updated my WezTerm¹ configuration file. (In case you’re the kind of person that gets excited by such things.) 👋🤓 https://codeberg.org/aral/.config/src/branch/main/wezterm.lua ¹ https://wezfurlong.org/wezterm/ #WezTerm #config #dotCon
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/dotconfig