#schei_encoding
Live, measured metrics for the hashtag #schei_encoding from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #schei_encoding
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 22:34 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 22:34 UTCNo related tags with measured usage found for #schei_encoding.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:34 UTCEverything below is measured over the latest 6 public posts (spanning ~28629 hours).
Posting hours (UTC)
Languages: German (3) · English (3)
Avg boosts / post: 1.3
Top of the latest posts
Mensch, Datev. Wenn Du das mit UTF-8 im Jahr 2026 (ok, Dokument ist von 2025) immer noch nicht hinbekommst, dann verwende halt keine Umlaute. #DATEV #UTF8 #Umlaut #Schei_Encoding
Sch... (puny) Encoding bei OpenSSL: "the bugs were introduced as part of punycode decoding functionality" #schei_encoding https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/
It arrived albeit #FedEx fucked up all #umlauts in my shipping address, even in two different ways: Once they obviously took #UTF8 as #ISOLatin and once they seem to have taken one #8bit charset as another 8-bit charset, probably #ISOLatin1
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/schei_encoding