Telegram RegisterThe public register of Telegram
Telegram profile photo for tech-afternoon

Channel

tech-afternoon

@techafternoon

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

1,647subscribers

+72 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002247739362
TypeChannel
Username@techafternoon
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/techafternoon

Growth

1,5751,6471,6116 August 2026 — 1,575 subscribers6 August 2026 — 1,575 subscribers6 August 2026 — 1,577 subscribers9 August 2026 — 1,588 subscribers15 August 2026 — 1,590 subscribers18 August 2026 — 1,595 subscribers21 August 2026 — 1,600 subscribers25 August 2026 — 1,617 subscribers28 August 2026 — 1,625 subscribers31 August 2026 — 1,641 subscribers4 September 2026 — 1,647 subscribers6 August 20264 September 2026
11 measurements spanning 29 days, net +72. 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 1,564–1,658 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 11:181,647+6
31 Aug 2026, 17:281,641+16
28 Aug 2026, 08:171,625+8
25 Aug 2026, 03:361,617+17
21 Aug 2026, 16:121,600+5
18 Aug 2026, 15:231,595+5
15 Aug 2026, 20:471,590+2
9 Aug 2026, 14:161,588+11
6 Aug 2026, 22:011,577+2
6 Aug 2026, 07:331,575no change
6 Aug 2026, 05:201,575first reading

Engagement

20 posts held, back to 7 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

384 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14838.5%
custom 59899191150856170176817.7%
🔥5113.3%
👍4612.0%
👏153.91%
😍153.91%
😁133.39%
102.60%
🤓61.56%
💯51.30%
👀30.781%
🤨20.521%
👌10.26%
🙏10.26%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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 20 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 384 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 7 June 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, 14:03 UTC355 views13 reactionsread 7 August 2026

Posted without readable text

11👏1custom 59899191150856170171

Signed Amin Mesbahi

2 Aug 2026, 15:09 UTC≈1,900 views27 reactionsread 7 August 2026

Posted without readable text

🔥174custom 59899191150856170173👏2👍1

Signed Amin Mesbahi

28 Jul 2026, 19:33 UTC≈2,520 views17 reactionsread 7 August 2026

🌟 انواع حملات پرامپت اینجکشن به زبان ساده و با مثال همون‌طور که شیوه توسعه نرم‌افزار و نحوه تعامل کاربر با نرم‌افزار، بعد از فراگیر شدن مدل‌های زبانی، تغییر کرده، نحوه تهاجم و حملات نرم‌افزاری هم تغییر کرده. یکی از موضوعاتی که باید بهش توجه مضاعفی کنیم، حملات Prompt Injection است که انواعش رو به زبان ساده و با مثال توضیح می‌دم. به زبون ساده، Prompt Injection یعنی مهاجم تلاش کنه با واردکردن دستوراتی در ورودی، رفتار

custom 598991911508561701710👍411🙏1

Signed Amin Mesbahi

26 Jul 2026, 12:36 UTC812 views11 reactionsread 7 August 2026

بعد از این نظرسنجی شاید بد نباشه تا با هم فکر کنیم ببینیم چه روش‌هایی می‌شه استفاده کرد تا AI به صورت درست و «پایدار» در اختیار طیف بیشتری از جامعه قرار بگیره. سه تا چالشی که به ذهن من می‌رسه: - تحریم، دشواری تهیه و البته مسدود شدن اکانت‌ها - نرخ برابری ریال و احتمالا قدرت خرید کمتر شرکت‌ها و افراد - تامین دسترسی سازمانی و تیمی راهکارهای پیشنهادی: - استفاده از LiteLLM یا bitfrost (به صورت کلی، یک AI Gateway که شما

custom 598991911508561701792

Signed Amin Mesbahi

24 Jul 2026, 17:01 UTC≈2,950 views22 reactionsread 7 August 2026

Posted without readable text

15👍5👏2

Signed Amin Mesbahi

24 Jul 2026, 09:41 UTC877 views27 reactionsread 7 August 2026

نیل دگراس تایسون، جایی می‌گه: 💡 یکی از چالش‌های بزرگ دنیا اینه که آدم‌ها درباره یک موضوع فقط اونقدری بدونن که فکر کنن حق با اون‌هاست، اما نه اونقدری که بفهمن دارن اشتباه می‌کنن. این عارضه، خیلی جاها هست، توی توسعه و معماری نرم‌افزار و AI هم هست و خیلی آزاردهنده است. اینجوری نباشیم 😅

16👏6🔥5

Signed Amin Mesbahi

19 Jul 2026, 16:11 UTC≈1,120 views5 reactionsread 7 August 2026
Poll

لطفا فقط در صورتیکه در ایران شاغل هستید این نظرسنجی رو شرکت کنید. تامین اشتراک و هزینه AI رو:

  1. خودم تهیه می‌کنم39%
  2. شرکت به صورت رویه عمومی برای همه تامین می‌کنه30%
  3. شرکت بنا به درخواست تهیه می‌کنه17%
  4. خودم باهوشم، نیازی به هوشواره ندارم 🥸15%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

👀3🤨2

Signed Amin Mesbahi

18 Jul 2026, 18:39 UTC≈2,410 views17 reactionsread 7 August 2026
Photo

معرفی Ontology Playground اصلاً Ontology یعنی چی؟ به بیان ساده، Ontology یک مدل صریح از «مفاهیم یک دامنه و رابطه بین آن‌ها» است. مثلاً توی دامنه منابع‌انسانی، ممکنه داشته باشیم: Employee Department Position Manager LeaveRequest و روابطی مثل: Employee worksIn Department Employee hasPosition Position Employee reportsTo Manager Employee submits LeaveRequest تفاوتش با ER Diagram یا دیتابیس‌مدل اینه که هدف Ontology فقط ت

11👍6

Signed Amin Mesbahi

14 Jul 2026, 08:55 UTC≈3,590 views20 reactionsread 7 August 2026
Photo

بدون شرح البته تشخیص صحیح top یا mid یا junior بودن خودش یکی از مراحل عرفانه 😅

😁135👏2

Signed Amin Mesbahi

12 Jul 2026, 19:12 UTC≈1,040 views12 reactionsread 7 August 2026
Poll

کوییز NoSQL: کدوم مورد بهترین توصیف برای "Embedding" در مقابل "Referencing" هست؟

  1. الف) Embedding همیشه بهتر از Referencing هست چون سریع‌تره8%
  2. ب) Referencing برای داده‌هایی که با نرخ بالا رشد می‌کنن (unbounded growth) مناسب‌تره36%
  3. ج) Embedding فقط برای relational databases کاربرد داره0%
  4. د) Referencing نیاز به هیچ index ای نداره8%
  5. ه) این دو مفهوم فقط در RDBMS معنا دارن4%
  6. و) نمی‌دانم، اطلاعی ندارم! توضیح بده.44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

9👍3

Signed Amin Mesbahi

10 Jul 2026, 21:26 UTC≈2,290 views30 reactionsread 7 August 2026

داستان یک Date بد! گاهی بزرگ‌ترین باگ‌ها، اون‌هایی نیستن که همون لحظه خطا بدن یا سیستم رو متوقف کنن. بلکه گاهی باگ، ۲۰ سال، ۳۰ سال، یا حتی بیشتر کنار ما زندگی می‌کنه. همه هم می‌دونن که بده. همه هم تجربه‌اش کردن. همه هم حداقل یک بار بهش فحش و فضیحت دادن. ولی چون میلیون‌ها خط کد بهش وابسته‌ است، کسی جرأت نمی‌کنه مستقیم دست ببره و درستش کنه. شروع ماجرا: ده روز فرصت و یک تصمیم عجولانه سال ۱۹۹۵، Brendan Eich در Netscape

12👍8custom 59899191150856170175💯3👏2

Signed Amin Mesbahi

6 Jul 2026, 20:49 UTC≈1,440 views11 reactionsread 7 August 2026
Poll

گاهی سرویس Identity اول پیام AccessRequested رو دریافت می‌کنه، اما هنوز پیام EmployeeCreated رو پردازش نکرده. و خطا می‌ده که کارمند رو پیدا نکرده. بهترین پاسخ از نظر شما کدومه؟

  1. احتمالا مشکل از بروکر است، چون ترتیب پیام‌ها را رعایت نشده.15%
  2. بهتره تا پیام‌ها رو synchronous کنیم تا دیگه این مشکل پیش نیاد.13%
  3. وابستگی پنهان بین eventهاست؛ consumer نباید فرض کنه eventهای وابسته همیشه به ترتیب مورد انتظار میان.65%
  4. - باید Outbox رو حذف کنیم، چون باعث تاخیر در publish شده.3%
  5. کافیه تا یک sleep چند ثانیه‌ای قبل از پردازش AccessRequested بگذاریم.4%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

🔥4😍3👍2🤓2

Signed Amin Mesbahi

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

Polls

The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

19 Jul 2026, 16:11 UTCFinal Results186 voters

لطفا فقط در صورتیکه در ایران شاغل هستید این نظرسنجی رو شرکت کنید. تامین اشتراک و هزینه AI رو:

  1. خودم تهیه می‌کنم39%
  2. شرکت به صورت رویه عمومی برای همه تامین می‌کنه30%
  3. شرکت بنا به درخواست تهیه می‌کنه17%
  4. خودم باهوشم، نیازی به هوشواره ندارم 🥸15%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

12 Jul 2026, 19:12 UTCFinal Results110 voters

کوییز NoSQL: کدوم مورد بهترین توصیف برای "Embedding" در مقابل "Referencing" هست؟

  1. الف) Embedding همیشه بهتر از Referencing هست چون سریع‌تره8%
  2. ب) Referencing برای داده‌هایی که با نرخ بالا رشد می‌کنن (unbounded growth) مناسب‌تره36%
  3. ج) Embedding فقط برای relational databases کاربرد داره0%
  4. د) Referencing نیاز به هیچ index ای نداره8%
  5. ه) این دو مفهوم فقط در RDBMS معنا دارن4%
  6. و) نمی‌دانم، اطلاعی ندارم! توضیح بده.44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

6 Jul 2026, 20:49 UTCFinal Results160 voters

گاهی سرویس Identity اول پیام AccessRequested رو دریافت می‌کنه، اما هنوز پیام EmployeeCreated رو پردازش نکرده. و خطا می‌ده که کارمند رو پیدا نکرده. بهترین پاسخ از نظر شما کدومه؟

  1. احتمالا مشکل از بروکر است، چون ترتیب پیام‌ها را رعایت نشده.15%
  2. بهتره تا پیام‌ها رو synchronous کنیم تا دیگه این مشکل پیش نیاد.13%
  3. وابستگی پنهان بین eventهاست؛ consumer نباید فرض کنه eventهای وابسته همیشه به ترتیب مورد انتظار میان.65%
  4. - باید Outbox رو حذف کنیم، چون باعث تاخیر در publish شده.3%
  5. کافیه تا یک sleep چند ثانیه‌ای قبل از پردازش AccessRequested بگذاریم.4%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

27 Jun 2026, 09:27 UTCFinal Results158 voters

کوییز: توی سیستم‌های توزیع‌شده، مخصوصا وقتی چند سرویس به واسطه پیام‌ها، eventها یا APIها با هم sync می‌شن، Reconciliation Job بیشتر برای چه کاری استفاده می‌شه؟

  1. جایگزین کردن Message Broker با یک batch job13%
  2. تضمین exactly-once delivery بین همه سرویس‌ها22%
  3. مقایسه دوره‌ای وضعیت چند سیستم و پیدا کردن یا اصلاح مغایرت‌ها57%
  4. حذف نیاز به Outbox/Inbox Pattern5%
  5. افزایش سرعت response time در APIهای synchronous3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 7 June 2026 to 5 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“tech-afternoon” (@techafternoon), 1,647 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/techafternoon.

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.