#USRSE23
Live, measured metrics for the hashtag #USRSE23 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #usrse23
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 23:58 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 23:58 UTCNo related tags with measured usage found for #usrse23.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:58 UTCEverything below is measured over the latest 40 public posts (spanning ~175 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (40)
Avg boosts / post: 1.7
Top of the latest posts
What IF we could publish using notebooks?? excited to see @2i2c_org have a present at this meeting today! James Monroe is presenting now in the notebooks session about using the Jupyter ecosystem Lots of energy & enthusiasm coming from Jame
takeaway: one of the biggest positive take aways from code review is knowledge sharing #usrse23 #python #opensource #science
excited to read this paper on the value / challenges etc of code review in scientific software. we have spent a lot of time documenting our code review process in our peer review guide here: https://www.pyopensci.org/software-peer-review/ a
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/usrse23