Telegram RegisterThe public register of Telegram

Channel

fc fs筆記

@fcnotes

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

283subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001432557689
TypeChannel
Username@fcnotes
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/fcnotes

Growth

2837 Aug 2026, 21:07 — 283 subscribers8 Aug 2026, 08:31 — 283 subscribers7 Aug 2026, 21:078 Aug 2026, 08:31
2 measurements taken within a single day. 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 282–284 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 08:31283no change
7 Aug 2026, 21:07283first reading

Engagement

20 posts held, back to 11 October 2022the 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 14 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
17
Links
286

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

20 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1050.0%
🥰420.0%
😱315.0%
🤔315.0%

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 5 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 20reactions 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 11 October 2022 to 14 March 2025, 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

14 Mar 2025, 02:17 UTC≈1,150 views3 reactionsread 8 August 2026

Linux and ext4 however does not (or at least, didn’t used to). It used to both clear the error state and mark the page clean, but valid. In all respects it looked like a page freshly read from disk. But, that data was not on disk (the write failed!), any attempt to flush it would do nothing (it’s not dirty). But, because it’s a clean page, it’s eligible for eviction, resulting in the weird situation that you could re

😱3

Signed farseerfc 😂

14 Mar 2025, 02:16 UTC≈1,220 views3 reactionsread 8 August 2026

https://despairlabs.com/blog/posts/2025-03-13-fsync-after-open-is-an-elaborate-no-op/ fsync 具體行為有多模糊

🤔3

Signed farseerfc 😂

11 Mar 2025, 05:45 UTC877 views5 reactionsread 8 August 2026
Forwarded from @r_linux

Understanding Unix filesystem timestamps https://unixdigest.com/articles/understanding-unix-filesystem-timestamps.html https://redd.it/1j8jhvt @r_linux

👍5

Signed farseerfc 😂

5 Mar 2025, 05:21 UTC937 viewsread 8 August 2026

Intel RST 在 linux 上用 mdadm 的文檔

Signed farseerfc 😂

5 Mar 2025, 05:21 UTC885 views5 reactionsread 8 August 2026

rst-linux-paper.pdf https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/rst-linux-paper.pdf

👍5

Signed farseerfc 😂

22 Feb 2025, 08:31 UTC≈1,030 views4 reactionsread 8 August 2026

https://www.evanjones.ca/durability-nvme.html 關於 NVMe 設備上寫入的語義的一些解讀,引用到了 NVMe 標準,對不想細讀標準是一個不錯的總結

🥰4

Signed farseerfc 😂

9 Jan 2024, 03:16 UTC≈1,640 viewsread 8 August 2026

https://lore.kernel.org/linux-btrfs/20231217165359.604246-1-hch@lst.de/ host-aware SMR hdd 從 SCSI / ATA 標準中刪掉了(NVMe 標準中沒有加過),今後就只會有 host-managed 和 device-managed SMR 了。 Linux 內核會把現存少量的 host-aware SMR 設備當作 device-managed SMR (OS 看來是普通的 HDD )用

Signed farseerfc 😂

6 Jan 2024, 09:00 UTC≈1,530 viewsread 8 August 2026

https://www.vidarholen.net/contents/blog/?p=479 tl;dr: dd works for reading and writing disks, but it has no "low level I/O" capabilities that make it more suited for this than any other shell utility. Like cat you should use it where it makes sense, e.g. to take advantage of its wide array of options, rather than try to ensure that all disk related commands begin and end with dd out of fear and superstition.

27 Dec 2023, 15:59 UTC≈1,220 viewsread 8 August 2026

https://despairlabs.com/blog/posts/2023-12-25-openzfs-data-corruption-bug/

8 Aug 2023, 15:28 UTC≈1,090 viewsread 8 August 2026

https://youtu.be/NtkKHhXf3V4 linux nvme and block layer

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Names

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

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

“fc fs筆記” (@fcnotes), 283 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/fcnotes.

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.