Channel

FSD Blog

@fsd_blog

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

391subscribers

-4 since we began measuring on 2 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1001708295579
Type	Channel
Username	@fsd_blog
Created	3 October 2023 — measured — dated from the channel’s first post
First recorded	2 September 2026
Last confirmed live	4 October 2026
Measurements held	4
Confirmed unchanged	1 time, most recently 4 October 2026
On Telegram	t.me/fsd_blog

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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

4 measurements spanning 33 days, net -4. 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 390–396 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
4 Oct 2026, 16:56	391	-2
2 Sept 2026, 16:56	393	-2
2 Sept 2026, 03:15	395	no change
2 Sept 2026, 03:00	395	first reading

Engagement

17 posts held, back to 3 October 2023 — 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 17 posts for this entry, the most recent from 5 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

240 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 67.1% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
🔥	161	67.1%
❤‍🔥	38	15.8%
❤	21	8.75%
👍	14	5.83%
✍	2	0.833%
👏	2	0.833%
👎	1	0.417%
🤣	1	0.417%

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 15 of the 17 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 240 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 3 October 2023 to 5 February 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

5 Feb 2026, 17:28 UTC385 views19 reactionsread 2 September 2026

Photo

New home for the docs! Our documentation website has finally moved to a new domain after the unfortunate loss of the previous one. It's short and sweet: https://fsd.how Also this blog is overdue for some news — the core team has now grown to 5 people! This is already showing fruits as there are new articles written and translations made, the website is being modernized, and last but not least, we're having conver…

🔥12👍6🤣1

Signed Lev

23 Nov 2024, 00:02 UTC≈1,830 views21 reactionsread 2 September 2026

Photo

Стрим об FSD 2.1 с Евгением Паромовым This post announces a discussion livestream about FSD 2.1 in Russian Мы сколлабились с Евгением Паромовым — автором русскоязычных курсов по FSD и другим фронтендовым темам и ведущим YouTube-канала про фронтенд, архитектуру и жизнь разработчиков в целом. Женя недавно выступал с докладом "3 главных недостатка Feature-Sliced Design", и мы просто не могли пройти мимо, не пообщавшис…

❤‍🔥16🔥5

Signed Lev Chelyadinov

13 Nov 2024, 20:39 UTC≈1,450 views20 reactionsread 2 September 2026

Photo

Feature-Sliced Design 2.1 Wow, it's been over a year since 2.0! With this release, Feature-Sliced Design is officially embracing a new mental model called pages-first that proved to be more practical and easy to understand, and also was endorsed by active community members for a while. Another noteworthy change is the standardization of the public API for cross-imports, also known as @x. Behind the scenes we've bee…

🔥18❤2

Signed Lev Chelyadinov

11 Nov 2024, 22:34 UTC≈1,330 views14 reactionsread 2 September 2026

Steiger just got a big update It's been a while since we released an update to our linter, Steiger, but trust us, it was worth the wait. This release comes with a new ESLint-9-like configuration format that allows you fine-grained control over which rules should run in which parts of the project. You can also change rule severities to be warnings instead of errors, and best of all, you can now write custom rules and…

🔥14

Signed Lev Chelyadinov

11 Nov 2024, 22:34 UTC795 views7 reactionsread 2 September 2026

Photo

Photo, posted without a caption

🔥7

Signed Lev Chelyadinov

6 Oct 2024, 00:30 UTC829 views7 reactionsread 2 September 2026

We're featured on Vasili's Office Hours! Lev from the FSD core team (yours truly) was invited to an episode of the Office Hours podcast by @vasili_sviridov. In this episode, they talk about the challenges of migrating to FSD in a company, especially an English-speaking one, exchange a few practical tips, and dive deeper into the understanding of FSD. This is the first video that marks the ongoing efforts of the cor…

🔥7

Signed Lev Chelyadinov

7 Jul 2024, 17:00 UTC≈1,400 views10 reactionsread 2 September 2026

Photo

RFC on the future configuration format of Steiger Our linter, Steiger, is maturing as the feature requests come in from community members (thanks, by the way!). In preparation for a stable release, we need to settle on a format for the configuration file. We’ve written up goals for the format, as well as the first proposal — an ESLint-style flat config format. Now we need your comments and ideas! Feel free to sugge…

🔥8❤2

Signed Lev Chelyadinov

9 Jun 2024, 11:36 UTC921 viewsread 2 September 2026

Photo

Photo, posted without a caption

Signed Lev Chelyadinov

9 Jun 2024, 11:36 UTC≈1,600 views25 reactionsread 2 September 2026

We proudly present to you, Steiger! It’s here! The architectural linter that we teased in that talk is finally ready. Grab it from npm and try it for yourself: $ npx steiger ./src It’s probably going to scream at you. From the 6 projects from FSD examples that we tried it on, every single one had issues, some of them genuine, some of them less so. To make it less strict, you can make a steiger.config.ts and expor…

🔥23✍2

Signed Lev Chelyadinov

31 May 2024, 21:53 UTC935 views12 reactionsread 2 September 2026

We gave our talk today, but in case you’ve missed it, we have a recording. The talk is in Russian though, so for non-Russian speakers, here’s the news — the linter is almost ready to be released for beta testing, with all the critical rules already written. Hopefully, next week we will share the actual release that you can try on your projects. We will post about it here, so stay tuned. Сегодня мы презентовали линте…

🔥10👍2

Signed Lev Chelyadinov

28 May 2024, 17:18 UTC761 views6 reactionsread 2 September 2026

While we’re on the train of contributor love, another recent noteworthy contribution is by Yan Levin (midas-png on GitHub), a comparison of Feature-Sliced Design with a well-known design methodology, Atomic Design. We appreciate it a lot as well :) https://feature-sliced.design/docs/about/alternatives#atomic-design This page is another hot zone for contributions, we’re looking for comparisons with DDD, Clean Archit…

❤5🔥1

Signed Lev Chelyadinov

28 May 2024, 17:09 UTC981 views11 reactionsread 2 September 2026

Photo

Using Feature-Sliced Design with TanStack Query A community member, Ruslan @rodrijiez, has written a new article for the docs with practical advice for using TanStack Query with FSD. Go read it, give it some love, post feedback in the chat, or even suggest further improvements through PRs. Big thanks to Ruslan from the core-team. https://feature-sliced.design/docs/guides/tech/with-react-query We love to see contri…

❤8👏2👎1

Signed Lev Chelyadinov

Showing the 12 most recent of 17 posts we hold for @fsd_blog. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

Евгений Паромов
@cleanfrontend · 3,6791 post

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.

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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“FSD Blog” (@fsd_blog), 391 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/fsd_blog.

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.