#tfcards
Live, measured metrics for the hashtag #tfcards from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tfcards
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:33 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:33 UTCNo related tags with measured usage found for #tfcards.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:33 UTCEverything below is measured over the latest 6 public posts (spanning ~2977 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.2
Top of the latest posts
@WiteWulf @matt303 @vnvobit Not really. The filesystem tools and operations are the usual ones, and indeed the image files that operating systems and whatnot are distributed as can be treated as mountable DASD volumes with md. So it's a sim
@matt303 @vnvobit @WiteWulf I've never bothered with special software to write TF cards, myself. I just gpart them and and use dd; or newfs and then mount the volumes directly and use pax/cp to just copy stuff in. Failure at unmount time, p
Another 4 hours gone. Another 2GiB done. I might not be doing the card for Orac's key today, after all. #pax #TFCards #BerkeleyFFS
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/tfcards