Channel
@govno17
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
621subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001381694574 |
|---|---|
| Type | Channel |
| Username | @govno17 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/govno17 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 06:43 | 621 | +1 |
| 8 Aug 2026, 03:02 | 620 | no change |
| 7 Aug 2026, 11:56 | 620 | first reading |
20 posts held, back to 15 April 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 11 June 2026. An engagement rate over an empty window would be a number about nothing.
255 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 136 | 53.3% | |
| 👍 | 54 | 21.2% | |
| 😱 | 45 | 17.6% | |
| 🔥 | 12 | 4.71% | |
| 🐳 | 8 | 3.14% |
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 17 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 255reactions 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 15 April 2025 to 11 June 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.
Я болезненно отношусь когда терминология плохо отражает действительность. HTTP Response состоит из нескольких частей: status line, 0 или несколько Header и body В stdlib голанга есть ResponseWriter. Чтобы отправить статус код клиенту надо вызвать r.WriteHeader(statuscode), а чтобы манипулировать набором хэдеров надо взять r.Header() и у него дергать Add/Set/Del. (write header кроме отправки статус кода заодно отправ…
🐳6😱2
Все знают что в голанге форматирование дат использует магические числа вместо "слабопонятных" %D %m %M. Допустим что сегодня 10 ноябра 2009 года. Что выведет этот код? now.Format("002 - 02 - 2") Ответ: 314 - 10 - 10
Угадайте что выведет этот код? type Foo interface{} func main() { var a *string var b Foo = a fmt.Printf("a: %v, %v, b: %v, %v", a, a == nil, b, b == nil) }
$ bazel test tests/tests_test
😁15👍5😱1
Если вы развиваете какую-то библиотеку, вполне реальна ситуация, когда ваши пользователи будут использовать не последнюю версию и захотят оставаться на ней какое-то время. Поэтому, всегда стоит оставлять документацию доступной по крайней мере для каждой мажорной версии. Смотрю я на доку polyfactory, у которой в конце осени вышла версия 3.х и не понимаю как мне прочитать доку для v2.2
🔥12🐳2
где-то в недрах библиотеки if TYPE_CHECKING: from .base_control import BaseControl # noqa ControlEvent = Event["BaseControl"] что может пойти не так, да? любые попытки дернуть get_type_hints на функции с таким параметром приведут к ошибкам, даже если сам параметр нам не интересен https://github.com/flet-dev/flet/blob/main/sdk/python/packages/flet/src/flet/controls/control_event.py#L121
👍2
import storages.utils ... # Monkey-patch django-storages to fetch settings from STORAGE_CONFIG storages.utils.setting = _setting https://github.com/netbox-community/netbox/blob/main/netbox/netbox/settings.py#L21
как это могло произойти? там вся дока такая https://cobra.dev/docs/tutorials/12-factor-app/
😱3
Угадайте, работает ли следующий код на голанге func a(x ...string) { } func b(x ...string) { a("prefix", x...) } func main() { b("arg1", "arg2") } Для сравнения, аналог на питоне def a(*x): pass def b(*x): a("prefix", *x) def main(): b("arg1", "arg2") Ответ: ./prog.go:9:9: too many arguments in call to a have (string, []string...) want (...string)
😁15
Не про код, а про результат его работы. Перед вами вырезанные два куска со скриншота "очень быстрого" редактора zed левые две стрелки - когда окно не на весь экран, правые - когда развернуто. Заметьте что вся панель осталась такого же размера, всё совпадает. Но стрелки блин на полпикселя смещены Как это могло произойти?
😁2
def smembers(self, name: KeyT) -> Union[Awaitable[Set], Set]: я понимаю, что поддерживать одновременно sync и async версии одного и того же всем лень, но делать вот так - это совершенно не уважать пользователей вашей библиотеки. https://github.com/redis/redis-py/blob/793af91087ee2bd949ba2fa9e0743284cab5cf72/redis/commands/core.py#L3591C9-L3591C13
😁18👍5😱2
всем любителям .env посвящается $ cat dumpenv.py import os print(os.getenv("XXX")) $ cat .env XXX = 1 export XXX=2 $ uv run --env-file=.env ./dumpenv.py 1 $ dotenv run python ./dumpenv.py 2 ещё больше вкусного в комментариях
😁20
Showing the 12 most recent of 20 posts we hold for @govno17. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Говнокод от @Tishka17 & @vlade11115” (@govno17), 621 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/govno17.
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.