#localmodel
Live, measured metrics for the hashtag #localmodel from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #localmodel
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 13:50 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 13:50 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:50 UTCEverything below is measured over the latest 16 public posts (spanning ~5677 hours).
Posting hours (UTC) — busiest: 22:00
Languages: English (16)
Avg boosts / post: 0.1
Top of the latest posts
Unsloth AI (@UnslothAI) 현재 가장 많이 사용하는 로컬 모델이 무엇인지 묻는 질문으로, 로컬 LLM 선택 트렌드를 파악하는 데는 참고가 되지만 구체적 기술 정보나 새로운 인사이트는 없습니다. https://x.com/UnslothAI/status/2070140617758486997 #localmodel #llm #ai #discussion
Dilum Sanjaya (@DilumSanjaya) 로컬 모델로 실험한 사례를 공유했다. 예시에서는 모든 요청을 Gemma 4가 처리하며, 프롬프트에 따라 새로운 회로를 JSON으로 생성한다. 클립의 대기 시간은 편집됐지만 실제 응답 시간은 보통 5~10초 수준이라고 설명했다. https://x.com/DilumSanjaya/status/2070187709361254669 #localmodel #gemma #json #pro
Eric Building... (@outsource_) 로컬 모델 기준 2,000 TK/S라는 매우 높은 처리량을 소개하며, Unsloth AI 팀의 최적화 성과를 강조합니다. 로컬 추론 성능 개선 사례로 개발자 관점에서 참고할 만합니다. https://x.com/outsource_/status/2065462780589731949 #unsloth #localmodel #throughput #inference #llm
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/localmodel