در یک حرکت اشتباه متاسفانه زدم سرور رو پاک کردم🫤 در روز های آتی دوباره فروارد ها از سر گرفته میشود
😐3❤1💔1😁1

Channel
@dev_perfects
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
39subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002201202057 |
|---|---|
| Type | Channel |
| Username | @dev_perfects |
| Description | بخوام خیلی خلاصه بگم این کانال میاد مطالب کانالای خفن تو حوزه تکنولوژی و برنامه نویسی رو جمع میکنه پست پین رو بخونید https://t.me/dev_perfects/455 ارتباط: https://t.me/HidenChat_Bot?start=936082426 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dev_perfects |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:01 | 39 | no change |
| 8 Aug 2026, 06:51 | 39 | first reading |
20 posts held, back to 19 November 2025 — 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.
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 19 November 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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 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.
7 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😐 | 3 | 42.9% | |
| 😁 | 2 | 28.6% | |
| ❤ | 1 | 14.3% | |
| 💔 | 1 | 14.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 19 November 2025 to 19 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
در یک حرکت اشتباه متاسفانه زدم سرور رو پاک کردم🫤 در روز های آتی دوباره فروارد ها از سر گرفته میشود
😐3❤1💔1😁1
Separate your Cloudflare page cache with a middleware group https://t.me/iv?url=https://laravel-news.com/separate-your-cloudflare-page-cache-with-a-middleware-group&rhash=8fee474e8a1638
🔶 از سر بیکاری فریم ورک CSS ساختم 🚬 @TheRaymondDev
Video, posted without a caption
از بعد از جنگ از ۲ تا از دوستان فعال در حوزه اینترنت آزاد بیخبر موندم و حقیقتش نگران وضعیشونم. اسم نمیارم، ولی امیدوارم از همین طریق پیامم رو ببینن، یا خبری از وضعیت و سلامتیشون بهم برسه. 🔍 ircf.space @ircfspace
تمپلیت r1ec honojs رو یسری تغییرات بهش دادم که خیلی تجربتون بهتر شه: - سیستم بیلد جدید با rollup - استفاده از تایپ اسکریپت - آنالیز کامل باندل سایز پس از بیلد - دیپلویمنت راحت تر از اینجا میتونید Use this template رو بزنید و شروع کنید: https://github.com/amirparsadd/r1ec-edge-hono @DevTwitter | <Amirparsa Baghdadi/>
حوصلم سررفت و تیبل تسکهام از نوشن رو وصل کردم به یه مدل ساده. تا هنوز کامل جایگزین نشدیم یکم لذت ببریم از سرعت کدزدن با AI https://github.com/alirezasakhaei/Notion-AI-Integratoin @DevTwitter | <سخا/>
این AGI ما چی شد؟!؟!؟ @reza_jafari_ai
سلام ، امیدوارم که حالتون خوب باشه برای رفع نیاز خودم یک داشبورد نوشتم برای مرورگر های کروم و ادج تصمیم گرفتم منتشرش کنم ، اگر شما هم به کارتون میاد میتونید دانلود و نصب کنید. دانلود از گیت هاب : https://github.com/ehsanerfani98/bookina @DevTwitter | <Ehsan Bavaghar/>
علت قطعی بزرگ اینترنت دیروز : کلادفلر یه سیستم ضد رباته، هر چند دقیقه یه فایل feature میسازه که به مدلهای ضدرباتش به صورت به روز بگه چه چیزی رفتار آدمه و چه چیزی رباته. اگه این کارو نکنه ربات ها مدل های ضد رباتش رو گول میزنن، این فایل معمولاً اندازهی ثابتی داره، حالا یه مشکل باعث شده بود این فایله بزرگ تر از حد معمول بشه. کُدِ مسیریاب اصلی (proxy) برای سرعت، حافظه رو از قبل تخصیص میداد و انتظار داشت تعداد ویژگ…
🔶 خلاصه قطعی کلودفلر در ۱۸ نوامبر ۲۰۲۵ قطعی از ساعت ۱۱:۲۰ UTC شروع شد و تا ۱۴:۳۰ ادامه داشت. تمام سرویس ها تا ساعت ۱۷:۰۶ به حالت عادی برگشتند. این بدترین قطعی کلودفلر از سال ۲۰۱۹ بود. علت اصلی: تغییر در مجوز های یک پایگاه داده باعث شد فایل پیکربندی سیستم Bot Management دو برابر شود و از حد مجاز عبور کند. این فایل بزرگتر به تمام سرور های شبکه ارسال شد و نرم افزار مسیر یابی ترافیک را مختل کرد. جزئیات فنی: - یک کو…
طبق گفته FFmpeg پچ جدید باعث شده یه تابع مهم تو پردازش ویدیو ۳.۴۶ برابر سریعتر بشه. ماجرا اینه که یکی از کانتریبیوترها به اسم mkver اومده تابع add_8x8basis_sse3 رو که قبلاً با C نوشته شده بود رو کاملا با اسمبلی x86 بازنویسی کرده و خروجی هم شده همین جهش سرعت جدی. دلیلش اینه که کامپایلرهای GCC و Clang وقتی با فلگ O3 کد رو کامپایل میکنند، معمولاً یه سری حلقه هایی که اصلاً قرار نیست زیاد اجرا بشن رو باز میکنن و کد رو…
Showing the 12 most recent of 20 posts we hold for @dev_perfects. 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Dev Perfects” (@dev_perfects), 39 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/dev_perfects.
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.