Telegram RegisterThe public register of Telegram
Telegram profile photo for ɪɴ ᴍʏ ʜᴇᴀᴅ

Channel

ɪɴ ᴍʏ ʜᴇᴀᴅ

@MyHeadLog

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

690subscribers

+264 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-1001517802203
TypeChannel
Username@MyHeadLog
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live1 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/MyHeadLog

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 55% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

4266905587 August 2026 — 426 subscribers7 August 2026 — 426 subscribers15 August 2026 — 434 subscribers22 August 2026 — 456 subscribers29 August 2026 — 459 subscribers7 September 2026 — 463 subscribers15 September 2026 — 513 subscribers1 October 2026 — 690 subscribers7 August 20261 October 2026
8 measurements spanning 55 days, net +264. 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 386–730 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 02:16690+177
15 Sept 2026, 19:20513+50
7 Sept 2026, 02:42463+4
29 Aug 2026, 19:42459+3
22 Aug 2026, 16:16456+22
15 Aug 2026, 10:08434+8
7 Aug 2026, 13:16426no change
7 Aug 2026, 01:32426first reading

Engagement

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

Reaction mix

160 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 47.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7647.5%
🔥6037.5%
❤‍🔥116.88%
👍74.38%
💯42.50%
🎉21.25%

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 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 160 reactions 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 22 May 2026 to 4 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

4 Aug 2026, 10:05 UTC275 viewsread 7 August 2026

یکیش ی وبسایت بزرگ داره دیگه ببینم چه میکنید کاری کردید تو کامنتا منم در جریان بزارید شل آماده و حاضره فقط برید بزنید😂

Signed 127.0.0.1:443

4 Aug 2026, 10:03 UTC292 views6 reactionsread 7 August 2026
Video

حوصله نداشتم آدرسا رو فیلتر کنم و بپوشونم بزنید نوش جونتون😂

❤6

Signed 127.0.0.1:443

4 Aug 2026, 09:11 UTC300 views5 reactionsread 7 August 2026
Voice message

Voice message, posted without a caption

👍3🔥2

Signed 127.0.0.1:443

26 Jul 2026, 20:29 UTC470 views12 reactionsread 7 August 2026

سورس کد باتشو گم کردم باید ی کوچولو صبرکنید تا دوباره بنویسمش ایندفعه میخوام با زبان QuantoScript بات رو توسعه بدم :()

🔥6❤4💯2

Signed 127.0.0.1:443

25 Jul 2026, 02:40 UTC514 views4 reactionsread 7 August 2026

نهایتا تا فردا پسفردا رباتو دوباره راه میندازم و شروع میکنیم به گذاشتن ویدیو ها ، دیگه خیلی وقته فعالیت درست و حسابی نداشتیم باید شروعش کنیم باز🤝

❤4

Signed 127.0.0.1:443

24 Jul 2026, 17:06 UTC548 views0 reactionsread 7 August 2026

خودمم هستم ، هرکی اوکی بود بره پیوی فرزین

Signed 127.0.0.1:443

24 Jul 2026, 17:06 UTC479 viewsread 7 August 2026
Forwarded from @iRLords

از تبریز یا مسیر تبریز تا تهران کدوماتون پایه مسابقه هستین؟ حضوری قراره دور هم جمع شیم و باهم یه پروژه رو تکمیل کنیم(هنوز پروژه معلوم نیست) ممکنه تا 1.5 سال طول بکشه و ما هر ماه حداقل یک بار شاید دور هم باید جمع بشیم. در آخر پروژه که تکمیل شد تبدیل به شرکت میشه و کسایی که کمک میکنن سهیمن توش... هر کدومتون خواست مخصوصا از تبریز-زنجان-تهران و دور اطراف اینا بهم پیام بده. @Farzin_Acc رزومه بفرستین لطفا یا حداقل بنو…

Signed 127.0.0.1:443

19 Jul 2026, 19:12 UTC680 views20 reactionsread 7 August 2026

به پیشنهاد یکی از رفیقام چند وقتیه که دارم روی ionCube کار میکنم ی ابزاریه که برای محافظت از کدهای PHP استفاده میشه ، خیلیا فکر میکنن صرفاً میاد سورس کد رو encrypt میکنه ، ولی داستان ی مقدار پیچیده تر از این حرفاست نمیاد مثل ی فایل متنی کل کد PHP رو برداره ، encrypt کنه و موقع اجرا دوباره decrypt کنه... چون اگه اینطوری بود خیلی راحت میشد موقع decrypt شدن ، کد اصلی رو از memory استخراج کرد برای اینکه بهتر بفهمیم داستا…

❤11❤‍🔥3🔥3🎉2💯1

Signed 127.0.0.1:443

16 Jul 2026, 19:41 UTC921 views14 reactionsread 7 August 2026
Video

خودتون نتایجو ببینید من حرفی ندارم😂 عملیاتی که پایتون در عرض 35 ثانیه انجام داده رو QuantoScript در عرض 4 ثانیه انجام داده! البته این مربوط میشه به بخش native C این زبان نمیدونم میدونید یا نه ولی خب این ی زبان هیبریدیه که سه تا بکند داره : interpreter, vm, native c اینجا با native c بنچمارکشو گرفتم :() کداشم با اپدیت بعدی میزارم روی گیتهاب که بتونید خودتون ران کنید و نتیجشو ببینید... توی این چند روزی که QuantoScript …

🔥11❤3

Signed 127.0.0.1:443

12 Jul 2026, 00:32 UTC873 views13 reactionsread 7 August 2026

منکه دیگه با پایتون کد نمیزنم ، سوییچ میکنم رو همین جدی ، چیزی هم دیدم کم اومده براش مینویسم اینطوری بهتره😂 ی پلاگین هم برای vscode فردا منتشر میکنم واسش که راحت بتونید باهاش کد بزنید کدارو مثل تکست خام نشونتون نده

❤13

Signed 127.0.0.1:443

12 Jul 2026, 00:25 UTC≈1,030 views21 reactionsread 7 August 2026

و بالاخره ، بعد از این همه مدت ، QuantoScript ریلیز شد 🚀 ی زبان برنامه نویسی کوچیک ، ساده و قابل فهم که از صفر ساخته شد و حالا نسخه 1.0.0 اش منتشر شده. ازتون دعوت میکنم برید داکیومنتش رو بخونید ، باهاش کد بزنید و امتحانش کنید . اگر جایی به باگ یا مشکلی برخوردید فقط گزارش کنید تا توی نسخه های بعدی بررسی و رفع بشه :() ی سری محدودیت ها و مواردی که هنوز کامل نشده هم وجود داره که همشون داخل داکیومنت نوشته شده و ازشون خبر …

❤19👍1🔥1

Signed 127.0.0.1:443

6 Jul 2026, 10:09 UTC934 views8 reactionsread 7 August 2026

یکی از رفقا اینو توسعش داده حمایت کنید🥰❤️

❤8

Signed 127.0.0.1:443

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

Mentions

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.

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

“ɪɴ ᴍʏ ʜᴇᴀᴅ” (@MyHeadLog), 690 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/MyHeadLog.

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.