Telegram RegisterThe public register of Telegram

Channel

neuro-job | нейроджоб — вакансии и работа в ИИ / Al

@jobs_chatGPT_midjourney

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Cite this entry

4,348subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001807483008
TypeChannel
Username@jobs_chatGPT_midjourney
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/jobs_chatGPT_midjourney

Topic

Job listings — 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 100% 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.

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

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@jobs_chatGPT_midjourney/751 · this entry30 Jul 2026, 06:44 UTC@jobs_it_digital/196530 Jul 2026, 06:45 UTC0.9372 seconds
@jobs_it_digital/195722 Jul 2026, 06:03 UTC@jobs_chatGPT_midjourney/743 · this entry22 Jul 2026, 06:05 UTC0.9272 seconds
@jobs_chatGPT_midjourney/747 · this entry26 Jul 2026, 06:06 UTC@jobs_it_digital/196126 Jul 2026, 06:07 UTC0.9272 seconds
@jobs_chatGPT_midjourney/754 · this entry2 Aug 2026, 06:01 UTC@jobs_it_digital/19682 Aug 2026, 06:04 UTC0.913 minutes
@jobs_chatGPT_midjourney/749 · this entry28 Jul 2026, 06:18 UTC@jobs_it_digital/196328 Jul 2026, 06:18 UTC0.88under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@jobs_it_digital5 (5/5 hand-verifiable sample passed)0.9172 secondsthis entry (32)

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 2 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 20 comparable posts for this entry, running 19 July 2026 to 7 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).

Across the whole group of 2, the earliest publisher we hold is @jobs_it_digital. 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.

Also posting the same content

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.

Growth

4,3484,3514,349.57 August 2026 — 4,351 subscribers7 August 2026 — 4,351 subscribers8 August 2026 — 4,349 subscribers11 August 2026 — 4,348 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -3. 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 4,348–4,351 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:174,348-1
8 Aug 2026, 04:174,349-2
7 Aug 2026, 13:034,351no change
7 Aug 2026, 12:494,351first reading

Engagement

21 posts held, back to 19 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.36%
avg views ÷ 4,348 subscribers
Avg views / post
59.3
21 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
21
of 21 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held21 (19 July 20268 August 2026)
Views total1,246
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:19 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

8 Aug 2026, 06:01 UTC12 viewsread 8 August 2026

Руководитель группы Кратко: Ищем руководителя в команду, которая создает AI-агента поддержки — продукт, способный изменить подход к клиентскому сервису Посмотреть подробнее - https://clck.ru/3TkFnZ #Руководитель_группы ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

7 Aug 2026, 06:53 UTC21 viewsread 8 August 2026

Security awareness Кратко: Ищем энергичного и опытного специалиста, который поможет нам поддерживать культуру, делая информацию о кибербезопасности понятной и доступной для каждого сотрудника. Посмотреть подробнее - https://clck.ru/3TkFdt #Security_awareness ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

6 Aug 2026, 06:47 UTC32 viewsread 8 August 2026

Тимлид команды разработки Кратко: Ищем опытных тимлидов в разные проекты. Вам предстоит развивать команду и управлять процессами разработки новых продуктов. Посмотреть подробнее - https://clck.ru/3SpVDi #Тимлид_команды_разработки ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

5 Aug 2026, 06:31 UTC38 viewsread 8 August 2026

Младший менеджер по маркетингу Кратко: Ищем специалиста с опытом в маркетинге, который поможет развивать разные каналы привлечения кандидатов. Посмотреть подробнее - https://clck.ru/3SvQkd #Младший_менеджер ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

4 Aug 2026, 06:07 UTC40 viewsread 8 August 2026

Системный аналитик Кратко: Собирать, анализировать и формализовать требования для разработки новой функциональности в наших 2 продуктах Посмотреть подробнее - https://clck.ru/3TAGX5 #Системный_аналитик ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

3 Aug 2026, 06:07 UTC51 viewsread 8 August 2026

Руководитель Кратко: Активное участие в проектировании архитектуры, вовлечённость в технические решения команды: код-ревью, техдолг, архитектурные комитеты Посмотреть подробнее - https://clck.ru/3TcCWd #Руководитель ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

2 Aug 2026, 06:01 UTC53 viewsread 8 August 2026

Senior Python Кратко: Разрабатывать сервисы внутренней автоматизации, писать новые и развивать существующие сервисы на Python Посмотреть подробнее - https://clck.ru/3TcCPi #Senior_Python ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

1 Aug 2026, 06:47 UTC59 viewsread 8 August 2026

Python-разработчикr Кратко: Ищем опытного специалиста, который будет влиять на архитектуру и стандарты агентных решений в компании Посмотреть подробнее - https://clck.ru/3TkFdG #Python_разработчик ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

31 Jul 2026, 06:47 UTC59 viewsread 8 August 2026

Инженер виртуализации Кратко: Ваша работа будет заключаться в том, чтобы обеспечивать надежную и эффективную работу платформы, которая решает задачи управления виртуальной и облачной ИТ-инфраструктурой. Посмотреть подробнее - https://clck.ru/3TAGYW #Инженер_виртуализации ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

30 Jul 2026, 06:44 UTC56 viewsread 8 August 2026

Аналитик данных Кратко: Анализировать причины отклонений ключевых метрик и поиск точек роста, разрабатывать модель роста для магазинов и прогнозировать рост розничного товарооборота Посмотреть подробнее - https://clck.ru/3TPpta #Аналитик_данных ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

29 Jul 2026, 06:26 UTC66 viewsread 8 August 2026

Инженер безопасности данных Кратко: Ищем специалиста, который будет развивать подходы и стандарты безопасности данных Посмотреть подробнее - https://clck.ru/3SpVPa #Инженер ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

28 Jul 2026, 06:18 UTC69 viewsread 8 August 2026

Главный инженер Кратко: Организация и проведение функционального и автоматизированного тестирования Посмотреть подробнее - https://clck.ru/3UnDY7 #Главный_инженер ➖➖➖➖➖➖➖➖➖➖ @jobs_chatGPT_midjourney

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

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

“neuro-job | нейроджоб — вакансии и работа в ИИ / Al” (@jobs_chatGPT_midjourney), 4,348 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/jobs_chatGPT_midjourney.

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.