#risc
Live, measured metrics for the hashtag #risc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #risc
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-09-15 04:03 UTC1 uses by 1 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-09-15 04:03 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-15 04:03 UTCEverything below is measured over the latest 40 public posts (spanning ~1581 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (27) · Italian (3) · Chinese (Taiwan) (2) · Russian (2) · Spanish (2) · Japanese (1)
Avg boosts / post: 0.7
Top of the latest posts
هل معمارية RISC-V أصبحت جاهزة فعلًا للاستخدام اليومي؟ 🤔 في هذه التجربة أستخدم لوحتي Orange Pi R2S وOrange Pi RV2 وأحوّلهما إلى راوتر وسيرفر منزلي، لأرى كيف أداء ودعم RISC-V في الاستخدام اليومي. أختبر الأداء، استهلاك الطاقة، تشغيل الخدمات،
NetBSD 11.0 released 👉 https://netbsd.org/releases/formal-11/NetBSD-11.0.html 𝗡𝗲𝘄 𝗽𝗼𝗿𝘁 𝘁𝗼 𝘁𝗵𝗲 #𝗥𝗜𝗦𝗖-𝗩 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗼𝗿 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲. #NetBSD 11.0 is the first stable release to include support for 64-bit RISC
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
#risc across platforms
every network with a public tag surfaceFollow #risc 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/risc