#rspec
Live, measured metrics for the hashtag #rspec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rspec
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-27 11:16 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-27 11:16 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:16 UTCEverything below is measured over the latest 40 public posts (spanning ~7589 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (38) · German (1)
Avg boosts / post: 0.6
Top of the latest posts
Lately I've found some resistance to use collection-based #rspec matchers Checking element by element is technically not wrong: expect(failure[:error]).to eq('Pusher error') expect(failure[:context]).to eq('notify_notification_started') but
ICYMI, I updated my RSpec testing book for Rails 8.1 and Ruby 4.0! Learn to test—and think about tests—the way I did, through a hands-on, full-stack approach. Minimal theory and dogma—just a straightforward, practical, and time-tested guide
Page 43, @benoit announced the "hidden draw" with the biggest letters possible. 😉 I guess Benoit is 100g of fun. And up top, 🌈 a rainbow in every marker he could reach, announced that you can find a Ruby friend in him. A :whyfox: fox RSpe
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/rspec