https://termux.xyz/how-to-install-visual-studio-code-on-android-termux/

Channel
alisoftware
@alisoftware
On this record: Topic · Growth · Engagement · Posts · Cite this entry
40subscribers
+1 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 | -1001170537553 |
|---|---|
| Type | Channel |
| Username | @alisoftware |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 4 October 2026 |
| On Telegram | t.me/alisoftware |
Topic
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 30 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 15:38 | 40 | +1 |
| 10 Aug 2026, 20:15 | 39 | no change |
| 7 Aug 2026, 16:46 | 39 | first reading |
Engagement
20 posts held, back to 5 March 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 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 28 December 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://sdrmike.medium.com/rails-7-api-only-app-with-devise-and-jwt-for-authentication-1397211fb97c
https://sasikala-r.medium.com/rails-7-with-vite-stimulus-tailwind-c3ecf2191ea9
https://github.com/termux/termux-packages/discussions/8855
https://stackoverflow.com/questions/74291173/cant-override-x-frame-options-sameorigin-with-x-frame-options-in-the-same
https://www.tecmint.com/restrict-ssh-user-to-directory-using-chrooted-jail/
https://stackoverflow.com/questions/44242267/nginx-wordpress-gives-err-too-many-redirects
https://stackoverflow.com/questions/70405436/next-auth-how-to-update-the-session-client-side
https://github.com/nextauthjs/next-auth/issues/596#issuecomment-943453568
https://dev.to/theodorusclarence/next-js-redirect-without-flashing-content-5bio
https://superuser.com/questions/232373/how-to-tell-git-which-private-key-to-use
https://wordpress.stackexchange.com/questions/53503/can-i-programmatically-login-a-user-without-a-password
Showing the 12 most recent of 20 posts we hold for @alisoftware. 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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“alisoftware” (@alisoftware), 40 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/alisoftware.
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.