In our application we allow customers to manage multiple social channels in one place for a team of social media managers. One of these social channels are Mentions and DMs of Twitter accounts.
Since this was introduced it is no longer possible to simply display images from DMs as requests to those now have to be signed. In the post linked above you propose the following solution: Implement a backend route that basically acts as image proxy – so instead of having the browser request the image directly, the DM image URL is passed to our own HTTP server that checks whether the client has access to the channel using our own authentication method and then a signed OAuth request is made and the image is passed through to the client.
This is not a viable solution though, because as explained in the link above you seem to apply rate limiting to all signed requests. This means that after loading several images / or loading the same image repeatedly – any further Twitter API requests will be blocked. Meaning that not only the DM images do no longer work, but we can’t even make any other API requests for synchronizing our system with Twitter.
- Do you have any plans on working on this issue?
- How do you expect us to deal with this in the meantime?