#subjectindexing
Live, measured metrics for the hashtag #subjectindexing from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #subjectindexing
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-24 00:31 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-24 00:31 UTCNo related tags with measured usage found for #subjectindexing.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-24 00:31 UTCEverything below is measured over the latest 17 public posts (spanning ~26529 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (11) · German (5) · Finnish (1)
Avg boosts / post: 5.6
Top of the latest posts
Earlier this year, the Annif team participated in the LLMs4Subjects challenge, where our automated indexing tool performed nicely! 🏆 We also got new ideas for Annif development out of the challenge! The SemEval-2025 workshop proceedings ar
... that AI–gold-standard disagreements that coincided with disagreements between the human evaluators were more frequent for Gemini (66.67%) than for ChatGPT (39.13%). The LLMs suffer from deficiencies evaluating incorrectly assigned descr
Tag 2 des KIM Workshops! Es geht 9:30 Uhr los mit: 🧠 Argie Kasprzik & Lakshmi Rajendram Bashyam (ZBW) – AI for automated subject indexing (Englisch) Wie lässt sich Bibliotheks‑Data für Machine‑Learning nutzbar machen? #kimws26 #AI #Subject
#subjectindexing across platforms
every network with a public tag surfaceFollow #subjectindexing 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/subjectindexing