Telegram RegisterThe public register of Telegram
Telegram profile photo for آموزش ساخت ربات تلگرام در پایتون

Channel

آموزش ساخت ربات تلگرام در پایتون

@sourcefurushi

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

593subscribers

+98 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-1002430827581
TypeChannel
Username@sourcefurushi
CreatedBetween 1 September 2024 and 15 December 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live20 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/sourcefurushi

Topic

Technology — 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 59% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@sourcefurushi/73 · this entry4 Aug 2026, 17:25 UTC@pyfaw3schools/24244 Aug 2026, 17:47 UTC1.0022 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@pyfaw3schools6 (6/6 hand-verifiable sample passed)0.9837 minutesthis entry (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 12 January 2025 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @sourcefurushi — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

494593543.57 August 2026 — 495 subscribers8 August 2026 — 495 subscribers8 August 2026 — 494 subscribers15 August 2026 — 522 subscribers23 August 2026 — 528 subscribers30 August 2026 — 531 subscribers8 September 2026 — 537 subscribers18 September 2026 — 566 subscribers2 October 2026 — 582 subscribers12 October 2026 — 586 subscribers19 October 2026 — 587 subscribers27 October 2026 — 586 subscribers3 November 2026 — 591 subscribers12 November 2026 — 592 subscribers20 November 2026 — 593 subscribers7 August 202620 November 2026
15 measurements spanning 105 days, net +98. 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 479–608 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Nov 2026, 16:56593+1
12 Nov 2026, 09:08592+1
3 Nov 2026, 07:34591+5
27 Oct 2026, 14:17586-1
19 Oct 2026, 22:26587+1
12 Oct 2026, 11:19586+4
2 Oct 2026, 14:55582+16
18 Sept 2026, 05:17566+29
8 Sept 2026, 23:20537+6
30 Aug 2026, 22:28531+3
23 Aug 2026, 07:07528+6
15 Aug 2026, 18:22522+28
8 Aug 2026, 10:55494-1
8 Aug 2026, 04:19495no change
7 Aug 2026, 13:01495first reading

Engagement

20 posts held, back to 15 December 2024 — 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.

What this channel posts

Video runtime
48m 18s
Average length
3m 43s

Measured directly from 13 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.

Recent posts

4 Aug 2026, 17:25 UTC121 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با پایتون و گوگل کولب از مبتدی تا حرفه ای - قسمت دهم : آموزش متصل کردن دیتابیس سوال‌وجواب به چت‌بات تلگرام با پایتون و Pandas! 🤖📊 در این جلسه یاد می‌گیریم چطور با استفاده از کتابخانه Pandas یک دیتافریم از ۱۰,۰۰۰ سوال و جواب (فایل CSV / TSV) بسازیم و منطق پاسخ‌دهی هوشمند رو پیاده‌سازی کنیم. همچنین تابع get_answer رو طوری طراحی می‌کنیم که در صورت عدم پیدا شدن پاسخ، پیام پیش‌فرض پشتیبانی ارسال …

4 Aug 2026, 17:04 UTC774 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با پایتون و گوگل کولب از مبتدی تا حرفه ای - قسمت نهم : 📌 حل مشکل پیام‌های تکراری و ساخت پایپ‌لاین اجرای دائمی ربات تلگرام! 🔄🤖 در این جلسه مشکل خوانده شدنِ چندباره‌ی یک پیام تکراری رو با آپدیت داینامیک پارامتر offset حل کردیم. همچنین با به‌کارگیری یک پایپ‌لاین بی‌نهایت (while True) ربات رو آماده کردیم تا به‌صورت مداوم گوش‌به‌زنگِ پیام‌های جدید باشه و فقط آپدیت‌های پردازش‌نشده رو دریافت کنه! …

3 Aug 2026, 16:09 UTC906 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام از مبتدی تا پیشرفته - قسمت هشتم آموزش ارسال فایل و سند (Document) در تلگرام با پایتون و متد sendDocument! 📁🤖 در این جلسه یاد می‌گیریم چطور با استفاده از اندپوینت sendDocument فایل‌های مختلف (مثل فایل CSV یا اسناد موجود در محیط گوگل کولب) را به همراه کپشن دلخواه از طریق ربات تلگرام ارسال کنیم. ⏱️ بخش‌های مهم ویدیو: 00:15 - دسترسی به فایل‌های نمونه (Sample Data) و کپی مسیر فایل CSV 00:26 - تنظی…

3 Aug 2026, 16:06 UTCviews —

Channel name was changed to «آموزش ساخت ربات تلگرام در پایتون»

3 Aug 2026, 16:04 UTC853 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با پایتون و گوگل کولب از مبتدی تا حرفه ای قسمت هفتم - آموزش ارسال تصویر (Photo) در تلگرام با پایتون و متد sendPhoto! 🖼🤖 در این جلسه به نحوه ارسال عکس به گروه‌ها و چت‌های تلگرام با پایتون می‌پردازیم؛ از فراخوانی متد sendPhoto و تنظیم عکس با لینک مستقیم تا اضافه کردن کپشن و ارسال زمان‌بندی‌شده مجموعه‌ای از تصاویر! ⏱️ بخش‌های مهم ویدیو: 00:10 - فراخوانی متد sendPhoto و تنظیم پارامترهای اصلی در…

3 Aug 2026, 16:03 UTC876 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با پایتون و گوگل کولب از مبتدی تا حرفه ای قسمت ششم - آموزش ارسال فایل صوتی (Audio) در تلگرام با پایتون و متد sendAudio! 🎵🤖 در این جلسه یاد می‌گیریم چطور با استفاده از اندپوینت sendAudio و لینک مستقیم، فایل‌های صوتی را به همراه کپشن دلخواه از طریق ربات تلگرام ارسال کنیم. ⏱️ بخش‌های مهم ویدیو: 00:16 - فراخوانی و تنظیم اندپوینت sendAudio در کد پایتون 00:28 - معرفی پارامتر audio برای دریافت لینک…

2 Aug 2026, 14:54 UTC925 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با پایتون و گوگل کولب از مبتدی تا حرفه‌ای -قسمت پنجم - ارسال خودکار پیام به گروه در این ویدیو می‌پردازیم به نحوه ارسال پیام به گروه‌ها و چت‌های تلگرام با پایتون؛ از پیدا کردن chat_id یکتا تا ارسال اتوماتیک لیستی از پیام‌ها با فواصل زمانی مشخص در گوگل کولب! ⏱️ بخش‌های مهم ویدیو: 00:16 - مرتب‌سازی سلول‌های گوگل کولب و کامنت‌گذاری برای خوانایی بهتر کد 02:06 - معرفی اندپوینت sendMessage و بررسی …

1 Aug 2026, 13:42 UTC≈1,100 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با گوگل کولب از مبتدی تا حرفه ای - قسمت چهارم خواندن پیام های گروه با API توی این جلسه میریم سراغ پایتون و یاد می‌گیریم چطور بدون استفاده از مرورگر و فقط با چند خط کد پایتون، درخواست HTTP GET به API تلگرام بفرستیم و تمامی پیام‌های دریافتی ربات را استخراج و چاپ کنیم! ⏱️ بخش‌های مختلف ویدیو: 00:00 - مقدمه و معرفی کتابخانه requests برای ارسال درخواست‌های HTTP 00:19 - نحوه ایمپورت کردن پکیج reque…

31 Jul 2026, 15:32 UTC≈1,170 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با گوگل کولب از مبتدی تا حرفه ای - قسمت سوم: در قسمت قبل ربات تلگرام مونو در BotFather پیاده سازی کردیم، حالا تو این قسمت می خوایم توی این جلسه یاد بگیریم چطور رباتی که ساختیم رو به گروه تلگرام اضافه کنیم، محیط گوگل کولب (Google Colab) رو برای کدنویسی آماده کنیم و با استفاده از متد getUpdates پیام‌های فرستاده‌شده در گروه رو به صورت JSON دریافت و خوانایی‌شون رو بررسی کنیم! ⏱️ بخش‌های مختلف ویدی…

29 Jul 2026, 13:29 UTC≈1,410 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با گوگل کولب از مبتدی تا حرفه ای - قسمت دوم: توی این جلسه میریم سراغ اولین و مهم‌ترین قدم برای توسعه ربات‌های تلگرام؛ یعنی ثبت ربات در BotFather، دریافت API Token و پیکربندی تنظیمات امنیتی و حریم خصوصی! ⏱️ بخش‌های مختلف ویدیو: 00:00 - مقدمه و مرور مستندات رسمی تلگرام (قابلیت‌های ربات) 00:53 - جستجوی BotFather و آشنایی با دستورات (Commands) 01:27 - ساخت ربات جدید با دستور /newbot و انتخاب نام…

8 Jul 2026, 15:23 UTC≈3,760 viewsread 8 August 2026
Photo

آموزش API به زبان ساده فرض کن دو نفر زبان همدیگر را بلد نیستند. برای اینکه با هم صحبت کنند، یک مترجم بینشان قرار می‌گیرد. API دقیقاً نقش همان مترجم را بین دو برنامه دارد. در برنامه‌نویسی، برنامه‌ها معمولاً نمی‌توانند مستقیم با هم ارتباط برقرار کنند. یک برنامه به جای اینکه وارد جزئیات برنامهٔ دیگر شود، از API درخواست می‌کند. مثلاً: 📱 برنامهٔ هواشناسی تو می‌خواهد دمای امروز را بداند. به جای اینکه خودش برود اطلاعات…

5 Jul 2026, 11:54 UTC≈1,910 viewsread 8 August 2026
Video

آموزش ساخت ربات تلگرام با پایتون و گوگل کولب از مبتدی تا حرفه‌ای 🤖🐍 قسمت اول: نیازمندی‌های نرم‌افزاری برای ساخت ربات (requirements) ⚙️ زبان: انگلیسی با زیرنویس فارسی 🇬🇧

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

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 1 registered channel — 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.

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

“آموزش ساخت ربات تلگرام در پایتون” (@sourcefurushi), 593 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/sourcefurushi.

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.