#plexoduswiki
Live, measured metrics for the hashtag #plexoduswiki from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #plexoduswiki
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-29 13:10 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-29 13:10 UTCNo related tags with measured usage found for #plexoduswiki.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 13:10 UTCEverything below is measured over the latest 8 public posts (spanning ~1 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 0.4
Top of the latest posts
#tootstorm (for my own reference) #UserGeneratedContent #SocialMedia #PlexodusWiki #SocialNetwork #DistributedC
@ricardojmendez The other issue I have is that I don't see how DistributedC is actually handling identity. Best I can tell, it permits multiple identities, but still centralises their management. That's ... an issue. Mind: centrallised trac
@ricardojmendez Having said all that... ... it's really hard to see how a platform or network or protocol will be used without seeing extant use cases. And the first issue I've got with DistributedC is that I don't see any content. G+ faced
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/plexoduswiki