Channel
@netbsd
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
230subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001169846413 |
|---|---|
| Type | Channel |
| Username | @netbsd |
| 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 | 7 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/netbsd |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 11:17 | 230 | -1 |
| 26 Sept 2026, 01:01 | 231 | +3 |
| 13 Sept 2026, 05:21 | 228 | +1 |
| 6 Sept 2026, 05:18 | 227 | +1 |
| 29 Aug 2026, 02:25 | 226 | +1 |
| 22 Aug 2026, 11:17 | 225 | +1 |
| 8 Aug 2026, 10:30 | 224 | no change |
| 7 Aug 2026, 09:18 | 224 | first reading |
19 posts held, back to 30 June 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 19 posts for this entry, the most recent from 5 February 2026. An engagement rate over an empty window would be a number about nothing.
119 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 47.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 57 | 47.9% | |
| 🔥 | 32 | 26.9% | |
| 🎉 | 20 | 16.8% | |
| 👎 | 5 | 4.20% | |
| 🤯 | 5 | 4.20% |
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 19 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 119 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 30 June 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.
Rust in the Kernel, and other odd decisions. NetBSD already has taken a much odder decision in the same space, by adding Lua into the kernel! This was also much discussed at the time. I have not used it, but apparently Lua is useful for rapid development and prototyping of kernel drivers. Note that in general, NetBSD is more conservative in its technical decisions than FreeBSD or Linux. Rust in the core of NetBSD i…
👍12🤯2👎1
smolBSD. smolBSD is a meta-operating system built on top of NetBSD. It lets you compose your own UNIX environment - from a single-purpose microservice system to a fully-custom OS image - in just a few minutes. The smolBSD environment uses the netbsd-MICROVM kernel as its foundation, leveraging the same portable, reliable codebase that powers NetBSD itself. You decide what to include - sshd, httpd, or your own servi…
🎉6🔥4
Adventures in porting a Wayland Compositor to NetBSD and OpenBSD. #video #wayland
👎4👍3🤯2
This blog is hosted on a Nintendo Wii. While browsing the NetBSD website recently, I noticed the fact that there was a ‘Wii’ option listed right there on the front page in the ‘Install Media’ section, nestled right next to the other first-class targets like the Raspberry Pi, and generic x86 machines. Unlike the other outdated and unmaintained examples above, clicking through to the NetBSD Wii port takes you to the …
👍9🤯1
Installing NetBSD on the Nintendo Wii!. It's about time for another Wii homebrew project! Because thanks to some recent developments, it's possible to get NetBSD working on this thing. Oh... and it's the latest version too! https://www.youtube.com/watch?v=KO9bNwE3Vps #system #install #nintendo
👍1
NetBSD on a ROCK64 Board. Long story short, I had the chance to resurrect 4 single-board computers that were collecting dust in my office. I decided to install FreeBSD on one of them and it was a success. This time I will show you how and why I installed NetBSD on a second ROCK64 board. https://simonevellei.com/blog/posts/netbsd-on-a-rock64-board/ #hardware #install #rock64
🔥7👍2
BSDCan 2024: - NetBSD on RISC-V - It Finally Runs NetBSD By: Dylan Eskew & Dr Phil Nelson; - NetBSD Subfiles By: Elijah Sherwood & Dr Philip Nelson; - Making NetBSD as a fast(er) booting microvm By: Emile Heitor; - Alamosa: A Tiered Disk Block Cache for NetBSD By: Kira Ash; All videos - Youtube, Peertube. #video #conf
👍9🔥1
Swap the operating system of any remote Linux server by the one of your choice. For a long time, I have been curious whether there were ways to swap out the operating systems of a remote server without having access to a BIOS/UEFI nor to a good cloud control panel with ISO/images loading capabilities, but only throughout a remote SSH access to an existing system... https://cloudbsd.xyz/ #cloud #system #install
👍2
Why I Like NetBSD, or Why Portability Matters So why use NetBSD? Many of its proponents would argue that NetBSD also has its own niche: the focus on portability. At the time I first heard about portability, I took it to roughly mean that you can run it on any machine. Now my understanding of the concept has evolved and I want to talk a bit about why portability is awesome, and why I think people undersell its import…
👍6🔥1
NetBSD 9.4 released! It represents a selected subset of fixes deemed important for security or stability reasons since the release of NetBSD 9.3 in August 2022, as well some enhancements backported from the development branch. It is fully compatible with NetBSD 9.0. Users running 9.3 or an earlier release are strongly recommended to upgrade... https://blog.netbsd.org/tnf/entry/netbsd_9_4_released #release #system
🎉7🔥1
NetBSD 10.0 available! The NetBSD project is pleased to announce the eighteenth major release of the NetBSD operating system NetBSD 10.0! See the release announcement for details... https://blog.netbsd.org/tnf/entry/netbsd_10_0_available #release #system
🔥7🎉4
Finding NetBSD Kernel Bugs through LockDoc. This post will be my attempt to package up my master’s thesis in a format that can be read comfortably. I’ve spent the last 15 months mostly on this topic, and if you’ve noticed that some of my past posts mostly revolved around NetBSD, this is why. I hope this also gives me the opportunity to shine a light on some implementation details, since the thesis itself had to be m…
Showing the 12 most recent of 19 posts we hold for @netbsd. 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.
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.
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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“NetBSD” (@netbsd), 230 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/netbsd.
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.