Telegram RegisterThe public register of Telegram

Channel

Diyorbek.dev | 👨🏻‍💻

@Diyorbekk_dev

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

175subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001548077192
TypeChannel
Username@Diyorbekk_dev
DescriptionAllohga taqvo qiling. Va Alloh sizga ilm beradi. [2:282] Software engineer @ Octane Core Team Dasturchi, jiddiy, kamgap, oddiy inson Òzim haqimda kòproq ma'lumot uchun: @Diyorbek_juraev_blog Web sahifam: https://mrdiyorbek.uz/
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Diyorbekk_dev

Growth

1756 August 2026 — 175 subscribers8 August 2026 — 175 subscribers6 August 20268 August 2026
2 measurements spanning 2 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 174–176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:01175no change
6 Aug 2026, 10:46175first reading

Engagement

19 posts held, back to 29 July 2026the 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 · 30 days
225.8%
avg views ÷ 175 subscribers
Avg views / post
395
19 posts measured
Reaction rate
1.58%
reactions ÷ views · ER floor
Posts in window
19
of 19 held

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. It is computed over the 17 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held19 (29 July 20267 August 2026)
Views total7,508
Reactions total97
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 14:01 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.

What this channel posts

Photos
280
Videos
31
Links
111

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
32s
Average length
32s

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.

Reaction mix

97 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 61.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6061.9%
1919.6%
1010.3%
🆒55.15%
👍33.09%

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 17 of the 19 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 97reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 29 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 19:14 UTC194 views7 reactionsread 8 August 2026

#insight Hozirgi Seniorlarni eng asosiy vazifasi, juniorlarni Senior qilishlik.

7

Signed Diyorbek Juraev

7 Aug 2026, 12:23 UTC219 views8 reactionsread 8 August 2026

Bu postga kòra maqolani publish qildim. AI davrida review workflow qanday o’zgarayotgani haqida yozdim. https://mrdiyorbek.uz/blog/ai-davri-review-workflow Share qilish esdan chiqmasin

5🔥3

Signed Diyorbek Juraev

7 Aug 2026, 06:00 UTC205 views4 reactionsread 8 August 2026
Photo

Endi Lynx va Octane bilan Native ilovalar yaratish mumkin. Octane yordamida Lynx orqali iOS va Android uchun native ilovalar yarating. Quyidagi misollar skrinshot emas, ular brauzerning o'zida jonli demo ko'rinishida ishlamoqda https://octanejs.dev/docs/lynx Ha yana bir gap, Hooks, Context, Suspense va Transitions odatdagidek ishlaydi. Faqat yuqori tezlik talab qiladigan kodni main thread'da ishlatish kifoya. Octa

2🆒2

Signed Diyorbek Juraev

6 Aug 2026, 14:07 UTC196 views5 reactionsread 8 August 2026

Hozirda ko‘pchilik duch kelayotgan bitta muammo bor. AI yaratgan giant PR 'larni nazarda tutyapman. Agar qiziq bo‘lsa, ularni qanday qilib review qilish oson bo‘lgan kichik PR stacklarga ajratish metodikasini tushuntirib beraman. Bugun shu mavzuni Octane Team ichida ham ko‘tardim. Kechki payt bu bo‘yicha discussion boshlanishi kerak. Let’s go deseylar, kommentariyada + qoldirib keting. Bo‘lmasa, step by step bos

🔥4👍1

Signed Diyorbek Juraev

6 Aug 2026, 04:44 UTC238 views9 reactionsread 8 August 2026
Photo

Never Compare yourself to others!

🔥63

Signed Diyorbek Juraev

5 Aug 2026, 12:26 UTC245 views4 reactionsread 8 August 2026
Video

Endi useState ni Sony PSP’da ham ishlatish mumkin 😎 Rostini aytsam, bunaqasini ko’raman deb o’ylamagandim. React bu qurilmada ishlamaydi, lekin Octane ishlaydi. Chunki u React’dagi JSX va hook’larni PocketJS’ning native UI tree’siga compile qiladi. Hech qanday Virtual DOM yoki reconciler kerak emas. PocketJS 0.8.0 bilan Octane endi first-class qo’llab-quvvatlanadi. Eski PSP’da zamonaviy frontend dasturlash usullar

🔥3👍1

Signed Diyorbek Juraev

5 Aug 2026, 04:02 UTC256 views3 reactionsread 8 August 2026
Video

You can define TypeGPU shader functions ('use gpu' directive) in @octanejs component files (.tsx/tsrx) and it works without a hitch! Very excited to play more with this integration https://github.com/iwoplaza/typegpu-octane-example

🔥21

Signed Diyorbek Juraev

4 Aug 2026, 18:47 UTC254 views2 reactionsread 8 August 2026
Photo

https://tanstack.com/table/latest/docs/framework/octane/examples/kitchen-sink?panel=code Octane + TanStack Table.

2

Signed Diyorbek Juraev

4 Aug 2026, 15:54 UTC293 views6 reactionsread 8 August 2026

ASD-STE100 Internetda juda qiziq bir narsaga duch kelib qoldim. QQ: hozirgi AI workflow’ingizda AI uchun yozilgan documentation qanchalik AI tushunishi oson deb o’ylaysiz? 1970-yillarning oxirida Yevropa aviakompaniyalari so’roviga binoan ASD-STE100 (Simplified Technical English) standarti ishlab chiqilgan. O’sha paytda mutaxassislarning qariyb 80% uchun ingliz tili ikkinchi yoki uchinchi til edi. Bilamizki Ingli

🔥42

Signed Diyorbek Juraev

4 Aug 2026, 08:33 UTC208 views7 reactionsread 8 August 2026
Photo

Position Changed. Oldinlari Communityda men ko'proq savol berar edim, hozir esa maintainer sifatida savollarga javob berishni boshladim. To’g’ri savollar vaqt o’tishi bilan tajribaga, tajriba esa boshqalarga yordam bera olishga olib keladi. Keyingi maqsad yana ham tajribalarni oshirib, teamdagi Founder Engineerlar kabi Founder va dunyodagi top engineerlar qatoriga kirishlik bo'ladi. Aytmoqchi bugun kechroq AI bo'

🔥43

Signed Diyorbek Juraev

3 Aug 2026, 09:36 UTC256 views6 reactionsread 8 August 2026
Photo

Bir hafta ichida 1000+ GitHub stars. 💪 https://github.com/octanejs/octane

🔥51

Signed Diyorbek Juraev

3 Aug 2026, 05:55 UTC288 views5 reactionsread 8 August 2026
Photo

Octane + NextJs or OctaneX? Kuni kecha Octane core jamoasida juda qiziq architecture discussion bo’lib o’tdi. Rostini aytsam, shu vaqtgacha framework architecture’sining low-level qismiga bunchalik chuqur kirib ko’rmagan ekanman. Dastlab gap Server Components haqida ketayotgandi. Oxirida esa butunlay boshqa savol paydo bo'ldi. Octane Next.js bilan ishlashi kerakmi yoki Octane o’zining meta framework’iga ega bòli

🔥5

Signed Diyorbek Juraev

Showing the 12 most recent of 19 posts we hold for @Diyorbekk_dev. 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

Citation-graph rank — 228,040 of 1,160,990entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 6 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.

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.

Cite this entry

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Diyorbek.dev | 👨🏻‍💻” (@Diyorbekk_dev), 175 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Diyorbekk_dev.

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.