#LJC
Live, measured metrics for the hashtag #LJC from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ljc
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-10-30 01:41 UTC0 uses by 0 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-10-30 01:41 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-30 01:41 UTCEverything below is measured over the latest 9 public posts (spanning ~16272 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0.7
Used together with
Top of the latest posts
Visiting an #LJC (London Java Community) meetup at #Hazelcast this eve. Looks interesting 😊.
@kittylyst "I am, in general, sceptical of micro-benchmarks. For measuring Open Telemetry overhead, if you add it to hello world, the overhead will look enormous, because the app isn't doing anything! You need to measure on a realistic appl
Did I really hear @kittylyst say "sad lamb-da?" ... or was it "sad panda," and I just had my next demo on my mind? #LJC
#ljc across platforms
every network with a public tag surfaceFollow #ljc straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/ljc