Channel
@front_interview
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
1,906subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001718187031 |
|---|---|
| Type | Channel |
| Username | @front_interview |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/front_interview |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @dh_jun/134630 Sept 2024, 15:13 UTC | @front_interview/494 · this entry30 Sept 2024, 15:13 UTC | 1.00 | under a minute |
| @front_interview/497 · this entry3 Oct 2024, 16:47 UTC | @dh_jun/13493 Oct 2024, 16:59 UTC | 1.00 | 13 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @dh_jun | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @dh_jun (4–1) |
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 1 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 16 comparable posts for this entry, running 14 December 2023 to 9 October 2024. 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.
Across the whole group of 2, the earliest publisher we hold is @dh_jun. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 11:35 | 1,906 | -3 |
| 7 Aug 2026, 05:31 | 1,909 | no change |
| 7 Aug 2026, 05:20 | 1,909 | first reading |
20 posts held, back to 14 December 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 10 October 2024. An engagement rate over an empty window would be a number about nothing.
33 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 81.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 27 | 81.8% | |
| ❤ | 2 | 6.06% | |
| 🎉 | 2 | 6.06% | |
| 🔥 | 2 | 6.06% |
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 15 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 33reactions 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 14 December 2023 to 10 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Ребят, как относитесь к использованию ИИ в кодинге?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👍1
Алоха ребят! Вот иногда сидишь и думаешь - красивые кнопочки как сделать? Зайдите и просто посмотрите на эту красоту, как переключается и т.п. Вам понравится)) Реализовано на HTML + CSS + JS. CSS здесь на препроцессоре SCSS, кто его не знает - не пугайтесь, он простой.) КодеПен - https://codepen.io/myacode/pen/PoqQQNM
👍2❤1
Всем привет привет! Ребят, понедельник) А все что то начинают с понедельника) У нас, как вы уже знаете - недавно полностью в бесплатном доступе открылся первый модуль. Даже не надо ничего платить. Просто пробуй и смотри. Так что залетай - будет полезно, введение в алгоритмы - мало кто рассказывает на таких пальцах, как у нас) (Ссылка)
И снова привет! Чуть не забыл рассказать за крутую новость. Ребят, видел пальцы вверх на тему, что бы открыть один модуль для общего доступа. Согласен, покупать курс (пусть и не дорогой) и не пощупать его? Ну ты чего, дядь.) Поэтому - первый модуль полностью доступен. Залетайте по ссылке, юзайте, ни к чему не обязывает.) Отдельно прошу рассказать, если пройдете модуль - как вам по сложности. (Ссылка)
👍2
😍Это как минимум красиво) Ребят, всем привет! Рекомендую покопаться в коде крутой верстки переключателя. Реализован на HTML + CSS + JS. CSS здесь на препроцессоре SCSS, кто его не знает - не пугайтесь, он простой.) КодеПен переключателя - https://codepen.io/jkantner/pen/vYPRvgr
🔥2
Ребят, дальше основные посты будут на нашем основном канале, а здесь - реже. Так что залетайте - https://t.me/dh_jun/1347 )
Йоу йоу, ребят! Решили навести суету, теперь будем каждый день стараться выдавать вам пользу.) По понедельникам мы теперь будем рассказывать вам о наших планах в плане обучалок.) И вот вам что подкину. Вы наверное видели, что у нас есть курсы. На этой неделе, скорее всего, мы сделаем 1-й модуль полностью бесплатным.) Как тебе такое? Полноценное введение на пару недель самостоятельного обучения - полностью бесплатн…
👍5
Front Interview | Подготовка к собеседованию pinned «Всем доброе утро четверга! Немного поднапряглись и полностью залили весь курс на платформу STEPIK. Так что теперь все совсем хорошо. Для тех, кто не в теме: ранее мы проводили курсы по Frontend-разработке. Писали его наши лучшие Senior-разработчики в течении…»
Всем привет! Небольшой апдейт курса. Добавили дополнительных три задания.
👍2
Всем привет! Пятница такая пятница. А я хочу сказать - вау - мы подобрались к первой маленькой победе - 5 учеников на курсе.) Ребята, вам отдельный респект.)
👍2
Всем доброе утро четверга! Немного поднапряглись и полностью залили весь курс на платформу STEPIK. Так что теперь все совсем хорошо. Для тех, кто не в теме: ранее мы проводили курсы по Frontend-разработке. Писали его наши лучшие Senior-разработчики в течении, примерно, полугода. По итогу мы получили большое количество практического материала, лекций и конспектов (из конспектов вообще книгу можно собрать). Практиче…
👍2
Слушайте, ну раз такая тема пошла - курс полностью выложим только к концу недели, но уже появился первый ученик, то давайте если кто то хочет получить доп скидку, так сказать, до официального старта курса (в понедельник), то вот вам мое предложение. Пишите сюда https://t.me/hanlaoyt , что хотите начать учиться у нас фронтенду - я предоставлю скидку. Вместо 5.000 рублей за весь курс - для вас будет 3.500 рублей (а та…
👍2
Showing the 12 most recent of 20 posts we hold for @front_interview. 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.
The 2 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.
Ребят, как относитесь к использованию ИИ в кодинге?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Угадай цену будущего курса?
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 14 December 2023 to 10 October 2024. 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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Front Interview | Подготовка к собеседованию” (@front_interview), 1,906 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/front_interview.
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.