#corescore
Live, measured metrics for the hashtag #corescore from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #corescore
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.social (Mastodon public tags API) · fetched 2026-07-27 11:15 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.social (Mastodon public search API) · fetched 2026-07-27 11:15 UTCNo related tags with measured usage found for #corescore.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 11:15 UTCEverything below is measured over the latest 2 public posts (spanning ~19471 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
Vivado ran for 4h53m overnight for 7,000 SERV cores, and there's room for more! Naively, 7000/.83 = 8,433. P&R difficulty increases nonlinearly, so I won't go straight to 8,443. But… how about 8,300? I think I can take second place 😎 #FPGA
Edalize 0.5.4 was just released, with among other things, support for the Efinix Efinity flow. And what better way to celebrate support for new devices than seeing how many RISC-V cores we can fit into them. Turns out that my Efinix Xyloni
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/corescore