DEV Community

Cover image for My News Digest Got a Telegram Channel That Forgets Everything After a Week
Den
Den

Posted on

My News Digest Got a Telegram Channel That Forgets Everything After a Week

A while back I posted here about RealFeedApp, a free digest that collects science and tech news, collapses the retellings into one card, ranks by significance and writes a short summary in your language. Last time it learned to explain itself: every card got three plain-language lines under the summary.

This post is about what happened since. The headline is a Telegram channel, and the most interesting thing about it is a setting: every post deletes itself after a week.

The first version was a wall of text

The idea was obvious. Search engines take months to notice a new site; a channel reaches people the day you post. So the first version did the obvious thing: once a day, the five top stories of the last 24 hours, as one message. Headline, summary, link to the original, repeat five times.

It worked, technically. I opened the first post in the channel and was disappointed.

It was a block of text. No pictures. None of the "in plain words" lines the site had just learned to write. No tags, no sense of which field a story belonged to. And every link went straight to the original source, so the site — the thing that actually does the work — was nowhere in it.

Nobody reposts a wall of text. You can't forward the one story you care about; it's glued to four others. And a reader who skims it learns nothing they couldn't have got from any aggregator.

The lesson was simple and slightly embarrassing: I had built a channel that showed less than the product it was supposed to advertise.

One story, one post, the whole card

So the channel now posts the way the site shows things. One story per message, spread through the day instead of a morning dump. Each post is the card:

  • the cover image from the site;
  • the headline and the summary;
  • the "in plain words" block — the field as a tag, what was done, why it matters — set off from the summary the way it is on the card;
  • tags you can tap through within the channel;
  • a link to the story's page on the site, and from there to the original;
  • the same story in Russian, folded into a collapsed quote at the very bottom.

The link to the site matters most. A post is now a preview of a card, not a replacement for it. If the story is yours, you forward that one post. If you want more, you land on the site, where the rest of the feed is.

Two small rules came out of looking at real posts before they went out. A story whose translation came out broken doesn't get posted at all — a broken word in a feed is a bug; in a public post it's a broken word in front of every subscriber at once. And the channel leans towards news over dense preprints: the feed is for people who opted in to a field; the channel is for people who just followed a link.

One channel, two languages

The site writes every summary in English and Russian, but the first channel was Russian only. That cut out half the readers. Two channels would have split the subscribers instead, and doubled the posting for a project run by one person.

So each post is now an English card with the Russian version inside it, as a collapsed quote: one line and an arrow until you tap it. An English reader never scrolls past Russian text; a Russian reader is one tap away from the full card in their language, with its own link to the Russian page of the story.

Fitting two languages into one post had a side effect. A photo caption in Telegram is short, and one card already filled it. So posts went from "photo with a caption" to a text message with the cover shown as a large preview above it. It looks the same, and there is room for both languages.

Why the posts disappear

Here's the setting I mentioned at the top: the channel's messages auto-delete after a week.

It sounds like throwing work away. It's the opposite.

A channel that keeps everything slowly becomes the product. Scroll back far enough and it's a second, worse feed: no search, no topics, no "hide this", no memory of what you liked, and nothing that gets better the more you use it. If that archive grows forever, it starts competing with the site and the app — and it wins on convenience while losing on everything else.

So the channel is a window, not a home. It shows what's happening this week, and points at the place where the rest lives. A week-old science headline is stale anyway; anything that still matters is on the site.

What else is new

RSS. Every story that goes to the channel also goes into an RSS feed: /en/rss.xml and /ru/rss.xml. The footer has a one-click "Follow on Feedly" link. If you'd rather not use Telegram at all, it's the same stream of hand-picked stories in your reader.

Bluesky. The same stories go to @realfeedapp.com as short threads: the summary with a link card to the story page, then what they did and why it matters as replies. English only — that's where a lot of the science crowd moved, and topic feeds there show posts beyond your followers.

Story pages. Every story now has its own page on the site: cover, summary, the plain-words block, tags, and a clear button to the original. That's where channel posts lead.

A daily archive. Each finished day gets a page with its top stories, open to everyone, no account needed — and an archive that lists the days. If you missed a week, that's the fastest way to catch up.

Links in your language. The feed now has its own address per language (/en/, /ru/, …). Share the Russian version with a friend and they get the Russian version, regardless of what their browser says.

Keywords from a vocabulary. Your own keywords are no longer typed in free text; you pick them from the terms the feed actually uses, and the screen explains what they change. Free text looked flexible and mostly matched nothing.

A quieter, more honest daily digest in the app. The notification gives you one reason to open it instead of a list nobody can read in a notification shade; the app tells you when the next one arrives; and the last digest can be reopened from settings.

A cleaner feed. Threads and discussions no longer show up as news — nothing happens in them, someone just talks about something that did. A story is filed by what it's about, not by where it came from. And a headline that says the opposite of its own summary, or names something the article never mentions, doesn't reach the feed.

Try it

Still free.

Top comments (3)

Collapse
 
wolf2016 profile image
wolf Valencia • • Edited

Making posts expire after a week is a clever answer to the "channel turns into an archive nobody scrolls" problem. Moving to one story per post makes sense too. You can't forward the one story you care about when it's glued to four others.

I'm a Staff SDET, and since you mentioned search engines being slow to notice new sites, two things on realfeedapp.com could be making that slower:

  1. Made-up URLs return a normal page. Something like realfeedapp.com/blog/does-not-exist comes back as HTTP 200 with the homepage content instead of a 404. Google calls these "soft 404s." It can spend crawl time on junk URLs and treat them as duplicates of your homepage. The usual fix is to return a real 404 status, with a not-found page, from the catch-all route.
  2. www.realfeedapp.com and realfeedapp.com both serve the site. Your canonical tag points at the non-www version, which helps, but a 301 redirect from www to the bare domain is the cleaner fix, so every link and ranking signal lands on one address.

We found 10 other issues besides those. Is the Telegram channel already sending more visitors to the site than search is?

Collapse
 
den0011 profile image
Den •

Thanks, both checked out. Unknown paths were returning 200 with the homepage, and the www host was serving the site without a redirect. Both are fixed now: unknown URLs return a real 404, and www redirects with a 301 to the bare domain. A useful catch for anyone running a single-page app with a catch-all route — it’s easy to miss because everything looks fine in the browser.

Collapse
 
wolf2016 profile image
wolf Valencia •

Nice, just checked and both are live: a made-up path now comes back as a real 404, and www lands on the bare domain with a 301. Agreed on the catch-all point, it's one of those bugs where the browser looks perfect and only the status code gives it away. Hope it helps search catch up with the Telegram channel.