#s390
Live, measured metrics for the hashtag #s390 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #s390
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 07:16 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 07:16 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:16 UTCEverything below is measured over the latest 13 public posts (spanning ~61555 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (12) · German (1)
Avg boosts / post: 0.5
Top of the latest posts
@opensuse #YaST sprint highlights progress of Secure Boot for #s390 & fixes libstorage-ng code and its documentation, plus much more - https://bit.ly/YaSTs96
Anyone here that cares about all of the following or knows someone who does: * #s390 * #Fedora * #LinuxKernel I'm wondering if its worth enabling s390 for some or all of my kernel vanilla coprs[1]. It's likely not much work for me, but well
I wanted to build a server on Fedora for S/390, but I ran into some problems. I thought it was on Fedora, but upon studying the situation in more detail, I found out it was on QEMU/KVM. Regardless, it seems to me a problem that would not be
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/s390