Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TelegramBridge] Images in old posts do not load due to media URLs with expiration date #1901

Open
ValdikSS opened this issue Dec 19, 2020 · 10 comments
Labels
Bug-Report Confirmed bug report

Comments

@ValdikSS
Copy link

Describe the bug
URLs for media in Telegram returned in web preview (https://cdn4.telesco.pe/file/…) are not persistent, they work only for limited amount of time. Due to this fact, the older Telegram posts in the channel have broken images and other media elements in the RSS reader.

The bridge should implement a jumper URLs to the bridge script itself, which would update the links and redirect the request to working updated URLs with HTTP redirect.

To Reproduce
Steps to reproduce the behavior:

  1. Subscribe to Telegram channel using RSS client
  2. Wait ≈2 days
  3. Open older posts containing media elements (images, video, audio)
  4. Result: no media is loaded

Expected behavior
The media should be loaded even in the older posts.

Screenshots
Screenshot_20201219_125058-fs8

The image URL returns HTTP 404.

Desktop (please complete the following information):

  • OS: Linux
  • Browser: QuiteRSS Reader
  • Version: Public bridge on feed.eugenemolotov.ru
@ValdikSS ValdikSS added the Bug-Report Confirmed bug report label Dec 19, 2020
@em92
Copy link
Contributor

em92 commented Dec 23, 2020

@VerifiedJoseph, do you have any idea how to implement those jumper URLs or other ways to solve this issue?

@VerifiedJoseph
Copy link
Contributor

@ValdikSS, does your RSS reader not support local caching of images and other media? Jumper URLs is an interesting idea. I'm not sure how it would be implemented given how the bridges currently work.

@ValdikSS
Copy link
Author

ValdikSS commented Jan 3, 2021

It does not.

@VerifiedJoseph
Copy link
Contributor

Another option would be to cache the images on the server running the rss-bridge, that would simpler to implement.

@ValdikSS
Copy link
Author

ValdikSS commented Jan 3, 2021

Telegram attachments may contain multi-gigabyte videos. I use public feed.eugenemolotov.ru feed, I'm sure it won't be implemented there, at least it will have some retention.
I'd like to open RSS item of several months old and have working media in it, so it's not a complete solution.

@em92
Copy link
Contributor

em92 commented Apr 11, 2021

@VerifiedJoseph, I have the idea. You could add one special context to TelegramBridge. The task of that context is not returning feeds, but make 302 redirections to that media by given URL or something that does identify that media.

With the bridge code addition, it is required to add code, that hides those special context inputs from bridge card.

@squromiv
Copy link

@em92 So should we wait for fix?

@em92 em92 mentioned this issue May 3, 2021
9 tasks
@em92
Copy link
Contributor

em92 commented May 3, 2021

@squromiv no one is assigned to this task, so feel free to make PR.

@squromiv
Copy link

squromiv commented May 4, 2021

@em92
Unfortunately, I am not a software developer, so I can feel free only to make an issue. :-D

@dumprop
Copy link

dumprop commented Aug 16, 2021

I noticed that seems telegra.ph URLs have no expiration date
image
telesco.pe link is dead, telegra.ph no
image
So, anyway telegra.ph links seems more stable
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug-Report Confirmed bug report
Projects
None yet
Development

No branches or pull requests

5 participants