Channel
@nossdpool
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
1,186subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001666710360 |
|---|---|
| Type | Channel |
| Username | @nossdpool |
| Created | Between 1 December 2021 and 27 July 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/nossdpool |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 01:23 | 1,186 | -5 |
| 11 Aug 2026, 10:58 | 1,191 | -3 |
| 8 Aug 2026, 06:20 | 1,194 | -1 |
| 7 Aug 2026, 11:01 | 1,195 | no change |
| 7 Aug 2026, 10:56 | 1,195 | first reading |
20 posts held, back to 27 July 2022 — 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 5 May 2026. An engagement rate over an empty window would be a number about nothing.
384 reactions across 19 posts, in 22 distinct kinds. The most used accounts for 41.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 159 | 41.4% | |
| 🔥 | 71 | 18.5% | |
| ❤ | 61 | 15.9% | |
| 😢 | 19 | 4.95% | |
| 😱 | 12 | 3.13% | |
| 🏆 | 7 | 1.82% | |
| 👏 | 7 | 1.82% | |
| 👎 | 5 | 1.30% | |
| ☃ | 4 | 1.04% | |
| 👀 | 4 | 1.04% | |
| 👌 | 4 | 1.04% | |
| 💩 | 4 | 1.04% | |
| 💯 | 4 | 1.04% | |
| 😭 | 4 | 1.04% | |
| 🥰 | 4 | 1.04% | |
| 🍾 | 3 | 0.781% | |
| 🐳 | 3 | 0.781% | |
| 🗿 | 3 | 0.781% | |
| 😁 | 2 | 0.521% | |
| 🤯 | 2 | 0.521% | |
| 2 further kinds | 2 | 0.521% |
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 19 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 384reactions 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 27 July 2022 to 5 May 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.
Total Chia netspace has declined greatly over the past few weeks, which is good for each individual miner and leads to higher profits. Unfortunately, with a smaller total netspace, more GPU computational power is required to serve the same amount of HDD space. It is not unique to our pool, and other compressed plot technologies are affected by this too. This, combined with the currently increased Signage Point rate, …
❤10👍4👌2
In the current situation, we have decided not to develop a new pool version for the Proof of Space 2.0. We will continue to provide the best services for all our devoted miners as long as current plots work on the Chia blockchain, regardless of the XCH price.
👍13😢13💩4😭4🐳3❤2👌2🔥1
Timelord currently generates signage points at a significantly decreased rate, which is reflected in the hourly share statistics on our pool. This decreases the number of generated blocks and affects the farming reward. UPDATED: it was fixed
😱5👍3😢2🤯1
Many people are still unaware of the recent events in the Chia blockchain and keep asking us questions. Therefore, we decided to provide some information here. A few days ago, someone posted a malformed transaction to the Chia mempool. That transaction dramatically slowed down the block generation algorithm, effectively preventing reference nodes from mining blocks. This knocked most solo miners and NFT pools off t…
👍32❤12👏1🤡1
Version 3.1 A few minor bugs were fixed. If you experience slow plotting or CPU plotting issues on Linux, please update to a new version.
👍20❤5💯4👏3
Version 3.0 is released - new compression levels from 47.5GiB down to 26.2GiB - up to 388% reward - 1 minute plot time on Linux in full-in-ram mode More info on the website
🔥19👍6🍾3👏2
A reminder Users of the old client versions 1.1, 1.2, and 1.3 must upgrade to a newer CPU (1.4) or GPU client version to successfully pass the plot filter change taking effect tomorrow
👍15❤3🔥2
Photo, posted without a caption
🔥20👍11☃4❤4😁1
Version 2.3 is released - better loging, verbose mode - globs (*) in directory names - more accurate benchmark, plot filter emulation mode - better plot insertion/removal handling, parallel plots enumeration A full list of changes can be found in this message https://t.me/nossdpoolchat/4077
👍19❤9🔥3😱2🤩1
Network generates signage points much quicker than it should. This overloads our GPU client. We are aware of this. We aren't sure what is the cause. May be CNI is recklessly testing its new ASIC timelord shooting its own leg. This should hopefully settle down in an hour or two when difficulty adjusts.
🏆7😱5❤3👎2👏1
We've updated our docker hub repository with a new GPU version Do not forget to install NVIDIA Container Toolkit to use it
🥰4👍3❤1🔥1
A critical bugfix update, version 2.2 - fixed a bug that led to a significant decrease in share rate on most machines - removed mandatory dependency from CUDA in linux version Strongly encourage everyone to update!
❤4👀4👍3🤯1
Showing the 12 most recent of 20 posts we hold for @nossdpool. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
What is your favorite minimum payment threshold?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 27 July 2022 to 5 May 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 736,962 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 registered channels — 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“NoSSD Chia Pool” (@nossdpool), 1,186 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/nossdpool.
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.