#comparch
Live, measured metrics for the hashtag #comparch from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #comparch
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-24 09:58 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-24 09:58 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-24 09:58 UTCEverything below is measured over the latest 10 public posts (spanning ~39378 hours).
Posting hours (UTC)
Languages: English (7) · Italian (1)
Avg boosts / post: 2.6
Top of the latest posts
I'm investigating the original Berkeley RISC-I CPU out of historical interest and wonder why some instructions use more than one opcode (e.g. LDHI uses 16 opcodes 0x70...0x7F). I can't see why this is necessary – is this an optimization or
Pavel Píša: Advanced Computer Architectures – 13 – ARM and RISC-V [M35PAP Winter 25/26] https://vhsky.cz/w/6Gn66TrgksWEaQozVMQj4b
Pavel Píša: Advanced Computer Architectures – 12 GPU and GPGPU [M35PAP Winter 25/26] https://vhsky.cz/w/tfQKzuM8zqpFDAejc8GLEd
#comparch across platforms
every network with a public tag surfaceFollow #comparch 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/comparch