TelegramBridge currently includes Telegram's web fallback block in item content for many public channel posts:
"Please open Telegram to view this post"
"VIEW IN TELEGRAM"
Example public channel:
https://t.me/s/skidka_13
This text appears in the generated RSS/MRSS item content and is visible in RSS readers, even though it is only Telegram's web preview fallback UI, not the actual post content.
It looks like this comes from div.message_media_not_supported_wrap / message_media_not_supported_label, and TelegramBridge intentionally appends it in processContent() / processNotSupported().
Expected behavior:
TelegramBridge should probably omit this fallback UI text from feed content, or expose an option to hide unsupported-media fallback blocks.
Actual behavior:
Many Telegram feed items contain the extra text before or around the real post content:
Please open Telegram to view this post
VIEW IN TELEGRAM
This makes feeds noisy, especially for Telegram channels where Telegram frequently emits this fallback block on t.me/s/... pages.

TelegramBridge currently includes Telegram's web fallback block in item content for many public channel posts:
"Please open Telegram to view this post"
"VIEW IN TELEGRAM"
Example public channel:
https://t.me/s/skidka_13
This text appears in the generated RSS/MRSS item content and is visible in RSS readers, even though it is only Telegram's web preview fallback UI, not the actual post content.
It looks like this comes from
div.message_media_not_supported_wrap/message_media_not_supported_label, and TelegramBridge intentionally appends it inprocessContent()/processNotSupported().Expected behavior:
TelegramBridge should probably omit this fallback UI text from feed content, or expose an option to hide unsupported-media fallback blocks.
Actual behavior:
Many Telegram feed items contain the extra text before or around the real post content:
Please open Telegram to view this post
VIEW IN TELEGRAM
This makes feeds noisy, especially for Telegram channels where Telegram frequently emits this fallback block on
t.me/s/...pages.