#gitlfs
Live, measured metrics for the hashtag #gitlfs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gitlfs
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 11:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 11:45 UTCNo related tags with measured usage found for #gitlfs.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 11:45 UTCEverything below is measured over the latest 27 public posts (spanning ~57972 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (23) · Russian (2) · Polish (1) · German (1)
Avg boosts / post: 0.1
Top of the latest posts
@senders the problem is that browser-supported image formats are either already well-compressed or uncompressed. There's no good way to i.e. have (lossy or lossless) compressed RAWs that works out of the box at peoples' devices that ain't J
@agowa338 That didn't work. 😔 I'm pretty sure that setting only applies to core #Git (which I believe uses #curl), not LFS (which is a Go program with a completely different HTTP stack). That's actually an issue on Windows too. IIRC, you c
Well, #Apple has put me in a bit of a pickle. I work for an org with a private #CA that issues 50-year #TLS certificates. One such certificate protects #Git repos on a #Forgejo instance. #GitLFS on #macOS says the cert is “not standards com
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/gitlfs