#dataeng
Live, measured metrics for the hashtag #dataeng from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dataeng
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:59 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:59 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:59 UTCEverything below is measured over the latest 11 public posts (spanning ~30702 hours).
Posting hours (UTC)
Languages: English (10) · French (1)
Avg boosts / post: 5.6
Top of the latest posts
I've been looking into dbt for data engineering and wanted to flesh out what the similarities and differences were to just using {targets} - I learned lots about both of them! I wrote up my findings in this post https://jcarroll.com.au/2026
#JeRecrute un ou une #dataengineer pour le datalab de #VIGINUM, le service en charge de la lutte contre les ingérences numériques étrangères en France. N'hésitez pas à postuler. https://www.welcometothejungle.com/fr/companies/viginum/jobs/i
hey all👋🏻 finally getting around to my #introduction :linux: i lead + manage a small data science + product team at LA county department of public health and do some consulting from time to time too :terminal: i work mostly in #rstats and
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/dataeng