#ipfs4mastodon
Live, measured metrics for the hashtag #ipfs4mastodon from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ipfs4mastodon
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 00:44 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 00:44 UTCNo related tags with measured usage found for #ipfs4mastodon.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 00:44 UTCEverything below is measured over the latest 10 public posts (spanning ~846 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 1.1
Used together with
Top of the latest posts
Thanks @Downes for becoming a contributor to adding #IPFS support to #Mastodon https://opencollective.com//fission/contribute/ipfs-media-support-for-mastodon-48315 #ipfs4mastodon
@tkenben @flancian just like Mastodon servers need “somebody” to run, we can collectively run the IPFS commons network. You can run your own node, use a commercial service, or even get users to cache & serve content client side. Rather than
@blaine @mastodonmigration @humbird0 @liaizon yeah I think we have a dev team who can take it on now. Might squeeze in a blog post before the end of the year. Open Collective is here https://opencollective.com//fission/contribute/ipfs-media
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/ipfs4mastodon