#DataCooperative
Live, measured metrics for the hashtag #DataCooperative from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #datacooperative
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 15:27 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 15:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 15:27 UTCEverything below is measured over the latest 4 public posts (spanning ~19283 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1.8
Top of the latest posts
Launching soon: a #DataCooperative with a focus on digital rights #performance #timekeeping #engagement 🍕 https://github.com/dribdat/coop
I don't always post on #Level1Techs forum, but when I do it's because I've become interested in #DataCooperative. As I mention in this post, blind trust towards your hosting vendor is one thing, but how does one set up a #kubernetes cluster
In regards to #LibreOffice collaborative features in Writer and Calc, has anyone actually implemented this on an #organizational level? What are the limitations? What's lacking? What have they gotten wrong, what have they gotten right? Is i
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/datacooperative