#loopix
Live, measured metrics for the hashtag #loopix from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #loopix
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 18: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 18:44 UTCNo related tags with measured usage found for #loopix.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 18:44 UTCEverything below is measured over the latest 9 public posts (spanning ~39656 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0.3
Top of the latest posts
@icedquinn Using #GNUnet's CADET (https://docs.gnunet.org/handbook/gnunet.html#CADET-Subsystem) and a #Loopix implementation would give you a fairly good mixnet, where each end-node also has a decent amount of cover traffic. That hasn't bee
The #mixnet use is unclear and the lack of #Loopix-style loop messages seems like a potential problem for cover traffic. Cover traffic is entirely unmentioned during the entirety of the slides. It would be possible to build that atop of #Ve
@mike805 @jeffcliff @brewsterkahle There's more to it than that. Both #Loopix and #Gnunet Filesharing go into such scenarios as resilience in the face of a malicious majority.
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/loopix