Telegram RegisterThe public register of Telegram
Telegram profile photo for Boris ProIT

Channel

Boris ProIT

@boris_proit

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

38subscribers

-2 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003441131512
TypeChannel
Username@boris_proit
Created11 November 2025 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live19 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/boris_proit

Topic

Education — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Growth

3840398 August 2026 — 40 subscribers10 August 2026 — 40 subscribers9 September 2026 — 39 subscribers19 November 2026 — 38 subscribers8 August 202619 November 2026
4 measurements spanning 103 days, net -2. 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 38–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Nov 2026, 08:4738-1
9 Sept 2026, 00:0039-1
10 Aug 2026, 19:1540no change
8 Aug 2026, 02:1840first reading

Engagement

16 posts held, back to 11 November 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 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 16 posts for this entry, the most recent from 22 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

41 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 97.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4097.6%
👍12.44%

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

Measured over the 16 most recent posts we hold, published 11 November 2025 to 22 December 2025, 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

22 Dec 2025, 17:54 UTC279 views3 reactionsread 10 August 2026

🎯 Easy Python Solution — How to Solve LeetCode 1431 (Kids With Candies) This problem looks trivial — and that’s exactly why many candidates fail it. Interviewers use tasks like this to check clarity of thinking, not syntax. In this short breakdown, you’ll see: ✅ The cleanest Python solution with zero overthinking ✅ How to identify the real condition behind the problem ✅ Why a single comparison is all you need ✅ A …

🔥3

4 Dec 2025, 16:50 UTC307 views2 reactionsread 10 August 2026

🎯 You MUST Know This: How the GCD Formula Actually Works — LeetCode 1071 (1 Minute) Most people can use GCD in this problem — but very few actually understand why the formula works. In this new 60-second breakdown, you’ll learn: ✅ The real intuition behind using GCD for strings ✅ Why the compatibility check str1 + str2 == str2 + str1 is the key ✅ How GCD(len1, len2) instantly gives the pattern length ✅ A 10-second…

🔥2

1 Dec 2025, 21:13 UTC230 views2 reactionsread 10 August 2026

🎯 Can You Solve This Coding Problem in ONE Line? — LeetCode 1071 Most people overthink GCD of Strings, but this task becomes insanely simple once you understand the core compatibility check behind it. In this new short, you’ll see: ✅ How to solve the entire problem in a single line ✅ Why this works mathematically (not by guessing) ✅ A fast check interviewers LOVE to see ✅ The cleanest version of the solution you c…

🔥2

28 Nov 2025, 14:38 UTC138 views5 reactionsread 10 August 2026

Time to repeat! 🎯 LeetCode 1768: Full Solution in 2 Minutes People think Merge Strings Alternately is too basic to study — but mastering these “easy” patterns is what actually builds interview speed. In this new short, you’ll see: ✅ A complete Python walkthrough in under 2 minutes ✅ The exact loop structure interviewers expect ✅ How to avoid the common merge mistakes ✅ A clean solution you can reuse in harder stri…

🔥5

25 Nov 2025, 19:51 UTC163 views3 reactionsread 10 August 2026

🎯 LeetCode 1071: STOP Doing This Most candidates attack GCD of Strings with random guesses or brute force. And that’s exactly why this “simple” problem quietly destroys interview performance. In this new short, you’ll learn: ✅ The #1 mistake almost everyone makes ✅ Why guessing patterns leads to failure ✅ The mindset shift that turns this task into pure logic ✅ A faster way to spot the real GCD idea instantly 💾 Sav…

🔥3

21 Nov 2025, 14:12 UTC163 views3 reactionsread 10 August 2026

🎯 LeetCode 1071: How I Solved It Without Memorizing Most people try to brute-force this task or memorize patterns. But the real power of GCD of Strings comes from understanding the hidden structure behind repeating substrings. In this new video, you’ll learn: ✅ The core intuition behind “string GCD” ✅ How to derive the solution from scratch (no memorization) ✅ A clean Python implementation with full explanation ✅ R…

🔥3

19 Nov 2025, 14:07 UTC115 views6 reactionsread 10 August 2026

🎯 LeetCode 1768: Interview Twists That Catch 90% of Candidates Most people think Merge Strings Alternately is “too easy to fail.” But in real interviews, this problem is used as a trap to expose weak thinking patterns. In this new short, you’ll see: ✅ 3 interview twists candidates never expect ✅ The hidden logic recruiters are checking ✅ Why “simple tasks” often filter out more people than hard ones 💾 Save it for l…

🔥6

17 Nov 2025, 17:26 UTC145 views6 reactionsread 10 August 2026

🎯 Failing LeetCode 1768? 3 Interview Mistakes You’re Making Most candidates think Merge Strings Alternately is “too easy to fail.” But in real interviews, this task filters out people who don’t understand how to think like developers. In this English short, you’ll learn: ✅ 3 silent mistakes that break your solution ✅ Save it for later YouTube (eng 🇬🇧) — [VIDEO LINK] And if you want the full deep-dive solution in…

🔥6

14 Nov 2025, 14:24 UTC182 views5 reactionsread 10 August 2026

This time I’m breaking down one of the most common mistakes candidates make when solving LeetCode 1768 — Merge Strings Alternately. A tiny detail that can cost you the interview. In this English short, you’ll learn: ✅ The mistake almost everyone makes ✅ Why it breaks your solution ✅ How to fix it in under 30 seconds YouTube (eng 🇬🇧) - [VIDEO LINK] And if you want the full deep-dive solution in Russian, here are al…

🔥4👍1

12 Nov 2025, 14:44 UTC722 views6 reactionsread 10 August 2026

🎯 Just dropped my first coding tutorial! LeetCode 1768: Merge Strings Alternately This isn't just a solution walkthrough—I'm teaching you HOW to think through problems. 32 min deep-dive covering: ✅ Fishing for keywords ✅ Core logic breakdown ✅ Debugging techniques [VIDEO LINK] #LeetCode #Python #CodingInterview

🔥6

11 Nov 2025, 19:55 UTC87 viewsread 10 August 2026

Main Links: Link Tree - Link LeetCode75 - Link Additional files and resources | Donation: Patreon (eng 🇬🇧) - Link Boosty (ru 🇷🇺) - Link Social Networks: YouTube (eng 🇬🇧) - Link YouTube (ru 🇷🇺) - Link Instagram (eng 🇬🇧) - Link TikTok (eng 🇬🇧) - Link VK (ru 🇷🇺) - Link RuTube (ru 🇷🇺) - Link

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

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

“Boris ProIT” (@boris_proit), 38 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/boris_proit.

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.