MCP без привязки запроса к одному серверу В спецификации MCP 2026-07-28 убрали обмен initialize/initialized и заголовок Mcp-Session-Id. Каждый запрос несёт собственные сведения о версии, клиенте и его возможностях. Балансировщик может направить его на любой экземпляр сервера. Состояние приложения при этом может сохраняться. В руководстве предлагают возвращать явный идентификатор и передавать его аргументом следующи…

Channel
Библиотека ИИ для айтишников
@neuro_text
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
6,451subscribers
-144 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 | -1002094560190 |
|---|---|
| Type | Channel |
| Username | @neuro_text |
| Description | Все самое полезное про ИИ: работающие промты, баттлы нейронок и свежие новости. Наши курсы: https://clc.to/pe9QmA По рекламе: @tproger_sales_bot Учиться у нас: https://proglib.io/w/5b542799 Для обратной связи: @proglibrary_feeedback_bot |
| Created | 10 March 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/neuro_text |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 03:35 | 6,451 | -12 |
| 30 Oct 2026, 08:16 | 6,463 | -8 |
| 27 Oct 2026, 07:11 | 6,471 | -7 |
| 24 Oct 2026, 08:39 | 6,478 | -4 |
| 21 Oct 2026, 08:09 | 6,482 | +1 |
| 18 Oct 2026, 15:55 | 6,481 | +5 |
| 15 Oct 2026, 22:49 | 6,476 | +5 |
| 12 Oct 2026, 18:17 | 6,471 | +6 |
| 5 Oct 2026, 21:17 | 6,465 | -28 |
| 28 Sept 2026, 03:19 | 6,493 | -15 |
| 18 Sept 2026, 08:37 | 6,508 | -11 |
| 13 Sept 2026, 22:38 | 6,519 | -3 |
| 10 Sept 2026, 12:01 | 6,522 | -11 |
| 5 Sept 2026, 03:38 | 6,533 | -10 |
| 1 Sept 2026, 04:04 | 6,543 | -2 |
| 28 Aug 2026, 17:04 | 6,545 | -11 |
| 25 Aug 2026, 12:12 | 6,556 | -11 |
| 22 Aug 2026, 22:43 | 6,567 | -7 |
| 19 Aug 2026, 08:58 | 6,574 | -1 |
| 16 Aug 2026, 19:05 | 6,575 | first reading |
Engagement
50 posts held, back to 22 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 7.41%
- avg views ÷ 6,451 subscribers
- Avg views / post
- 478
- 21 posts measured
- Reaction rate
- 0.247%
- reactions ÷ views · ER floor
- Posts in window
- 21
- of 50 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. It is computed over the 15 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 50 (22 July 2026 – 4 November 2026) |
| Views total | 10,035 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 10:30 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.
What this channel posts
- Photos
- ≈1,330
- Videos
- ≈486
- Links
- ≈1,610
Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 9m 36s
- Average length
- 1m 04s
Measured directly from 9 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.
Reaction mix
249 reactions across 41 posts, in 9 distinct kinds. The most used accounts for 26.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤩 | 66 | 26.5% | |
| ❤ | 50 | 20.1% | |
| 🥰 | 41 | 16.5% | |
| 👍 | 39 | 15.7% | |
| 🔥 | 19 | 7.63% | |
| 😁 | 18 | 7.23% | |
| 🥱 | 11 | 4.42% | |
| 👾 | 4 | 1.61% | |
| 👏 | 1 | 0.402% |
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 42 of the 50 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 249 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 50 most recent posts we hold, published 22 July 2026 to 4 November 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
Telegram’s own ‘edited’ marker: 0 of 21 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
OpenAI Batch API: скидка 50% с ожиданием до суток Для разметки корпуса или обработки данных ночью можно использовать OpenAI Batch API, если ответы не нужны сразу. Запросы передают файлом JSONL, по одному на строку. В документации указаны скидка 50% относительно синхронных API и окно завершения до 24 часов. Среди поддерживаемых путей есть /v1/responses, /v1/chat/completions и /v1/embeddings. Перед сборкой файла про…
Совместите поиск по смыслу с точным совпадением Для базы знаний полезны два способа поиска: dense-векторы находят близкий смысл, BM25 — точные слова при настроенном full-text индексе. В Qdrant Query API оба запроса можно выполнить через prefetch, а результаты объединить с RRF. Он учитывает места документов в выдачах, поэтому не нужно напрямую сравнивать две шкалы оценок. При пагинации offset действует только на осн…
🛠 Дайте модели текст страницы без меню и подвала Crawl4AI получает веб-страницы через браузер и возвращает Markdown. Для очистки есть Fit Markdown: можно убрать служебные блоки или отобрать текст по запросу через BM25. Если структура страниц повторяется, CSS- или XPath-схема позволяет извлечь JSON без вызова LLM. Для извлечения моделью предусмотрена отдельная стратегия. Перед передачей агенту проверьте полученный …
🎵 Почему AudioSR может не помочь вашему MP3 AudioSR достраивает высокочастотную часть звука. Но модель обучалась на аудио после low-pass-фильтра, а MP3 может терять частоты иначе — с «дырами» возле границы диапазона. В README авторы показывают неудачный результат и вариант с low-pass-обработкой перед AudioSR. На схеме — обе ветки эксперимента авторов. Своего сравнительного теста мы не проводили. Перед обработкой в…
Другая формулировка без потери старого чата В LibreChat можно создать отдельный чат от выбранного сообщения. Исходный разговор останется без изменений: удобно проверить другую постановку задачи и сохранить прежний ответ. При создании fork выберите, сколько истории перенести. Visible messages only копирует прямой видимый путь к сообщению без боковых веток. Есть варианты с боковыми ветками на этом пути или со всей ис…
Два разных вопроса к вашему RAG Нашли ли нужный контекст и опирается ли на него ответ? В Ragas это разные проверки. Context Precision учитывает порядок найденных фрагментов: релевантные должны стоять выше нерелевантных. Одной доли полезных фрагментов недостаточно. Faithfulness проверяет, подтверждаются ли утверждения ответа полученным контекстом. В примере документации подтверждено одно из двух утверждений, оценка…
🎨 Увеличить маленькую картинку и проверить детали Upscayl — настольный AI-апскейлер для Linux, macOS и Windows. В ролике авторов видны выбор модели и слайдер сравнения. Это старый интерфейс v2.11.0, а не показ последнего релиза. Инструмент подходит для изображений низкого разрешения. В FAQ отдельно сказано, что он не предназначен для исправления расфокуса. Нужен совместимый Vulkan GPU, большинство iGPU и CPU не под…
❤2
💡 GEPA: менять промпт по обратной связи В DSPy оптимизатор GEPA получает не только оценку ответа, но и текстовый feedback. Отдельная модель использует его, чтобы предложить новые инструкции. GEPA запускает программу с ними и оценивает кандидатов. Разделите данные по назначению: train — для изменения инструкций, validation — для выбора программы, test — для финальной проверки на примерах вне оптимизации. Без отдельн…
❤1
🔒 Чат с базой начинается с прав пользователя Vanna 2.0 даёт backend и готовый компонент vanna-chat: модель составляет SQL по вопросу, а интерфейс показывает результат в виде таблицы, графика и текстовой сводки. В ролике это показывает автор проекта. UserResolver определяет пользователя по данным вашей авторизации, например cookies или JWT. Инструменты могут проверять доступ по его группам. Авторизацию и права к ре…
❤1
Из пачки тикетов в сводку по категориям В README DocETL есть пример: map присваивает каждому обращению категорию и приоритет, а reduce собирает сводку обращений одной категории. Так коллекция документов проходит несколько этапов обработки. pipeline.show() обрабатывает пять документов и показывает результат, collect() запускает полную обработку. Стоимость вызовов доступна в total_cost. Сначала проверьте категории и…
❤1
🎞 Выделить объект маской на кадрах видео В демонстрации команды SAM 2 цветные области следуют за мячом и бутсами. Это маски сегментации: их можно использовать при разметке или дальнейшей обработке кадров. Модели можно указать объект кликом, рамкой или маской, затем распространить выделение по видео. Дополнительными подсказками можно исправлять ошибки маски. SAM 2 поддерживает работу с несколькими объектами. В теку…
❤1
Showing the 12 most recent of 50 posts we hold for @neuro_text. 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.
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.
Mentions
Named by 7 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.
@progbook · 138,22111 postsБиблиотека программиста
@proglibrary · 77,7115 postsБиблиотека программиста 🇷🇺
@lib_it3 · 994 postsТипичный программист
@tproger · 78,0133 postsПубликация вакансий в Proglib.io
@proglib_hh · 3222 postsAI Sapiens | Нейросети и ИИ
@aisapiens · 2,7231 postПрайс - Библиотека программиста (Proglib.io)
@proglib_advertising · 1011 post
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@pyproglib · 37,011
Telegram ranks this channel #20 of 84 here — alongside 83 others — read 1 September 2026
@hahacker_news · 25,271
Telegram ranks this channel #24 of 59 here — alongside 58 others — read 14 September 2026
@proglibrary · 77,711
Telegram ranks this channel #26 of 82 here — alongside 81 others — read 19 August 2026
@Cena_uspeha · 58,008
Telegram ranks this channel #31 of 50 here — alongside 49 others — read 23 August 2026
@goproglib · 23,930
Telegram ranks this channel #56 of 91 here — alongside 90 others — read 17 September 2026
@frontendproglib · 20,632
Telegram ranks this channel #84 of 93 here — alongside 92 others — read 25 September 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Библиотека ИИ для айтишников” (@neuro_text), 6,451 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/neuro_text.
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.