The bot's been updated and is now enabled again.
❤2😍2🙏1

Channel
@spotdll_updates
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
2subscribers
-3,359 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003797755375 |
|---|---|
| Type | Channel |
| Username | @spotdll_updates |
| Created | Between 1 February 2026 and 15 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 2 times, most recently 9 October 2026 |
| On Telegram | t.me/spotdll_updates |
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 |
|---|---|---|
| 29 Sept 2026, 12:55 | 2 | -4,196 |
| 15 Sept 2026, 23:01 | 4,198 | -43 |
| 12 Sept 2026, 08:40 | 4,241 | -122 |
| 8 Sept 2026, 00:36 | 4,363 | +133 |
| 3 Sept 2026, 08:14 | 4,230 | +90 |
| 31 Aug 2026, 00:53 | 4,140 | +83 |
| 27 Aug 2026, 20:07 | 4,057 | +131 |
| 24 Aug 2026, 13:27 | 3,926 | +107 |
| 20 Aug 2026, 19:26 | 3,819 | +153 |
| 17 Aug 2026, 19:14 | 3,666 | +141 |
| 14 Aug 2026, 22:24 | 3,525 | +90 |
| 11 Aug 2026, 07:07 | 3,435 | +60 |
| 8 Aug 2026, 12:01 | 3,375 | +14 |
| 7 Aug 2026, 20:01 | 3,361 | no change |
| 7 Aug 2026, 19:05 | 3,361 | first reading |
17 posts held, back to 15 July 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 17 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
84 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 58.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 49 | 58.3% | |
| ❤🔥 | 10 | 11.9% | |
| 😍 | 9 | 10.7% | |
| 🔥 | 8 | 9.52% | |
| 💅 | 3 | 3.57% | |
| 💋 | 2 | 2.38% | |
| 💯 | 1 | 1.19% | |
| 😭 | 1 | 1.19% | |
| 🙏 | 1 | 1.19% |
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 16 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 84 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 15 July 2026 to 28 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.
The bot's been updated and is now enabled again.
❤2😍2🙏1
I'll update the bot tonight and add the miniapp. I'll disable the bot for the duration of the update (shouldn't take more than 30 minutes). It's still not complete but since I probably won't be able to work on the bot for the next few days as much, I'll just roll out the update anyways. Report issues you find or features you'd like to be added to the miniapp.
❤5💋1
The miniapp that started as a light miniapp to make using the bot easier is slowly turning into a full featured music streaming app inside telegram 👀
❤🔥5❤1💋1😭1
Video, posted without a caption
❤🔥5💅1
Photo, posted without a caption
😍7❤2💅2
This is the first "prototype". The final version that will be added to the production will probably look a lot better and more polished.
🔥5💯1
The bot's been performing pretty good even with limits increased and delays decreased 😄 I'll now add a feature that nobody's asked for but I just like to add it myself lol. A mini app to make using the bot far easier without using the inline button menus.
❤3
The bot has been updated and is now enabled again. The new metadata resolver is implemented, it's used as the first step in the ladder and if it fails the bot will fall back to the old Spotify API usage. API usage has also been improved and the bot will aggressively cache anything necessary to reduce API usage and avoid rate limits and throttling. I've also improved SoundCloud downloads (but it wasn't a priority an…
❤8
The bot will be updated in a few minutes. I'll disable the bot temporarily and let it finish unfinished downloads so there won't be any partial downloads mid update.
❤2
So it's currently 5:44 AM and I'v been putting most of my time in the past few days + the whole night to find some workaround for this annoying Spotify rate limit without continuously adding more Spotify API credentials. And finally, found a workaround (kind of). If the tests are successful (which so far they've been better than I expected), I might even remove the delays between album song downloads and might even …
❤7
More improvements and Spotify api use optimization coming soon. Also large files not getting sent properly will also be fixed. Some other bugs that the users have reported will also be fixed soon. As the number of users grows, I'll either have to optimize the Spotify API usage more (which it already is, and more optimization will only add maintenance load and has diminishing returns) or add more Spotify API credenti…
❤4
The bot has been updated and is now back online.
❤3
Showing the 12 most recent of 17 posts we hold for @spotdll_updates. 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.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“Soundster” (@spotdll_updates), 2 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/spotdll_updates.
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.