#floatingpoint
Live, measured metrics for the hashtag #floatingpoint from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #floatingpoint
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 07:32 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 07:32 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:32 UTCEverything below is measured over the latest 40 public posts (spanning ~6954 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (38) · Russian (1) · French (1)
Avg boosts / post: 1.2
Top of the latest posts
New blog post! I really hope I'll get a decent amount of people mad with this one 😈😈😈 It's OK to compare floating-points for equality: https://lisyarus.github.io/blog/posts/its-ok-to-compare-floating-points-for-equality.html #programming
Somewhat inspired by @erin_catto releasing Box3D I've tossed together a header for attempting to detect "hostile" floating point compiler options. The idea is an attempt (with minimal friction) to spot problems including peeps that grab and
Same theme as "checking" floating-point options: a clean-up and better commented version of "override all the options I can" in a header. https://github.com/Marc-B-Reynolds/fp_compiler_shield/blob/main/fp_compiler_hammer.h example: https://
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/floatingpoint