Channel
@Hoody
On this record: Growth · Engagement · Posts · Cite this entry
390subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001271406852 |
|---|---|
| Type | Channel |
| Username | @Hoody |
| 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 | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/Hoody |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 09:08 | 390 | -2 |
| 16 Aug 2026, 18:04 | 392 | -3 |
| 8 Aug 2026, 05:50 | 395 | no change |
| 7 Aug 2026, 21:21 | 395 | first reading |
20 posts held, back to 31 October 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 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 December 2025. An engagement rate over an empty window would be a number about nothing.
The Permissionless Internet Authentication is friction. Unguessable URLs become the permission system: Public: https://blog.com Private: https://5f68dab2adbeb2558bdd3bbf-48f1a1f1.hoody.com Share secrets without passwords. Collaborate without user management. Build services without auth. The 48-character string becomes security. Access control becomes URL distribution. Security through cryptography, not complexity…
What Happens When Setup Time Goes to Zero? Setup friction kills experimentation. Containers spawn in 3 seconds—everything changes. Try wild ideas without hesitation. Test in production-identical environments. Give each branch full stack. Spawn containers for single commands. The cost of trying approaches zero. Innovation accelerates. Ideas become implementation instantly. When failure costs nothing, you try every…
Computing Without Borders Start work on laptop. Continue on phone. Present from borrowed computer. Your environment follows through URLs. Physical devices become viewports into persistent cloud environments. Applications continue running. Files remain accessible. Terminal history persists. AI remembers conversations. Morning: Check builds on phone Commute: Review on tablet Office: Develop on desktop Evening: Commi…
Build a SaaS in a Single File Forget frameworks and boilerplate. Any JavaScript file becomes a live API: // billing.js - complete SaaS if (request.path === '/subscribe') { return processPayment(request); } if (request.path === '/webhook') { return handleStripe(request); } return dashboard(request); Save file. It's live at your domain. SSL included. Scaling automatic. The shared object maintains state. SQLite …
The Zero-Infrastructure Startup Traditional startup: Provision servers, configure databases, setup CI/CD. Modern startup: Create one container. That container becomes: - Development environment - Staging server - Production infrastructure - Backup system - Monitoring dashboard Setup time: 3 seconds. Config files: 0. Unlimited containers. Focus 100% on product. Infrastructure handles itself. Scale happens automat…
Your Terminal Has Infinite Memory Command history usually dies with sessions. Not anymore. Every command persists to /hoody/storage/logs/terminals/. AI agents read this history, understanding context from past sessions. Close terminal, open months later—complete history remains. $ ai "What was that ffmpeg command?" > ffmpeg -i input.mp4 -vf scale=1920:1080 > Used on 2024-07-15 Your terminal becomes a knowledge ba…
SQLite That Just Works (Even at Scale) SQLite's simplicity breaks when multiple processes write. Now they can: // Container A writes db.query('INSERT INTO events...').run(); // Container B writes simultaneously - no locks! db.query('INSERT INTO logs...').run(); No connection pools. No lock errors. No configuration. Multiple containers, processes, all writing safely to same SQLite database. The simplicity of SQLi…
Why File Systems Should Be APIs Files in folders is prehistoric. Every file becomes an HTTP endpoint: curl https://{container}-files.hoody.com/data.json curl https://{container}-files.hoody.com/?q=config curl https://{container}-files.hoody.com/?json No mounting drives. No FTP. Just URLs working everywhere—scripts, browsers, mobile apps, AI agents. Your filesystem becomes universally accessible, programmable, sha…
Multiplayer Everything: The Future We Didn't See Coming Single-user software is obsolete. Every application becomes collaborative by default. Open VS Code at display-1. Teammates join the same URL. Everyone edits simultaneously, debugs together, sees cursors. No screen sharing. No special features. Works for ANY software: - Your browser becomes multiplayer - Terminal sessions share history - Database clients show …
The Browser Is Your New Operating System Install nothing. Own everything. Your browser becomes the only software you need. Access a full desktop, any application, development environments—all through browser tabs. Each tab is a different computer, different OS. Tab 1: VS code Tab 2: SQLite Browser GUI Tab 3: Testing server Applications stream from containers. Storage persists in the cloud. Your 8-year-old laptop …
What If Every App Had a URL? Launch VS Code—it's at display-1. Firefox? display-2. Terminal? terminal-1. Each application gets a globally-accessible endpoint: https://{container}-display-1.containers.hoody.com/ These aren't remote desktop sessions—individual applications stream through browsers. Share your IDE by sharing a link. Embed tools in documentation. Multiple developers access simultaneously. Software dis…
The Day Your GitHub Issues Started Fixing Themselves Imagine opening GitHub to find issues already resolved, tested, and merged. Autonomous AI agents make this reality. The workflow runs without intervention: 1. AI reads GitHub issue 2. Spawns fresh container 3. Implements fix 4. Runs tests until passing 5. Creates pull request Failed attempts? AI rolls back using snapshots, tries different approaches. Multiple co…
Showing the 12 most recent of 20 posts we hold for @Hoody. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Hoody” (@Hoody), 390 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/Hoody.
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.