#collisiondetection
Live, measured metrics for the hashtag #collisiondetection from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #collisiondetection
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:05 UTC1 uses by 1 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:05 UTCNo related tags with measured usage found for #collisiondetection.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:05 UTCEverything below is measured over the latest 9 public posts (spanning ~52586 hours).
Posting hours (UTC)
Languages: English (7) · German (2)
Avg boosts / post: 0.2
Top of the latest posts
Comprehensive basics of collision detection. https://www.jeffreythompson.org/collision-detection/index.php #programming #math #collisiondetection
🚀 Oh, look! Another riveting dissertation on #SIMD collision detection—because who wouldn't want to spend their weekend pondering graph coloring in Box3D? 🙄 Wide SIMD vs. narrow SIMD: because apparently, some collisions are just too compl
#APLQuest 2015-06: Write a function that takes, as each of its right and left arguments, a pair of co-ordinates representing diagonally opposite corners of two rectangles and returns a 1 if the rectangles overlap (see https://apl.quest/2015
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/collisiondetection