#open3e
Live, measured metrics for the hashtag #open3e from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #open3e
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 21:42 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 21:42 UTCNo related tags with measured usage found for #open3e.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 21:42 UTCEverything below is measured over the latest 9 public posts (spanning ~13323 hours).
Posting hours (UTC)
Languages: German (7) · English (2)
Avg boosts / post: 0.7
Top of the latest posts
I updated my #open3E installation for locally fetching data of my favorite #Viessmann heatpump via CAN bus. Broke my #HomeAssistant sensors due to changed MQQT topic names. Was a quick fix because sources are public and diff is easy. I love
First time since many many months my #Open3E VM lost connection to the heatpump or #HomeAssistant. Not sure. Had no good option to debug via phone so I just rebooted the VM. #HomeLab
@remo @gnulinux Jup hab ich mit meiner 250 auch gemacht. Mit #Open3E. Die Cloud API war einfach total instabil. https://github.com/open3e/open3e
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/open3e