#lollms
Live, measured metrics for the hashtag #lollms from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lollms
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.social (Mastodon public tags API) · fetched 2026-10-16 17:44 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.social (Mastodon public search API) · fetched 2026-10-16 17:44 UTCNo related tags with measured usage found for #lollms.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-16 17:44 UTCEverything below is measured over the latest 2 public posts (spanning ~24417 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
CVE-2026-10595 - Path traversal in lollms v2.1.0 lets unauthenticated attackers read arbitrary files via encoded dot-dot sequences. CVSS 7.5. No patch yet—disable or isolate service immediately. #CVE #infosec #lollms https://www.valtersit.c
How to install #petals #distributed #ai model via #lollms as well as other models like #gpt4all. Petals integration was made possible by a SCI-funded bounty and our generous donors, thank you! https://www.youtube.com/watch?v=a5TqNp49giU
#lollms across platforms
every network with a public tag surfaceFollow #lollms 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/lollms