Channel
@DotNetIsFun
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
1,868subscribers
+12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001776738249 |
|---|---|
| Type | Channel |
| Username | @DotNetIsFun |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 3 times, most recently 18 September 2026 |
| On Telegram | t.me/DotNetIsFun |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 11:17 | 1,868 | -1 |
| 6 Sept 2026, 06:59 | 1,869 | +6 |
| 2 Sept 2026, 07:52 | 1,863 | +4 |
| 24 Aug 2026, 03:16 | 1,859 | -2 |
| 20 Aug 2026, 17:02 | 1,861 | +1 |
| 17 Aug 2026, 20:53 | 1,860 | +6 |
| 14 Aug 2026, 15:26 | 1,854 | -1 |
| 11 Aug 2026, 02:33 | 1,855 | -3 |
| 7 Aug 2026, 23:21 | 1,858 | +2 |
| 7 Aug 2026, 15:32 | 1,856 | no change |
| 7 Aug 2026, 14:02 | 1,856 | first reading |
20 posts held, back to 16 June 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
#شخصی این روزها با این حجم از خبرهای بد و استرسزا چطور کنار میاید؟ چطور ذهنتون رو آروم میکنید و از این فضای پر از اضطراب فاصله میگیرید؟ وقتی مدام خبرهای منفی میبینید، چطور نمیذارید ذهنتون سمت سناریوهای آخرالزمانی و بدترین حالتهای ممکن بره؟ واقعاً کنجکاوم بدونم هر کدوم چه راهکاری برای خودتون پیدا کردید.
با این پروژه میتونید هر کتاب رفرنس و یا داکیومنت کاری خودتون رو به یک Skill تبدیل کنید. مدل طبق الگوریتم ها و نکات اون کتاب کد بزنه یا خروجی بده. https://github.com/virgiliojr94/book-to-skill @DevTwitter | <کدلوژیست/>
اگر برنامهنویس باشید حتماً میدونید که بررسی کردن یه Pull Request گنده چقدر مکافاته و چقدر از تیم وقت میگیره! از اون طرف، تیکه تیکه کردن کارها تو چند تا برنچ مختلف و سر و کله زدن با Rebase کردنهای دستی هم دردسرهای خودش رو داشت. حالا گیتهاب یه قابلیت خیلی خفن به اسم Stacked Pull Requests معرفی کرده که این مشکل رو از ریشه حل میکنه. با این فیچر، شما میتونید اون تغییرات بزرگ کدهاتون رو به چند تا PR کوچیک، مرتب و لا…
یه بات اضافه کردیم برای جلوگیری از اسپم گروه یه بعد از ظهر کار و دیپلوی راحت با Dokploy ببینیم تا چه حد موثره. اگه موردی دیدید بگید @DotNetIsFun
از اسپم کردن گروه و کانال چی گیرتون میاد؟
CONTEXT! @DotNetIsFun
قبلاً اینکه بدونی یه تکنولوژی یا یه قابلیت چجوری کار میکنه یه مزیت بود. همین که کدت کار میکرد هم معمولاً کافی بود. ولی الان این دیگه مزیت نیست، حداقل انتظاره. بازار دیگه به کسی که فقط کدی بنویسه که کار کنه نیاز نداره. به کسی نیاز داره که بفهمه چرا این کد کار میکنه، زیر پوستش چه خبره، کجاها ممکنه به مشکل بخوره و چرا این راهحل رو انتخاب کرده نه یه راهحل دیگه. پس دیپ بشید. بیزنس رو بفهمید. مزایا، معایب و trade-o…
از Microsoft.Agents.AI به هیچ وجه غافل نشید. ایجاد ورک فلو و اضافه کردن مموری بهش واقعا ساده هست. کارای جالبی باهاش میتونید انجام بدید @DotNetIsFun
به شخصه توی پروژه هایی که مستقیم با AI ارتباط دارند Value Proposition ای برای Semantic Kernel نمیبینم. تقریبا ۹۰ درصد کار با Microsoft.Extensions.AI درمیاد. @DotNetIsFun
توی تیم هاتون همیشه حواستون باشه: آدمی که شنیده نشه بلندتر حرف میزنه ادمی که درک نشه دیگه حرفی نمیزنه
کلاد به کارتی که باهاش پرداخت شده ریفاند میکنه ( حتی اگه prepaid باشه) یعنی پول به کارت ایرانیکارت برمیگرده . بعد ایرانیکارت پولشو به شمایی که ازش خواستی برات بخره برنمیگردونه. عالیه
خنده دار اینجاست که ایرانیکارت هنوز فروشش رو نبسته و صرفا گفته اگه خرید کردید و حسابتون بن شد از این به بعد، عودت وجه نداریم و مسئولیتش با خودتونه
Showing the 12 most recent of 20 posts we hold for @DotNetIsFun. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“.NET Fun” (@DotNetIsFun), 1,868 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/DotNetIsFun.
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.