#jdk11
Live, measured metrics for the hashtag #jdk11 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jdk11
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 07:02 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 07:02 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:02 UTCEverything below is measured over the latest 7 public posts (spanning ~28117 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.9
Top of the latest posts
There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE
Proposal: Support Wayland and add KEM APIs [..] only Wayland will be supported in RHEL 10 and subsequent releases. [..] We would also like to add support in Java SE 17 for functionality required by some Post-Quantum Cryptographic (PQC) algo
https://bugs.openjdk.org/browse/JDK-8302697 #Fonts with #ContextualAlternates are not correct rendered in #Java #JavaOpenJDK #OpenJDK #Adoptium #Eclipse #Temurin #AdoptOpenJDK #AdoptiumTemurin #EclipseTemurin #Amazon #Coretto #AmazonCoretto
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/jdk11