#serde
Live, measured metrics for the hashtag #serde from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #serde
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 08:43 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 08:43 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:43 UTCEverything below is measured over the latest 40 public posts (spanning ~21319 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (32) · Russian (3) · Chinese (Taiwan) (2) · Swedish (1)
Avg boosts / post: 1.9
Top of the latest posts
Today, I once again wake up worrying about #Rust 's future. Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned f
🚩 SAVE THE DATE My online talk about how to speed up #Rust serialization with #serde by up to 2.25x 🚀 What to expect: 🙂 A simple example with JSON 🧐 How serialization in serde works 🛠️ Manually implementing the Serialize trait 🌟 Seria
Rust's serde should really support default literals! 🦀 ➡️ Read more: https://serde.rs/attr-default.html ✨ Tracking issue: https://github.com/serde-rs/serde/issues/368 #rustlang #serde #serialization
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/serde