Channel
@r_dotnet
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001967380955 |
|---|---|
| Type | Channel |
| Username | @r_dotnet |
| Description | .NET Community, if you are using C#, VB.NET, F#, or anything running with .NET... you are at the right place! https://www.reddit.com/r/dotnet Part of @reddit2telegram and @r_channels @JavaOfftopic |
| Created | Between 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/r_dotnet |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:48 | 9 | no change |
| 7 Aug 2026, 07:17 | 9 | first reading |
20 posts held, back to 22 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (22 July 2026 – 5 August 2026) |
| Views total | 43 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 10:48 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
How do production systems actually solve hard distributed systems problems? Most microservices tutorials stop at Auth, Product, Order Service, RabbitMQ, and Docker Compose. They rarely cover the problems that make distributed systems challenging. I'm curious how experienced engineers solve problems like: * Preventing double-booking under concurrent requests * Inventory reservation during flash sales * Idempotency …
Is there any valid reason to prefer sync over async for a DB-only API in .NET? I’m working on a backend for a marketplace application in C#/.NET and recently implemented a new API using async/await. During the PR review, one of the reviewers asked me to make the endpoint synchronous instead. Their reasoning was that the API only calls a stored procedure, the expected traffic is very low, and the application runs on …
Architecture Diagrams Disclaimer: My question isn't specifically about .NET. For those of you working as Senior/Principal Architects or Solution Architects, are you using any tools, workflows, or AI/LLM-based approaches to generate High-Level Design (HLD) documentation, especially architecture diagrams? I'm currently building a documentation generation workflow, and generating the written documentation is going re…
Application Insights bug - Dependencies telemetry is not sent with Activity This is a weeeird bug regarding application insights, and I can't seem to wrap my head around it. Hoping either I missed something, or that someone else saw this problem already. We're creating a long running job that handles multiple tasks at the same time. It calls an internal system and validates the state of some assets, and records the…
ExplorerFocus 1.2.11 — WPF file explorer I built with profiles, remote/cloud and built-in capture I'm the developer, and this is a solo project that's taken me a few months of work so far. To manage my personal and code documents I spend most of my day inside the same handful of folders, either on my machine or on remote ones — I need to reach them fast, and I often want to see what's inside a file without actually…
React/Vue/Svelte on top of MAUI Hi everyone, My team (.NET + web devs) needed to ship a desktop and mobile app from an existing React UI, and nothing in the ecosystem quite fit. Electron means a Node backend and shipping a whole Chromium. Tauri means Rust, which nobody on the team writes. MAUI/Avalonia/WPF means throwing away the React UI and rewriting it in XAML. Blazor Hybrid locks you into Razor. Photino was th…
AviyalWM: a portable and lightweight window manager for windows. https://redd.it/1v6jg3a @r_dotnet
An update on the world of PeachPDF PeachPDF is the HTML -> PDF engine I've been building for the last decade that renders HTML into PDF without using a headless browser or external process. We target .NET 8+, but we also multi-target .NET 10+. We support everywhere .NET 8+ runs, though some features don't work on certain platforms. As an example, iOS doesn't expose system fonts directly as font files, so you have t…
Rx.NET v7.0 Now Available https://endjin.com/blog/rx-dotnet-v7-0-released https://redd.it/1v61l6y @r_dotnet
First preview of ProGPU Avalonia rendering platform and Silk.NET windowing platform for Avalonia bringing powerful ProGPU WebGPU based rendering /r/ProGPU/comments/1v5kxst/first_preview_of_progpu_avalonia_rendering/ https://redd.it/1v5kyer @r_dotnet
metrics would you check for this type of problem? \- Any recommended tools for debugging TCP connection issues on Windows? I am still investigating and will update again if I find the cause. Thanks again to everyone who helped in the previous post! https://redd.it/1v5d7ws @r_dotnet
ASP.NET Core on IIS randomly goes offline for 2 minutes. no errors, no recycle, but TCP CLOSE_WAIT spikes Hi everyone, A few weeks ago I posted here about a strange production issue we were having: [https://www.reddit.com/r/dotnet/s/sdmADloeNS](https://www.reddit.com/r/dotnet/s/sdmADloeNS) First, I want to say thank you to everyone who replied there. The comments gave me a lot of ideas and helped me improve my mo…
Showing the 12 most recent of 20 posts we hold for @r_dotnet. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 1,171,783 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“r/DotNet” (@r_dotnet), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/r_dotnet.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.