#jdtls
Live, measured metrics for the hashtag #jdtls from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jdtls
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 14:40 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 14:40 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:40 UTCEverything below is measured over the latest 8 public posts (spanning ~37417 hours).
Posting hours (UTC)
Languages: English (4) · German (3)
Avg boosts / post: 0
Top of the latest posts
Ok, you can just replace the directories in $HOME/.local/share/nvim/mason/packages/jdtls with ones from jdtls v1.58.0 and it works. #java #nvim #neovim #jdtls
A few days ago the maintainers of #homebrew accepted my contribution to bring #eclipse #languageserver a.k.a. #jdtls to this #packagemanager. :ablobcatbongo: However, the workflow of accepting a #contribution in #homebrew is weird and frank
AI coding tools don’t fail on Java projects because Java is too hard. They fail because the tool has no map of your repository, no real symbol knowledge, no file boundaries, and no written conventions. I wrote up a hands-on way to fix that
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/jdtls