#fluidsimulation
Live, measured metrics for the hashtag #fluidsimulation from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fluidsimulation
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 12:11 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 12:11 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:11 UTCEverything below is measured over the latest 40 public posts (spanning ~23262 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (22) · German (17) · French (1)
Avg boosts / post: 2
Top of the latest posts
Here is the result in the #FluidSimulation. And it creates quite a mess. I'm really not satisfied. My next idea is a "reshape" algorithm, that will find the shortest path from input to output (also favoring lower altitude), and then spread
Just fixed another #FluidSimulation bug. Water could overflow through the roof 🫣 This was a bit hard to spot because usually you don't get to see what happens inside the terrain. So let's take a look behind the scenes. Or under the scene a
"Fluid fun with py5 and NumPy" https://discourse.processing.org/t/fluid-fun-with-py5-and-numpy/47943 #CreativeCoding #py5 #NumPy #fluidsimulation
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/fluidsimulation