#主機
Live, measured metrics for the hashtag #主機 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #主機
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-08-27 05:40 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-08-27 05:40 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-08-27 05:40 UTCEverything below is measured over the latest 4 public posts (spanning ~17413 hours).
Posting hours (UTC)
Languages: Chinese (Taiwan) (3) · Chinese (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
🌘 主機升級僅靠剪斷電線? ➤ 剪線解鎖的早期主機時代 ✤ https://alt.folklore.computers.narkive.com/nZagiUHj/mainframe-upgrade-done-with-wire-cutters 這篇文章探討了早期主機電腦中一種傳奇性的升級方式:透過剪斷電線來啟用被鎖定的處理器或記憶體。多位參與討論者分享了相關經驗和傳聞,指出這種做法可能與透過切換跳線器、移動電阻或修改迴路來達成效能提升有關。文章也回溯了早期電腦租賃模式,以
🌘 1981年IBM/Motorola主機控制晶片內部結構 ➤ IBM 3274控制單元晶片的內部結構和功能 ✤ http://www.righto.com/2024/07/ibm-3274-keystone-chip.html 本文探討了1981年IBM 3274控制單元晶片的內部結構。通過介紹主機和終端設備層次結構以及晶片的具體內部組成,深入解析了當時主機系統的運作方式和特點。 + 介紹了當時的主機系統,讓人對當時的技術水平有了更深入的瞭解。 + 對1981年的主機技術
🌗 我對Fediverse的使用- 所有的東西都由我自己架設- PeerTube、Mastodon和Lemmy- JTube ➤ 作者如何在Fediverse上自己架設PeerTube、Mastodon和Lemmy ✤ https://tube.jeena.net/w/nivehRx8J7ZwujfS2oCoPC 在這篇文章中,作者分享了他如何自己架設PeerTube、Mastodon和Lemmy等社羣網站,並提到了一些與使用JavaScript相關的問題和解決方法。 +
#主機 across platforms
every network with a public tag surfaceFollow #主機 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/主機