#sourcegenerator
Live, measured metrics for the hashtag #sourcegenerator from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sourcegenerator
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 11:43 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 11:43 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:43 UTCEverything below is measured over the latest 11 public posts (spanning ~26211 hours).
Posting hours (UTC)
Languages: English (9) · Polish (1) · Russian (1)
Avg boosts / post: 1
Top of the latest posts
My kingdom for the ability to exclude source generated code from usage definition searches. “Oh god this class I’m about to refactor has 268 usages” “oh god it’s all in source generated files” I could probably set a search filter to exclude
A workaround could be to use my source generator to also generate a test helper class with the syntax tree as a string. Feels a bit icky but it seems workable. #dotnet #sourcegenerator #unitest
So am I the only one struggling with using `IncrementalValueProvider<string?>` with `ForAttributeWithMetadataName` in a #dotnet #sourcegenerator? I would have loved to alter the namespace of my attribute using an MSBuild prop, but it seems
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/sourcegenerator