Telegram RegisterThe public register of Telegram
Telegram profile photo for Nek.12's Blog [EN]

Channel

Nek.12's Blog [EN]

@nek_12_personal_en

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

7subscribers

+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-1002856128690
TypeChannel
Username@nek_12_personal_en
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 12 October 2026
On Telegramt.me/nek_12_personal_en

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 2 October 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 why it has no browse page of its own yet.

Growth

676.56 August 2026 — 6 subscribers12 August 2026 — 6 subscribers15 September 2026 — 7 subscribers6 August 202615 September 2026
3 measurements spanning 40 days, net +1. 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 6–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:597+1
12 Aug 2026, 19:466no change
6 Aug 2026, 22:246first reading

Engagement

20 posts held, back to 7 January 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 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 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

11 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 54.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍654.5%
🔥327.3%
❤19.09%
🤔19.09%

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 10 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 11 reactions 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 7 January 2026 to 10 July 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

10 Jul 2026, 15:09 UTC24 views1 reactionsread 12 August 2026

How to choose between GPT-5.6 Sol, Terra, and Luna + reasoning? Explaining practically using real-world examples. I break down how to choose between GPT-5.6 models (Luna, Terra, Sol) and reasoning levels through a simple analogy with human attention: some tasks need more "memory for rules," others need more "time to think." Read more #ai #gpt56 #aiagents #reasoning #llm #prompting #agenticcoding

👍1

Signed Nek.12 - Automation

25 Jun 2026, 18:23 UTC33 views1 reactionsread 12 August 2026

Stop Babysitting Your Agents! Introducing Kent Workflows. Explaining Kent Workflows - a new paradigm for working with agents that lets you turn manual agent management into a fully automated process where agents work in loops. Read more #ai #personal #aiagents #workflows #kent #opensource #llm #automation #multiagent #agenticai

👍1

Signed Nek.12 - Automation

15 Jun 2026, 13:14 UTC26 viewsread 12 August 2026

Meet Kent 2.0 - Your Coding Accomplice Released Kent 2.0 - formerly Builder, now Kent with a new site at kent.sh. This release includes: system prompt customization, new subagents with config examples, performance and terminal fixes, system sleep prevention, and more. Read more #development #ai #kent #aiagent #llm #subagents #systemprompt #localmodels #release #clitools

Signed Nek.12 - Automation

11 Jun 2026, 18:40 UTC22 viewsread 12 August 2026

I gave your agent access to Firefox - meet Firefox CLI TL;DR: Firefox CLI is a CLI interface for controlling a real Firefox session with AI agents - a full equivalent of Agent Browser for Chrome, but better. Install once via an extension; supports Claude Code and Codex. Firefox CLI is my new project - a CLI interface that lets your agent control your real Firefox session. It's a full equivalent of Agent Browser wi…

Signed Nek.12 - Automation

25 May 2026, 13:02 UTC20 views1 reactionsread 12 August 2026

MCP is Deprecated MCP has fundamental architectural problems - it pollutes context, kills flexibility, and creates security risks. For agents with terminal access, CLI is a far better alternative, and it's time to stop using MCP. Read more #ai #development #mcp #cli #aiagents #llm #anthropic #contextengineering #harnessengineering #bash

🤔1

Signed Nek.12 - Automation

1 May 2026, 12:37 UTC26 viewsread 12 August 2026

Claude-pilled: why complex agent workflows are working against you Complex systems of agents, slash commands, and orchestrators aren't progress - they're micromanagement that gets in the way of frontier models doing their best work. Here's why the simple approach works better, and how I actually work. Read more #ai #development #llm #agents #claude #prompting #workflow #context #tokens #claudecode #aidevelopment #…

Signed Nek.12 - Automation

10 Apr 2026, 10:37 UTC30 viewsread 12 August 2026

Builder 0.10.1 update: • Fast async file search: type @query -> Tab to autocomplete. • Token counter improvements: counts context much more accurately, which makes it feel like you have ~+15% more context window. • Compact, rollback, and supervisor no longer invalidate caches, saves a lot of money. • You can pick a different model for supervisor right during onboarding • You can skip sign in, e.g. for usin…

Signed Nek.12 - Automation

9 Apr 2026, 11:11 UTC25 views1 reactionsread 12 August 2026

How Does My Agent Survive 37+ Compactions in a Row? A Deep Dive into Proactive Compact in Builder Explanation of Builder's advanced compaction algorithm and how it lets the agent run for dozens of sessions in a row without losing context or making unnecessary stops. Read more #ai #development #builder #compaction #claude #codex #agentai #llm #context #buildercli #opensource

🔥1

Signed Nek.12 - Automation

7 Apr 2026, 15:39 UTC20 views2 reactionsread 12 August 2026

I got tired of every existing coding agent. So I built my own - Builder. Introducing Builder - a free, open-source coding agent built for professional engineers. Outperforms Codex and is already available on GitHub. Read more #ai #development #agenticcoding #opensource #codingagent #builder #claudecode #codex #ai #devtools

👍2

Signed Nek.12 - Automation

27 Mar 2026, 11:08 UTC21 viewsread 12 August 2026

I switched to a tiling window manager on macOS. Full breakdown: Aerospace, Amethyst, and Yabai Switching to a tiling window manager became a necessity for me as the number of parallel agentic workflows kept growing. Here's a full breakdown of three options for macOS (Aerospace, Amethyst, Yabai) - pros, cons, and conclusions. Read more #personal #development #macos #tilingwm #yabai #aerospace #amethyst #windowmanag…

Signed Nek.12 - Automation

23 Feb 2026, 12:10 UTC19 views1 reactionsread 12 August 2026

Gemini finally fixed, Google and Anthropic shot themselves in the foot, and OpenAI is farming karma - weekly news. TL;DR: Google released Gemini 3.1 Pro with fixed tool calling, Anthropic and Google started aggressively banning subscription use outside their own tools, while OpenAI keeps actively supporting OpenClaw and is gearing up for GPT-5.3. Gemini finally fixed tool calling I just wrote in my last post about…

👍1

Signed Nek.12 - Automation

18 Feb 2026, 12:35 UTC16 viewsread 12 August 2026

I spent $150 and 5 days testing OpenClaw with all top models. My verdict on the future of AI assistants. Spent 5 days and $150+ testing OpenClaw with different AI models. GPT is a robot without personality, Gemini has great character but can't work properly, Opus is perfect but costs $100/day. OpenClaw is still full of bugs (4000 issues, 3000 PRs). Read more #ai #personal #openclaw #aiassistants #claudeopus #gpt #…

Signed Nek.12 - Automation

Showing the 12 most recent of 20 posts we hold for @nek_12_personal_en. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“Nek.12's Blog [EN]” (@nek_12_personal_en), 7 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/nek_12_personal_en.

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.