#jres19
Live, measured metrics for the hashtag #jres19 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jres19
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 20:02 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 20:02 UTCNo related tags with measured usage found for #jres19.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:02 UTCEverything below is measured over the latest 27 public posts (spanning ~257 hours).
Posting hours (UTC) — busiest: 15:00
Languages: French (27)
Avg boosts / post: 1
Top of the latest posts
Vous pouvez trouver les diapositives de ma présentation en ligne sur notre site. http://eole.ac-dijon.fr/presentations/2019-12-JRES/jres-2019-opennebula.pdf #OpenNebula #JRES #JRES2019 #JRES19 (cc @Troupier @EOLE)
@publisher_2019 Présentation super claire. @bortzmeyer nous parle de distribution de supervision, tacle @LesJRES pour l’absence d’IPv6 sur le site des #JRES et place @FDN comme ça l’air de rien. Il défonce aussi un certain système d’exploit
C'est #BeeGFS et non pas BeegsFS Le client est #GPLv2 mais tout le reste est en « BeeGFS EULA » dont la lecture ultra diagonale m'inquiète un peu « All enterprise features are disabled by default. » Ne serais-ce pas #OpenCore ? https://www.
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/jres19