Channel
@khraks_dev
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
99subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002109574336 |
|---|---|
| Type | Channel |
| Username | @khraks_dev |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/khraks_dev |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 11:01 | 99 | no change |
| 6 Aug 2026, 23:02 | 99 | first reading |
20 posts held, back to 23 March 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 pageof 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 8 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
116 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 34.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 40 | 34.5% | |
| 🔥 | 28 | 24.1% | |
| ✍ | 14 | 12.1% | |
| ❤ | 8 | 6.90% | |
| 🤯 | 6 | 5.17% | |
| 🤔 | 5 | 4.31% | |
| 🤓 | 3 | 2.59% | |
| 🤩 | 3 | 2.59% | |
| 🥱 | 3 | 2.59% | |
| ❤🔥 | 2 | 1.72% | |
| 👏 | 2 | 1.72% | |
| 👎 | 1 | 0.862% | |
| 💩 | 1 | 0.862% |
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 20 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 116reactions 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 23 March 2025 to 8 March 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.
Combiner & Reducer В v4 добавили новые модули которые являются адаптированными Semigroup & Monoid из fp-ts. Semigroup (Полугруппа) — это некий тип A и операция combine которая каким-то образом делает из двух экземпляров типа один. Как отражено в названии - комбинирует) interface Combiner<A> { combine: (self: A, that: A) => A } Самое интересное: подразумевается, что эта штука удовлетворяет неким законам. // ассо…
👍7
Апдейт по модулю Filter github В итоге Filter прадставляет собой вот такую функцию: export interface Filter { (input: Input): Result<Pass, Fail> } По-сути это filterMap: остается то что в succeed() плюс можно сразу мапнуть результат Array.filter( [1,2,3], x => isOdd(x) ? succeed(x.toString()) : fail(x) ) // ["1", "3"] Но дополнительный трюк в том, что были добавлены перегрузки которые одновременно при…
❤1👍1
Дождались — бета 4 версии https://effect.website/blog/releases/effect/40-beta/ https://www.youtube.com/watch?v=P04R7lUR4Cc
🔥6👏2👎1
#DI как в Effect Pt3 Теперь озадачился написанием аналога Effect.gen, чтобы можно было просто делать yield* вычислений и получать более читаемый код, вот искомый результат: const program = gen(function* () { const randomService = yield* RandomTag; const randomNumber = random.random(); const logger = yield* LoggerTag; logger.log(randomNumber); return randomNumber; }); Для реализации понадобится 2 вещи: …
🔥4
#DI как в Effect Pt2 Получаем вот что: const program: Computation<void, { logger: Logger, random: Random }> = andThan(getRandom)(logNumber) const runnable = provideServices(program)({ logger: ConsoleLogger, random: MathRandom }) run(runnable) // OK Можно заметить что мы заранее декларировали сервисы функкий в типах. Можно сделать более интересно — как yield* MyServiceTag в Effect. Чтобы мы его просто читали и он …
👍4
#DI как в Effect Pt1 Мааам можно мне: "Effect-like-DI" Нет! У нас "Effect-like-DI" есть дома Дома: Reader После прочтения заметки вы будете понимать шутку. Часто вижу, что хвалят DI в Effect. Хочу поделиться дедовским рецептиком наколенной версии. Во первых каждое вычисление должно трекать необходимую зависимость на уровне типов — в Effect это третий типопараметр R. interface Computation<out Value, in Services ex…
👍3
## Effect 4.0 Вмерджили моe предложение об улучшении DX при работе с Redacted. Теперь можно задать label при конструировании и при сериализации будет выведен он. const redacted = Redacted.make('password') const redactedWithLabel = Redacted.make('password', { label: 'MY_PASS' }) console.log(redacted) // <redacted> console.log(redactedWithLabel) // <MY_PASS> Пропихнуть в Config не получилось, а хотелось бы чтобы la…
🔥4
## Effect 4.0 Добавили модуль Filter — похож на Predicate. Но Predicate больше про нативную обертку предикатов и тайпгардов. interface Filter<in Input, out Output = Input> { (input: Input): Output | absent } const absent: unique symbol = Symbol.for("effect/Filter/absent") Более удобный, как по мне, потомучто является по факту filterMap — вместо Option.none() теперь Filter.absent и не нужен Option.some declare fu…
👍2❤1
Expandable hover Хорошая фича, интересно как оно будет отбражать интерфейсы и юнионы? https://x.com/drosenwasser/status/1939775110858383418?t=1rW9WKEh3GdniAtQ7_EGKQ&s=19
❤2
Posted without readable text
🤔4❤2
## Заинтересовался вот этой оптимизацией в Schema: If you want more perf you can use ParseResult.flatMap instead of Effect.gen and get eager optimization skipping the Effect runtime. Michael Arnaldi Суть в том что трансформеры Schema.transformOrFail должны возвращать Effect<unknown, ParseResult.ParseIssue, unknown>. Но например Either — это его подтип, который не требует вовлечения рантайма. Идея оптимизации тако…
🔥3
ExecutionPlan — появился в свежем релизе Effect@3.16 Интересно было посмотреть что за штучка. Кристализовался модуль в процессе разработки @effect/ai Суть в том, что можно описать в плоском виде (просто массив) порядок сервисов, которые будет использовать эффект при неудаче. То есть семантика буквально: - попробовать сначала с этим сервисом: - если успех, то идем дальше - если нет - то другой сервис - и тд…
👍3🥱3
Showing the 12 most recent of 20 posts we hold for @khraks_dev. 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.
Citation-graph rank — 1,049,179 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
@khraks_dev named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Khraks dev” (@khraks_dev), 99 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/khraks_dev.
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.