Turn a Noisy Telegram Channel Into a Long-Video Feed

You can forward Telegram videos by their running time instead of hoping the caption says “full lesson.” RedFox Auto Forward Telegram supports video-duration rules in Whitelist and Blacklist. Use a duration-only whitelist policy for a destination that should receive matching videos; use a blacklist when you want to reject short clips while leaving other eligible posts in the feed.

That turns a mixed source of lessons, trailers and chat into a more useful viewing feed without manually checking each upload. A duration rule selects media; it does not understand the lesson’s subject or trim a long video into a shorter one.

RedFox’s October 26, 2026 media-filter announcement introduces duration and size rules, blacklist priority and intact albums on Web and Telegram Bot. The current media Whitelist guide and media Blacklist guide specify that creating or editing these rules requires an active Platinum or Trial Platinum plan. Sources were checked November 3, 2026. RedFox develops the product; Auto-Bot.io publishes this guide.

Choose “only long videos” or “everything except short clips”

These are different editorial policies. Pick one before opening the rule editor.

• A long-video library: use a video-duration Whitelist rule. A standalone text notice or photo does not become a qualifying video just because its caption contains “lesson.”
• A mixed community feed without teasers: use a Blacklist rule for videos shorter than your chosen threshold. That rule alone does not reject ordinary text or photos; other active rules still apply.

Whitelist rules use OR, not an automatic intersection. A message can pass by matching any one attached whitelist rule. An existing keyword rule can still admit text or photos, so a video-only policy needs its own task with no alternative whitelist paths. Two separate duration whitelists do not create a bounded time window: “at least five minutes” plus “at most ten minutes” is not a five-to-ten-minute range.

For a training channel, a useful example policy is “accept standalone videos at least five minutes long.” Five minutes is your selection choice, not a product limit or a test result. A different audience might need a different threshold.

Length is not quality. A long advertisement can meet the duration condition, while a short but important correction can fail it. Keep essential notices on a separate appropriate route if your library is deliberately video-only. If you need to select by wording instead, use the separate whole-word keyword filtering guide.

Scope the rule to one controlled route

Start with content you own or may redistribute and a private destination you control. Preserve the current task’s rule settings and confirm the exact source and target before editing. If you are new to forwarding, use the existing setup guide rather than changing a working audience route as an experiment.

1. Open the AutoForward Web App and Whitelist or Blacklist → Add New. Choose the list that matches the policy above. RedFox also announces media-rule configuration through @AutoForwardNew_Bot.
2. In Filter type, choose Video duration and enter a recognizable label. Do not use a Basic keyword rule for a duration comparison. Video duration, Video size and Document size answer different questions.
3. Select the operator, value and unit. For the example long-video whitelist, choose >=, enter 5 and select m. Check the preview reads at least five minutes. For the mixed-feed blacklist, use <, 5, m instead. “Greater than” without “or equal” would exclude the exact boundary.
4. Select only the intended test task’s Forward connection, then choose Create Whitelist or Create Blacklist. The docs also allow linking a saved rule from its list. Keep the rule off unrelated tasks; Apply For All Tasks would spread this library-specific policy globally.
5. Review the saved rule and task association. The media type is fixed when editing; create a separate rule if you need a different type. Check fresh source posts in the private target, not merely that the rule exists in the list.

Use Web or the bot for the media-rule controls described here. The product also has mobile apps, but their general availability does not establish that this particular rule editor is exposed on every mobile build.

Do not exclude the videos you meant to keep

A matching whitelist does not overrule a matching blacklist. RedFox explicitly gives Blacklist priority in the media-filter announcement. For example, a qualifying long video can still be blocked by a separate rule matching a promotional phrase in its caption.

Also check the task’s ordinary type filters. RedFox’s Filter By Type documentation says turning a type filter on excludes that message type. Enabling Video because you want videos would select the opposite behavior. Cleaner is different again: it removes parts of content rather than making the same whole-post eligibility decision.

For the first controlled comparison, isolate unrelated rules on the test task, not on your live audience route. Add necessary exclusions back one at a time. If a captioned post arrives without its media or text, use the filter-versus-Cleaner diagnostic for that separate symptom instead of lowering the duration threshold.

Check both sides of the duration boundary

Before the intended production rollout, compare fresh, owned standalone samples with a known working baseline on the same test route. Keep the source links, actual media duration, active rules and observed destination result together. The following expected outcomes assume the five-minute duration whitelist is the only eligibility rule under examination.

• A short teaser below five minutes: it should not qualify.
• A video exactly five minutes long: it should qualify for the inclusive comparison.
• A longer video with an ordinary caption: it should qualify; inspect video playback and caption separately.
• A text-only post saying “ten-minute lesson”: it should not qualify as a video.
• A video uploaded as a file/document: it is not a Video duration match. The documented Document size rule applies to that media type, not its running time. Under a short-video blacklist alone, a clip sent as a document is not rejected by that duration rule.

First establish that the relevant samples can reach the private destination without this media rule. Then enable the single duration condition and send fresh comparable samples. Keep the short-video rejection as well as the positive long-video result. A missing copy alone cannot distinguish a rule exclusion from a sending or access problem.

If the boundary sample fails unexpectedly, inspect its actual metadata, the saved comparison and task association before changing the policy. If you cannot explain a result, retain it as unresolved and restore the test configuration rather than stacking changes onto the live feed.

Treat an album as a group, not a bag of clips

The announced media rules keep albums together; they do not extract individual matching videos from an album. Include an all-qualifying video album and an album with a short clip or a different media type in your controlled check. Under a duration-only whitelist, a member that cannot satisfy the rule can prevent the group from qualifying; do not plan on receiving just the long member.

A blacklist match on any album member blocks the entire album. In the mixed-feed example, a short trailer inside the same album as a full lesson can therefore keep the whole lesson package out, not just the trailer. Check the complete group against the policy you selected.

This matters when a lesson is packaged with a trailer or a cover photo. Decide whether the intact group belongs in your destination before rollout. Do not tell members that a duration filter will automatically split that package for them.

The separate Album Delivery Modes guide covers grouping and delivery behavior. Changing a delivery mode is not a replacement for checking whether your media rules admit the album.

Roll out the policy, not an unexplained lucky sample

Once the positive and negative cases behave as intended, apply the reviewed rule to the one audience route that needs it. Keep unrelated tasks unchanged, retain the previous configuration and compare the first real eligible videos with their target copies.

For multiple sources, repeat the check for the actual media patterns they publish. A source that sends ordinary videos and one that uploads lesson files may need different policies. A duration rule does not infer missing metadata from the caption or evaluate the educational value of a clip.

Changing a live rule does not itself establish that older skipped posts have been copied. If you also need historical material, plan it as a separate history-to-live handover; do not launch a large Clone just to test a new ongoing-feed filter.

Frequently asked questions

Is file size a substitute for video duration?

No. A large file can be a short high-bitrate clip, and a longer video can be heavily compressed. RedFox announces separate video-duration, video-size and document-size rules. Choose duration for a running-time policy.

Can a whitelist force a blacklisted video through?

No. The media-filter announcement says blacklist rules take priority when they match. Review both lists and other active task conditions when an expected video is absent.

Can I create these media filters on Free?

The current media-filter docs require an active Platinum or Trial Platinum plan to create or edit these rules. Eligible new users can try Platinum for five days, according to RedFox’s current product guide. Basic Free forwarding does not establish media-rule eligibility; confirm your account’s active entitlement before configuring this workflow.

Give viewers a feed worth opening

Start with one duration policy and one controlled route in RedFox Auto Forward Telegram. Choose whether you want a video-only library or a mixed feed with short clips excluded, then verify both the intended acceptance and rejection before rollout.

Use Web for the announced media-rule management. Choose iOS or Android for the product’s broader app management where the needed controls are available. Web and apps provide fuller general management than the bot entrypoint; active forwarding runs in RedFox’s cloud without keeping the management interface open. The current bot is @AutoForwardNew_Bot, replacing @Auto_Forward_Messages_Bot.