#fcitx
Live, measured metrics for the hashtag #fcitx from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fcitx
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 · mas.to (Mastodon public tags API) · fetched 2026-10-17 22:46 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-17 22:46 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-17 22:46 UTCEverything below is measured over the latest 26 public posts (spanning ~47872 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (17) · Japanese (4) · Russian (1) · German (1) · Chinese (China) (1)
Avg boosts / post: 0.6
Top of the latest posts
Thanks to great work from @agx , typing #chinese is possible on phosh. So on my #FuriLabs #FLX1 I can natively type Chinese. It uses #uim behind the scenes. Before this I used to type in waydroid android container using #fcitx and copy it.
I am testing #Fedora 38 #KDE. I followed the wiki on how to set up #fcitx, but it doesn't work (switching input method is a no-op and typing just types English). I tried the same thing on Fedora 37 with the same results, and Fedora 36 didn'
Now seriously - is anyone using #fcitx and is happy with it? It switches the input as the mood takes. It never was as stable as ibus - how is that even possible? Or do I have the wrong hardware?
What “fcitx” means
WikipediaFcitx stands for Flexible Context-aware Input Tool with eXtension support, is an input method framework with extension support for the X Window System that supports multiple input method engines including Pinyin transcription, table-based input methods, fcitx-chewing for Traditional Chinese, fcitx-keyboard for layout-based ones, fcitx-mozc for Japanese, and fcitx-hangul for Korean.
“Fcitx” on Wikipedia (CC BY-SA) →#fcitx across platforms
every network with a public tag surfaceFollow #fcitx 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/fcitx