rss-bridge: Image scaling in Twitter is not working anymore

Describe the bug Before, Twitter embedded pictures with tags about their size, like: example.jpg:thumb example.jpg:orig

Some RSS readers were not able to handle that correctly, that’s why @LogMANOriginal introduced the option disable image scaling back in 2018, as mentioned in this thread. The problem was fixed by this commit.

However, it seems that Twitter changed the naming scheme to: example.jpg?name=thumb example.jpg?name=orig

This introduces the problem that pictures and videos are not shown anymore when disable image scaling is active (broken link).

To Reproduce

  1. Subscribe to a Twitter user with disable image scaling is activated (checkbox).
  2. Have a look at the Atom feed: Embedded media (images and videos) are not shown, there are broken links instead.

This bevaiour is the same when disable image scaling is not activated. So this function is not working anymore, because Twitter changed the name scheme.

Expected behavior When using disable image scaling, the feed should load with the orig pictures embedded as it was before, when the fix was applied in 2018.

Desktop (please complete the following information):

  • OS: Linux Mint
  • Browser: Firefox
  • Version: 97.0

Smartphone (please complete the following information):

  • Device: Fairphone 3
  • OS: Android 10
  • App: TinyTinyRSS

RSS-Bridge:

  • Running on Docker
  • Tag: latest

I would be really happy if you could have a look at this issue and maybe change the bridge to meet the current beviour of Twitter.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 21 (11 by maintainers)

Most upvoted comments

For the record, i’m using tt-rss with twitterbrigde (1.1) and images are working.

I’m using lastest commit on master branch from git repo for tt-rss. I’m also using ttrss-reader app on android. Both are working

My settings in tt-rss are Always display image attachments => off Do not embed media => off Cache media => some off, others on (so has no effect on the problem)

Have you taken a look in your browser console, if there are some kind of error messages ? Have you tried to open the link to the graphic directly in your browser ? If so, what error message do you get ?

EDIT: I have planned to try the new twitterbridge (V2) in the next days.