Gleam v1.18.0 🚀 Вышел новый релиз Gleam. На этот раз праздник у language server'а: куча новых возможностей LSP плюс оптимизации компилятора 🐡 Полноценная поддержка полей рекордов в LSP! Теперь go-to-definition, find references и rename работают для полей везде: в объявлениях, labeled аргументах, паттернах, record update и доступе к полям 🐡 Rename теперь работает и для type variables в функциях, типах и константах 🐡…

Channel
Gleam
@gleam_ru
On this record: Growth · Engagement · Posts · Citations · Cite this entry
5subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002056699823 |
|---|---|
| Type | Channel |
| Username | @gleam_ru |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 14 September 2026 |
| On Telegram | t.me/gleam_ru |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 12:59 | 5 | +1 |
| 13 Aug 2026, 05:00 | 4 | no change |
| 6 Aug 2026, 23:02 | 4 | first reading |
Engagement
20 posts held, back to 20 May 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 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Gleam v1.15.0 🚀 Вышел новый релиз Gleam с обновлённой безопасностью Hex и улучшениями LSP 🐡 Hex перешёл на OAuth2. Добавили MFA на операции записи, используются короткоживущие токены, и теперь не нужно лишний раз вбивать пароль. Старые токены отзываются автоматически 🐡 Конкатенация строк <> теперь работает в guard clauses 🐡 Типы в internal больше не утекают в автокомплит, но подсказываются в ошибках об exhaustivene…
Channel photo updated
https://giacomocavalieri.me/writing/testing-can-be-fun-actually
https://www.youtube.com/watch?v=vyEWc0-kbkw
https://www.youtube.com/watch?v=WC_j91qogyY
https://www.youtube.com/watch?v=Ux9mT-XULwM
https://guycoding.medium.com/have-you-tried-gleam-a-fresh-take-on-functional-programming-a8390234f156?sk=251b83a97132b109a1b1b02d10040dda
https://gleam.run/news/formalising-external-apis/
https://www.youtube.com/watch?v=ynXZSvJXXJo
https://gleam.run/case-studies/strand/
Gleam v1.12.0 🚀 Вышел новый релиз Gleam упрощающий управление версиями зависимостей и множеством мелких улучшений 🐡 Понятные ошибки зависимостей! Теперь компилятор показывает точную цепочку конфликтов версий, показывает что есть новые мажорные версии при gleam update и объясняет почему версии несовместимы (новая версия pubgrub алгоритма) 🐡 Добавлены кастомные сообщения для echo: echo 11 as "lucky number" 🐡 Уменьшен…
Showing the 12 most recent of 20 posts we hold for @gleam_ru. 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Gleam” (@gleam_ru), 5 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/gleam_ru.
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.