#jakartaee
Live, measured metrics for the hashtag #jakartaee from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jakartaee
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 00:55 UTC7 uses by 6 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 00:55 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 00:55 UTCEverything below is measured over the latest 40 public posts (spanning ~1080 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (36) · German (3) · French (1)
Avg boosts / post: 0.3
Top of the latest posts
On my way to Crete for #JCrete to discuss Java, Jakarta EE, Open Source, and more CPH ✈️ CHQ #JakartaEE #EclipseFoundation #Community
Hashtag Jakarta EE number 343 is out! Read about summer conferences, Jakarta EE 12 progress, and the Java Documentary #JakartaEE #EclipseFoundation #Community https://www.agilejava.eu/2026/07/26/hashtag-jakarta-ee-343/
Given the two tables accounts in the first screenshot, you can either have a #JakartaEE mapping, and you get an object graph, or use Virtual Graphs. Our internal configuration looks much the same (compare second screenshot left and right).
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/jakartaee