Urgent.News

What's breaking now, across thousands of outlets.

Tech

How to Monitor Public Telegram Channels for Free (No API Key, No Bot)

You can monitor public Telegram channels for free. No API key, no bot, no server bill. The trick is that Telegram exposes a web preview at t.me/s/<channel> that returns the last ~20 posts as plain HTML. Poll it. The 20-line loop import requests , re , time URL = " https://t.me/s/<channel> " seen = set () while True : html = requests . get ( URL , timeout = 15 ). text for msg_id in re . findall (…

You can monitor public Telegram channels for free without needing an API key, bot, or server bill. The key is that Telegram provides a web preview at t.me/s/channel that returns the last ~20 posts as plain HTML. To monitor these posts, simply poll this URL periodically. The code loop imports the necessary libraries, gets the HTML from the URL with a 15-second timeout, and then uses a regular expression to find all message IDs in the HTML.

If a message ID hasn't been seen before, it's added to a set and printed as a new post. The script then sleeps for 5 minutes before checking again. The post IDs are sequential per channel, so a new max ID indicates a new post. The HTML contains subscriber counts, view counts, forward chains, media URLs, and more. However, this method only provides a window of the last ~20 posts, not a full history.

It also doesn't support private channels. To ensure deduplication across restarts, persist the seen message IDs to disk. The polling cadence is crucial, as 60 seconds would be too frequent for monitoring and 5 minutes is a good balance for alerts and research. This method has been used to monitor around 200 channels for market and OSINT signals.

The full collection-layer playbook, including cursor pagination, repost flags, and alerting, is available for $5 at a provided link.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Turning code-review comments into useful Cursor rules

I asked my agent to build pr-rulebook from an idea that came up in conversation. When I wrote about the result, I included the candidate rule that failed review.

  • Code-review comments analyzed to identify frequently mentioned clues, not established policies.
  • Transforming feedback into Cursor rules requires gathering evidence, not reusing wording.
  • A useful rule specifies what to check, when it applies, and provides a correct example.

How we wire up lead replies that go out in under a minute

A fast reply isn't just "thanks, we'll be in touch". Within a minute of an enquiry arriving, a useful reply should: answer what the person asked, or at least show you read it ask one qualifying…

  • Replies sent within a minute address questions and ask qualifying questions
  • CRM systems like HubSpot and Pipedrive enable automated email replies with sender names
  • AI-powered automation platforms ensure personalized, non-canned replies

Homelab security on 512 MB: warden scores my logs and asks before it bans anything

I wanted one place that tells me what is going on in my homelab: who is poking at it from outside, which boxes have known-exploited CVEs, what needs patching, and whether anything new turned up on the…

  • "Warden" monitors homelab security on minimal resources
  • Combines scanners and adds logic without agents
  • Uses Discord for user approval before taking action

More from Saturday 10 October →