#coarrays
Live, measured metrics for the hashtag #coarrays from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #coarrays
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 09:53 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 09:53 UTCNo related tags with measured usage found for #coarrays.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 09:53 UTCEverything below is measured over the latest 3 public posts (spanning ~30068 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 3
Top of the latest posts
#GFortran 16.1 released. The great new feature is: - #Coarrays using native shared memory mulithreading on single node machines and handling #Fortran 2018's TEAM feature. See more changes on: https://gcc.gnu.org/gcc-16/changes.html
Which language/technology did you use when developing your first parallel program? #OpenMP? #MPI? #CUDA? #pthreads? #Coarrays? #UPC? Something else? #HPC
@Ruth_Mottram I don't know, probably. But since #Fortran 90/95, the language has evolved significantly: - Fortran 2003: object oriented programming (#OOP) and interoperability with C (iso_c_binding) - Fortran 2008: parallel programming with
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/coarrays