🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)
🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)

🔧 Programmierung 🕛 vor 2 Monaten 3 Min Lesezeit
0

"Scrape Public Telegram Channels Without an API Key, Bot Token or Phone Number"

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

Telegram's official APIs are great, but both come with strings attached: the Bot API needs a bot that channel owners must add, and the MTProto client API wants your phone number and an app registration. If all you need is the public message history of public channels, there is a third door with no strings at all.






The t.me preview pages



Every public channel has a web preview:




CODE
GET https://t.me/s/durov






That returns the latest ~20 messages as server-rendered HTML. No key, no cookie, no login. And it paginates:




CODE
GET https://t.me/s/durov?before=510






gives you the 20 messages older than message id 510. Walk before= down and you can read a channel's history as far back as you care to go.






What is in the HTML



Each message sits in a .tgme_widget_message block with a data-post="channel/id" attribute. Inside:





  • .tgme_widget_message_text holds the message body, links included


  • time[datetime] gives a clean ISO 8601 timestamp


  • .tgme_widget_message_views shows the view count, abbreviated (3.4M)


  • .tgme_widget_message_photo_wrap hides photo URLs in its inline background-image style


  • .tgme_widget_message_forwarded_from_name names the source channel of a forward, with link



The channel card at t.me/<channel> (without /s/) adds the title, bio and subscriber count via ordinary OpenGraph meta tags plus a .tgme_page_extra element.






Two parsing gotchas



Abbreviated and spaced numbers. View counts come as 3.4M or 12.3K, and subscriber counts as 11 862 837 with narrow no-break spaces (U+202F) between groups, which will break a naive parseInt. Normalize both:




CODE
function parseCount(raw) {
const s = raw.replace(/[\s  ]/g, '').toLowerCase();
const m = s.match(/^([\d.]+)([km]?)$/);
if (!m) return null;
return Math.round(parseFloat(m[1]) * (m[2] === 'm' ? 1e6 : m[2] === 'k' ? 1e3 : 1));
}






Not every channel has a preview. Private channels, most groups, and channels that disabled previews return a page with no message blocks. Detect the empty case and report it honestly instead of retrying.






What the preview does not have



Reactions, comment counts and poll results are not in the public preview, so no keyless scraper can offer them truthfully. If a tool claims them without asking for API credentials, be suspicious.






Be polite and it just works



The preview pages are served to every browser and link previewer on the internet, so they are tolerant, even from datacenter IPs. Pace your requests a few hundred milliseconds apart and paginate only as deep as you need.






If you want it as a service



I packaged this as a pay per use actor: public channel usernames in, one JSON row per message out (text, date, parsed views, links, media, forward source), plus a free channel info row with the subscriber count: https://apify.com/scrapemint/telegram-channel-scraper



Same theme as the rest of my actors: find the public endpoint a platform already serves, skip the browser, and the data costs almost nothing.

Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Hackers Just Poisoned the Rust Supply Chain | Threat Wire
1 Quelle
Hackers Found a Way Into Humanoid Robots | Threat Wire
1 Quelle
Bits und so #1021 (Passwort für Laufwerk)
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten "Scrape Public Telegram Channels Without an API Key, Bot Token or Phone Number"

Thematisch verwandte Begriffe: Scrape, Public, Telegram, Channels · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...