Telegram RegisterThe public register of Telegram
Telegram profile photo for KernCore

Channel

KernCore

@KernCore

On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

926subscribers

+1 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-1001841232768
TypeChannel
Username@KernCore
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/KernCore

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 7 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

923926924.57 August 2026 — 925 subscribers8 August 2026 — 925 subscribers14 August 2026 — 923 subscribers22 August 2026 — 925 subscribers30 August 2026 — 926 subscribers7 August 202630 August 2026
5 measurements spanning 23 days, net +1. 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 923–926 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 10:04926+1
22 Aug 2026, 11:44925+2
14 Aug 2026, 21:23923-2
8 Aug 2026, 01:00925no change
7 Aug 2026, 16:32925first reading

Engagement

17 posts held, back to 9 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 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 17 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7168.9%
🔥2221.4%
🤔54.85%
👍32.91%
🥰21.94%

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

Measured over the 17 most recent posts we hold, published 9 July 2026 to 5 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

5 Aug 2026, 16:57 UTC53 views6 reactionsread 8 August 2026
Forwarded from @hiddenlockteamcPhoto

رغم سعادتي ان الموقع رجع اشتغل ثاني، وان المشكلة تم حلها. لكن بردوا Blogger ملهوش أمان، علشان كده هيكون في تجديد مختلف تماماً للموقع.

🔥3🥰21

5 Aug 2026, 12:55 UTC64 views1 reactionsread 8 August 2026
Forwarded from @sparrows0y0Photo

‼️ هل الأمن السيبراني له مستقبل حاليا ✅ ال AI مش مجرد اداة طلعت وخلاص او تقنية جديدة مبهرة , بل فعلا عصر تاني زي عصر الكهرباء وعصر الكومبيوتر , ومن اهم المجالات اللي حاليا عليها العين وهو الأمن السيبراني , طالما انه ال AI بقا بيعرف يحل كل الثغرات بل وكمان بيهاجم سعتها ايه لازمة الأمن السيبراني , كل ده هنعرفه اكثر هنا رابط الفيديو : 🎥 https://youtu.be/gQFD9BG1zKI

1

5 Aug 2026, 09:06 UTC50 views2 reactionsread 8 August 2026
Forwarded from @hiddenlockteamc

سلام عليكم جميعا، عاملين ايه ؟ الموقع بيواجه مشكلة تقنيه حاليا، هيتوقف لفتره ان شاء الله لحد ما المشكلة ما تتحل، وممكن يكون في تجديد للموقع بشكل كامل شكرا ليكم

2

28 Jul 2026, 12:20 UTC105 views1 reactionsread 8 August 2026
Forwarded from @sparrows0y0Photo

‼️ ليه الشركات بتسرب بياناتها !! ✅ أبل بتحارب المسربين علنا.. وفي نفس الوقت مستفيدة منهم , الفيديو ده بيشرح جانب مختلف تماما بقا عن الفكرة النمطية اللي دايما واخدينها , انه دايما التسريبات بتكون من هاكر او شخص خارج الشركة , ولكن في الفيديو هتعرف انه تقريبا اللي بيحصل اكثر حاجة هو دايما العكس 📎 رابط الفيديو : 🎥 https://youtu.be/e0vP6yCWGyU

1

26 Jul 2026, 19:06 UTC196 views11 reactionsread 8 August 2026
Photo

يتم شرح حالة TIME_WAIT في لينكس بشكل خاطئ منذ سنوات. فأثناء اطلاعي على الشيفرة المصدرية لـ TCP في نواة لينكس، صادفت مرة أخرى واحدة من أكثر الخرافات انتشارا في عالم الشبكات. في نواة لينكس، مدة حالة TIME_WAIT محددة فعليا بـ 60 ثانية داخل الشيفرة المصدرية: #define TCP_TIMEWAIT_LEN (60 * HZ) ولا يمكن تغيير هذه المدة لكل سوكيت Socket بشكل مستقل. والمثير للاهتمام أن الخيار tcp_fin_timeout، اللي تنصح الكثير من المقالات ب

8🤔2👍1

23 Jul 2026, 23:35 UTC178 views6 reactionsread 8 August 2026
Photo

🚨 ا Kimi K3 تعثر على ثغرة RCE في Redis خلال 27 دقيقة فقط تمكن سرب مكون من 32 AI Agents من اكتشاف ثغرة في Redis تتيح، بعد Authentication تنفيذ أوامر برمجية عشوائية على الخادم Remote Code Execution - RCE. وموقفتش هنا بس، فيه تقارير تشير إلى أنه بعد ساعات قليلة بس تمكن النظام من اكتشاف سلسلة هجوم تستهدف Telegram Desktop وiOS، وتعتمد على ملف فيديو تالف بيتم تحميله تلقائيا، دون أي تفاعل من المستخدم. وكان يفصلها عن الو

🔥6

23 Jul 2026, 13:58 UTC131 views2 reactionsread 8 August 2026
Forwarded from @sparrows0y0Photo

‼️ لينكس طلع اسوء مما تتخيل ! ✅ كل الناس بقت بتتكلم عن لينكس , وقد ايه هو اعظم نظام في المجرة , وان ويندوز اسوء نظام في المجرة ,ولكن هيحصل ايه لو عملنا نفس المقارنة ده بالظبط على لينكس , نفس المعاير اللي بنعملها لويندوز نعملها للينكس , ونشوف هل لينكس فعلا نظام يستاهل ولا !! رابط الفيديو : 🎥 https://youtu.be/NSNPrDIbTsw

2

21 Jul 2026, 12:59 UTC297 views13 reactionsread 8 August 2026
Photo

يبدو أن لينوس تورفالدس بدأ يغير نظرته للai 👀

🔥8🤔32

18 Jul 2026, 10:07 UTC367 views5 reactionsread 8 August 2026

معظم مستخدمي لينكس بيعرفو صلاحيات rwx، بس فيه صلاحيات خاصة لا تقل أهمية عنها. 🔐 SUID 👥 SGID 📌 Sticky Bit الصلاحيات دي بتتحكم في كيفية تشغيل البرامج وإدارة الملفات والمجلدات، وفهمها ضروري لكل من يريد التعمق في لينكس. اقرأ الشرح الكامل هنا: https://linuxhandbook.com/suid-sgid-sticky-bit/ #HiddenLock #Linux #SysAdmin

5

17 Jul 2026, 15:48 UTC908 views7 reactionsread 8 August 2026
Photo

الحل الجذري لتعطل إضاءة الكيبورد وأزرار الـ Fn على Linux https://www.hiddenlockteam.com/2026/07/linux-acer-1.html

7

17 Jul 2026, 13:34 UTC240 views8 reactionsread 8 August 2026

عاملين أيه، كل جمعو وانتم طيبين سؤال كنا بنسأله كثير، ونسأله ثاني، هل في أي Issue في استخدامه للينكس. 🤔

8

15 Jul 2026, 13:59 UTC162 views5 reactionsread 8 August 2026
Forwarded from @sparrows0y0Photo

‼️ مايكروسوفت بتحب لينكس ✅ مايكروسوفت مش زي ما احنا فاكرين عنها (بيل جيتس دافعلي) رابط الفيديو : https://youtu.be/WlFh0W4IaCE

5

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

Republished by

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

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

“KernCore” (@KernCore), 926 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/KernCore.

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.