#corewars
Live, measured metrics for the hashtag #corewars from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #corewars
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 14:33 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 14:33 UTCNo related tags with measured usage found for #corewars.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 14:33 UTCEverything below is measured over the latest 11 public posts (spanning ~36643 hours).
Posting hours (UTC)
Languages: English (11)
Avg boosts / post: 0.5
Top of the latest posts
So there is another competition coming up, this time from Inversed: http://inversed.ru/CoreWar_Challenge_2.htm This competition uses the "nano" parameter set with warriors having a maximum of 5 instructions in an 80 location space. Fights a
Just having a little read up on Fibonacci Hashing. It seems to me that it should produce optimum step sizes for covering core in a useful manner but the problem is calculating it in an efficient manner in a loop ... I have some thoughts! #C
Started to have a look at the Core War Fortress Hill on SAL which specifies a write limit. So I need to upgrade from pMars 0.9.2 to 0.9.4 ... maybe they have fixed the compile errors on Linux ... nope. Patched the source to eliminate errors
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/corewars