#wlr
Live, measured metrics for the hashtag #wlr from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #wlr
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-07-27 22:10 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-07-27 22:10 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 22:10 UTCEverything below is measured over the latest 7 public posts (spanning ~14659 hours).
Posting hours (UTC)
Languages: English (6) · German (1)
Avg boosts / post: 2.1
Top of the latest posts
#wayland - a never ending story... #sway gestartet: "Oh, Dein Monitor hat eine Auflösung von 2560x1080, die nehm' ich". Monitor auf anderen Eingang umgeschaltet, später zurück. #sway und #wlr-randr: "Das Gerät kann nur 1024x768, leb' damit"
Does anybody know how to set a custom refresh rate on wlr compositors, specifically Sway? By that, I mean, to sacrifice resolution for more refresh rate. #wlr #sway #wayland
... and it stopped working again in flatpak OBS, while still working fine in #OBS from #ArchLinux repo. This is crazy. It's really hard to troubleshoot since I have no domain knowledge, and this is not a crash. The #WLR portal just receives
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/wlr