#multiseat
Live, measured metrics for the hashtag #multiseat from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #multiseat
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-09-30 02:29 UTC1 uses by 1 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-09-30 02:29 UTCNo related tags with measured usage found for #multiseat.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-30 02:29 UTCEverything below is measured over the latest 13 public posts (spanning ~57214 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (10) · German (3)
Avg boosts / post: 0.9
Top of the latest posts
Alright, with a little change in SDL to also return device IDs in "absolute mode", I can now write multi-mouse applications in the LÖVE game engine! \o/ Here's a little physics playground! Already a lot of fun with two people! :D #love2d #s
Also got multiple keyboards to work! Made a little testing program where two people can play "scrabble" by moving their mouse and stamping letters! :D #multiseat
On my 2nd job we're developing "MST" -- an open source/free software solution for multi-seat configuration: https://gitlab.com/gkaz/mst To test it in production we've deployed MST on several workplaces in our local college and it works quit
#multiseat across platforms
every network with a public tag surfaceFollow #multiseat 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/multiseat