#lakehouse
Live, measured metrics for the hashtag #lakehouse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lakehouse
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 02:17 UTC3 uses by 2 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 02:17 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 02:17 UTCEverything below is measured over the latest 40 public posts (spanning ~5037 hours).
Posting hours (UTC) — busiest: 08:00
Languages: Russian (22) · English (14) · Dutch (2) · German (1)
Avg boosts / post: 1.1
Top of the latest posts
Presented at the Berlin Open Lakehouse and AI Meetups, about WarehousePG. Finally found the time to write about the meetup. My talk was: How we made WarehousePG Open Source (again) All talks and recordings are linked in the blog posting. ht
Most ML issues are not model problems. They are data problems. I retrained the same churn model twice. Same code. Same path to the data. Different result. Why? Because of mutable data references. :blobcoffee: I wrote a small Data Lake vs Da
I'm presenting at the: Open Lakehouse and AI Meetup in Berlin tomorrow, about WarehousePG and how we made the product open source again. If you want to join, register here: https://luma.com/imejx9t2 #WarehousePG #OpenSource #Lakehouse #Meet
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/lakehouse