I found a small edge case bug during testing, so I'm pushing the release back a few days. It's a quick fix, if I can carve out the time, the release should land Tuesday or Wednesday.
👍8

Channel
@powerampache
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
236subscribers
+8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002092999604 |
|---|---|
| Type | Channel |
| Username | @powerampache |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/powerampache |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 11:56 | 236 | -1 |
| 5 Sept 2026, 00:21 | 237 | +4 |
| 21 Aug 2026, 13:46 | 233 | +4 |
| 15 Aug 2026, 04:58 | 229 | +1 |
| 8 Aug 2026, 10:17 | 228 | no change |
| 7 Aug 2026, 23:03 | 228 | first reading |
20 posts held, back to 13 December 2025 — 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 20 posts for this entry, the most recent from 27 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.
189 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 39.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 74 | 39.2% | |
| ❤ | 44 | 23.3% | |
| 🔥 | 24 | 12.7% | |
| 👏 | 18 | 9.52% | |
| 🤬 | 13 | 6.88% | |
| 🎉 | 6 | 3.17% | |
| 😢 | 3 | 1.59% | |
| 😁 | 2 | 1.06% | |
| 😱 | 2 | 1.06% | |
| 🙈 | 2 | 1.06% | |
| 👨💻 | 1 | 0.529% |
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 18 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 189 reactions 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 13 December 2025 to 27 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.
I found a small edge case bug during testing, so I'm pushing the release back a few days. It's a quick fix, if I can carve out the time, the release should land Tuesday or Wednesday.
👍8
⚠️ Texas Users (likely other states will follow up) . Important! Google has notified me that Texas SB 2420 is now in effect after a federal appeals court lifted an injunction on May 28. This law requires age verification and tracking via Google's proprietary Play Age Signals API. Power Ampache 2 will never implement age verification or any proprietary tracking library. Principles aren't negotiable. This stand may …
❤23👍11
A decade ago I was already neck-deep in RxJava while the Android community looked at me like I'd lost the plot. "Reactive programming on Android? Unnecessary. It'll never stick." Fast forward to today and LiveData and Flows ( its reactive descendants) are some of the most basic android patterns. Power Ampache was already thinking ahead, wasn't such a terrible idea after all. Same thing with Power Ampache 2 I try to s…
👏9👍1
anyone remembers this?
This morning I randomly realized it's been 10 years since my first commit for Power Ampache, the original, the one that started this whole ride
❤4👏2
This one was mostly dedicated to Auto. The next update will come very soon, I'm fixing some bugs from Github-Issues and improving some other features
👍1
—— — NEW RELEASE 1.01-88 —— (https://github.com/icefields/Power-Ampache-2/releases) ANDROID AUTO FDroid and PlayStore releases coming up in a few days, as usual. To start using Android Auto (beta) join the plugin testers room. — [NEW] Created transfer data protocol for Auto. — Bug fixes and improvements. — Improved init config. — (contd) Code refactoring and cleanup. Please report any bug. The app is actively m…
Testing's done, the code demons have been appeased. Last changes for v1.01-88 are pushed and the PR review is now in session. Release drops the moment review clears. This version is required for the new Auto plugin, both the plugin and the PA2 update will hit the streets on the same day. Beta testers volunteers: I know many of you reached out to test the Auto plugin. I appreciate the hunger. I created a dedicated t…
👏6🔥4
ANDROID AUTO UPDATE I know I've been announcing this for a month and missing the mark every time, but this time it's actually happening. The Auto plugin is very close to release. I kept hitting weird issues every time, but now every blocker that kept me from shipping a beta is gone. Only one bug remains on the hit list, and I already know how to kill it. That gets handled between now and tomorrow morning. Once thi…
🔥9❤4
Auto Plugin is looking nice! I will try to release the Beta on the same day I make the new app release
🔥5👍1👨💻1
DEV UPDATE I’ll be wrapping up the new version of Power Ampache 2 over the next week or 2, along with a beta release of the Auto plugin. It’s been a particularly busy month, so progress on PA2 slowed slightly, but I’m already back to a more consistent update schedule. The wait should be worth it. This new version is packed with improvements and fixes, and the Auto plugin will finally be available.
👍7🔥6❤1
F-Droid is taking longer than expected to publish the app this time. It appears the build job is failing due to their migration to a new server running Java SDK 21. I’ve reached out to them and requested that the job be restarted.
👍6😁2
Showing the 12 most recent of 20 posts we hold for @powerampache. 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Power Ampache 2” (@powerampache), 236 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/powerampache.
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.