#openharbors
Live, measured metrics for the hashtag #openharbors from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #openharbors
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 13:38 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 13:38 UTCNo related tags with measured usage found for #openharbors.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 13:38 UTCEverything below is measured over the latest 5 public posts (spanning ~4106 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 2
Top of the latest posts
Yaiy! I'm super excited, have gotten accepted for funding from @nlnet!!! This will finally give me the opportunity to work on this project idea that has been on my mind for quite a while now: https://nlnet.nl/project/OpenHarbors/ Which will
One step further for #OpenHarbors with my #tc hackery/prototype. The client/supplicant seems to now receive the #EAPoL from the remote, bridged AP fine and replies to it. Next need to get the reply back to the remote AP. Initially wasn't su
So, some small progress for #OpenHarbors. Currently trying to see how far I can get with what #hostapd, #wpasupplicant and Linux in general already provide and hacks around that. With control_port=0 and some #tc rules I was able to snitch t
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/openharbors