#cubieboard
Live, measured metrics for the hashtag #cubieboard from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cubieboard
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-30 00:31 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-30 00:31 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-30 00:31 UTCEverything below is measured over the latest 3 public posts (spanning ~0.4 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
Who wants a #Cubieboard 1 to tinker with? I do not want to invest time in devices with broken drivers.
under #debian sid & bookworm (stable) the NIC of the #cubieboard seems software broken. I get a link but no address(es). An USB NIC using the same network connection works fine. 😞
I tried to use #FreeBSD but my #Cubieboard did not see its SATA hdd. So back to #debian?
What “cubieboard” means
WikipediaCubieboard is/WAS a single-board computer, made in Zhuhai, Guangdong, China. The first short run of prototype boards were sold internationally in September 2012, and the production version started to be sold in October 2012. Several other versions from Cubieboard2 to 6 were produced between 2012 and 2017. The website for sales and support appears to have been unmodified with no response to essential software links being down since 2017.
“Cubieboard” on Wikipedia (CC BY-SA) →#cubieboard across platforms
every network with a public tag surfaceFollow #cubieboard 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/cubieboard