GeekNotif pinned a video

Channel
GeekNotif
@GeekNotif
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
271subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002220021675 |
|---|---|
| Type | Channel |
| Username | @GeekNotif |
| Description | گیکنوتیف |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GeekNotif |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 08:48 | 271 | no change |
| 7 Aug 2026, 15:41 | 271 | first reading |
Engagement
20 posts held, back to 26 October 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.
- ERR · 30 days
- 34.5%
- avg views ÷ 271 subscribers
- Avg views / post
- 93.4
- 9 posts measured
- Reaction rate
- 2.58%
- reactions ÷ views · ER floor
- Posts in window
- 10
- of 20 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 4 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (26 October 2025 – 6 August 2026) |
| Views total | 841 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 08: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.
What this channel posts
- Photos
- 39
- Videos
- 23
- Links
- 56
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
- 7m 50s
- Average length
- 3m 55s
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.
Reaction mix
23 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 47.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 47.8% | |
| 🔥 | 5 | 21.7% | |
| 🤓 | 5 | 21.7% | |
| 🆒 | 2 | 8.70% |
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 9 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 23reactions 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 26 October 2025 to 6 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
Video, posted without a caption
🔥3
اما خب ماکه اندروید یوزریم خوشحالو شاد و خندانیم آپدیت: تلگرام برگشت
🤓1
وسط بدبختی هامون الان تلگرام هم از اپ استور حذف شد
مثلا Workflow های مشخص تحلیل Forensic داشتن Memory سازمانی و بتونه از Context ذخیره شده استفاده کنه و Reasoning انتخابی توسط AI یعنی LLM فقط جایی استفاده میشه که واقعا ارزش اضافه کنه. نه برای هر مرحله از هر Investigation. نتیجه؟ سیستمی که میتونه همه Alert ها رو دائم بررسی کنه، ولی هزینه قابل کنترل داشته باشه. استفاده از Claude برای بررسی همه Alert ها شبیه استفاده از ماشین Formula 1 برای ارسال بسته است. ماشین فوق الع…
🆒2
یکم به این موضوع بپردازیم که AI داره با سرعت دیوانه کننده ای جلو میره؛ ولی هر AI برای هر کاری ساخته نشده مثلا نقش AI توی SOC چطوره و آینده اون چطور میشه این یکم طولانی میشه ولی جالبه . همونطور که میبینیم هوش مصنوعی با سرعت عجیبی داره پیشرفت میکنه و تقریبا هر مدیر امنیتی یه فشار مشترک رو حس میکنه: اینکه چطور خودش و تیمش رو با این سرعت هماهنگ کنه. چیزایی مثل Claude، Codex و Cursor همین الان دارن به تیم های امنیتی کمک …
باجافزار INC تبدیل شده به تهدید اصلی علیه SonicWall SMA؛ ۸۸۵ قربانی ... گروه INC Ransomware الان تبدیل شده به مهم ترین تهدیدی که داره از باگ های تازه کشف شده توی تجهیزات VPN سری SonicWall Secure Mobile Access (SMA) 1000 سوءاستفاده میکنه. طبق گزارشی که آخر هفته توسط Resecurity منتشر شد، این گروه از ابتدای آگوست ۲۰۲۶ فعالیتش رو شدیدا بیشتر کرده و چندین قربانی جدید رو توی سایت نشت اطلاعات خودش لیست کرده. طبق آمار Rans…
یه نفر یک ابزار متنباز ساخته به اسم AirLLM که باهاش میتونی یه مدل 2.8 تریلیون پارامتری رو با یه GPU فقط 4GB VRAMروی لپ تاپت اجرا کنی! از روشی به اسم Layer-wise Inference استفاده میکنه؛ یعنی بهجای اینکه کل مدل رو یکجا داخل VRAM بریزه، فقط همون لایهای که همون لحظه لازمه رو بارگذاری میکنه. نه Quantization نه Distillation نه Pruning نمونهها: مدل DeepSeek-V3 (671B) روی 12GB مدل Llama 3.1 405B روی 8GB مدل Kimi K3…
Video, posted without a caption
❤2
یکم درباره SharedRoot حرف بزنیم؛ باگ جدید Claude Cowork که Sandbox رو دور میزنه و به کل macOS دسترسی میده محققای امنیت سایبری یه اسیب پذیری جدید توی Claude Cowork شرکت Anthropic پیدا کردن که میتونه Sandbox رو دور بزنه و از داخل Linux VM به فایل های اصلی macOS دسترسی پیدا کنه. طبق گزارش Accomplish AI، قبل از اینکه این تغییرات اعمال بشه، حدود ۵۰۰ هزار کاربر macOS که از Local Execution استفاده میکردن در معرض این باگ …
ورژن جدید thefeed رلیز شده تا نت هست کاراشو بکنید. https://github.com/sartoopjj/thefeed/releases
🤓1
سیسکو یه باگ توی Unified Communications Manager (Unified CM) رو پچ کرده که به یه مهاجم داخل شبکه اجازه میده بدون احراز هویت روی سرور فایل رایت کنه و بعدش دسترسی خودش رو از طریق همون تا سطح root بالا ببره. این باگ با شناسه CVE-2026-20230 ثبت شده وPoC اون هم الان عمومی شده. تیم امنیتی سیسکو گفته فعلا موردی از سو استفاده واقعی ندیده، ولی وقتی PoC منتشر میشه معمولا فاصله بین «کشف باگ» و «حمله واقعی» خیلی کوتاه میشه. اصل …
❤3🤓1
Showing the 12 most recent of 20 posts we hold for @GeekNotif. 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.
Forward network
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.
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.
“GeekNotif” (@GeekNotif), 271 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/GeekNotif.
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.