Channel
@uzbek_developer_blog
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
68subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001708554781 |
|---|---|
| Type | Channel |
| Username | @uzbek_developer_blog |
| Description | 💻 Let's get acquainted with IT news ✍️ Author: @uzbek_coder_2022_bot or @uzbek_developer_support 🌐 Web-site: uzbekdeveloper.uz 🔸 Scientists investigate that which already is 🔹 Engineers create that which has never been! (👤 Albert Einstein) |
| Created | Between 1 December 2021 and 31 March 2023— 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/uzbek_developer_blog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 00:46 | 68 | no change |
| 7 Aug 2026, 18:43 | 68 | first reading |
15 posts held, back to 26 February 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 4 July 2026. 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 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.
7 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 57.1% | |
| ⚡ | 1 | 14.3% | |
| ❤🔥 | 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 7 of the 15 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 15 most recent posts we hold, published 26 February 2026 to 4 July 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.
Qiziq narsa ekan. gitfut.com da o'z GitHub(FIFA) cardingizni toping va comments qismida share qiling. Coding bo'yicha jahon chempionatiga tarkibni hal qilib olaylik 😄
SI uchun o'zbekcha gapirish bitta devorni qurishda 4 baravar ko'p g'isht ishlatishdek gap. Natijada o'zbekcha promptlar 15 baravar qimmatga tushadi. Tejamkorlik siri: ko'rsatmalarni (bepul tarjimonlar yordamida) inglizcha berib, yakuniy javobni o'zbekcha oling. Shunda xarajatni 70% gacha qisqartirasiz. Koʻproq foydali tavsiyalar uchun albatta kanalga obuna boʻling. @ertagakech
⚡1👍1
Yetib kelganimiz shu bo'lsin) Claude Adobe bilan integratsiyasini e'lon qildi, endilikda promptlar orqali dizayn tayyorlash, tahrirlash ishlari va yana boshqa Adobe dasturlarini imkoniyatlarini birgina promptda qilish mumkin bo'ladi. Qani iloho omin 🤲
👍2
Vercel’ni xakerlar urib ketdi. Eng qo‘rqinchli joyi esa hujumning o‘zi emas, unga eshikni odamning o‘zi ochib bergani. Vercel’ning bayonotiga ko‘ra, gap uchinchi tomon AI vositasi — Context.ai — orqali boshlanganida: bir xodim ish akkaunti bilan kirib, OAuth ruxsatini berib yuborgan, xakerlar esa shu yo‘l bilan systemaga kirgan. Ayrim nashrlar xakerlar o‘g‘irlangan ma’lumot uchun $2 mln so‘rayotganini yozayapti. Ham…
👍1
🚨 Lovable.dev’da ma’lumotlar sizib chiqdi: Agar siz Lovable.dev platformasi orqali biror loyiha yaratgan bo‘lsangiz, hushyor bo‘ling! Tizimdagi jiddiy xatolik sababli 48 kundan beri shaxsiy ma’lumotlaringiz va yozgan kodlaringiz hamma uchun ochiq bo‘lib qolgan bo‘lishi mumkin. manba: https://www.cyberkendra.com/2026/04/lovable-left-thousands-of-projects.html
🟦🟦🟦 “UzGeeks Conf 2026”GA TAKLIF ETAMIZ! ⚜️Joriy yilning 25-aprel kuni UzGeeks hamjamiyatining 10 yilligi munosabati bilan “UzGeeks Conf 2026” tadbiri boʻlib oʻtadi. 🏷Ushbu tadbirda yillar davomida oʻtkazilgan meetuplar sarhisobi, hamjamiyat erishgan yutuqlar hamda bir-biridan qiziq mavzularda chiqishlar boʻladi. ➡️“UzGeeks Conf 2026” rejasi quyidagicha: 1. Klassik Product managementdan AI Startup Product manage…
Olimpiada darajasidagi dasturlash va matematika vazifalari bilan oʻzingizni sinab koʻring. Eng kuchli ishtirokchilar Yandex'dan imkoniyatlarga ega boʻladi. Yandex Coding and Math Contest endi Oʻzbekistondagi 18 yoshdan katta oliy o‘quv yurtlari talabalari, dasturchilar, muhandislar va IT-mutaxassislari uchun ochiq. Agar siz algoritmlar, matematika va zamonaviy dasturlash tillarida oʻzingizga ishonsangiz, 2026-yil …
"System Design" desa qo'rqadiganlar bormi? Shu yakshanba shu qo'rquvni yo'qotishga harakat qilamiz. Stream. Vaqtini aniqlashtiraman.
Sizni Stanford University HAI bilan bepul vebinarga taklif etamiz 👇 26-mart kuni sun’iy intellekt sohasidagi yetakchi tadqiqot markazi - Stanford University Human-Centered AI Institute (Stanford University HAI) boshqaruvchi direktori jonli efirda sun’iy intellekt bo‘yicha global trendlar bilan bo’lishadi. AI Index Stanford universitetining yillik hisoboti bo‘lib, u butun dunyo bo‘ylab sun’iy intellektning holati va…
Raqamli texnologiyalar va sun’iy intellektni rivojlantirish ilmiy-tadqiqot instituti hamda "School 21" raqamli texnologiyalar maktabi tomonidan “Kibernetika - zamonaviy sun’iy intellekt poydevori” mavzusida xalqaro ilmiy-amaliy anjuman o'tkaziladi. ☁️ Konferensiya O‘zbekiston Fanlar akademiyasining yirik ilmiy muassasalaridan biri hisoblangan Kibernetika instituti tashkil etilganining 60 yilligiga bag‘ishlab o'tkazi…
🟥 Yandex Uzbekistan’da amaliyot o‘tashni xohlaysizmi? Algoritmlar bo‘yicha mashg‘ulotlarning yangi formati besh hafta ichida sizning ko‘nikmalaringizni oshiradi va tanlovning har qanday bosqichlariga - birinchi qadamlardan yakuniy suhbatlargacha tayyorlaydi. Ishtirokchilarni qisqa videodarslar, musobaqalar va ajoyib sovrinlar kutmoqda, eng yaxshilar esa Toshkent ofisida IT-amaliyot uchun taklif olishlari mumkin! O‘…
❤🔥1
Yaxshi xabar: Coursera O‘zbekistonni ayollar Sun’iy Intellekt kurslariga o‘qishi bo‘yicha Global Leader sifatida e’tirof etdi! 8 mart arafasidagi bu tahliliy materialda O‘zbekistonda Prezidentimiz tomonlaridan ayollarni Sun’iy Intellekt bo‘yicha ta’limiga qaratilayotgan tizimli e’tibor natijasini boshqa davlatlarga ham namuna bo‘lishi kerakligiga urg‘u qaratilgan. Bayramga o’ziga xos sovg‘a bo‘libdi. Siz ham vaqti…
Showing the 12 most recent of 15 posts we hold for @uzbek_developer_blog. 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.
“Khusanboy Sobirjonov | IT Blog 📰” (@uzbek_developer_blog), 68 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/uzbek_developer_blog.
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.