You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discord will cache images when produced from a URL, causing solar data images that can be days or weeks old.
Steps to reproduce
solar
Expected behaviour
Suspect serving an image the same way the svg images are gathered and producing with attachment:// would suffice with a realtime image instead of a cached image from the URL
How did you download qrm?
Git (clone)
How are you running qrm?
Docker
What qrm version are you running?
v2.7.4
Environment
No response
Logs
No response
Additional context, screenshots, etc
No response
The text was updated successfully, but these errors were encountered:
hamqsl's images don't support giving any kind of timestamp in a way that affects the generated image (like the greyline map does), and adding a unique nonce just for discord doesn't work (see #308 and #318, especially #318 (comment)).
We've spent a while on this issue and the only reasonable solution seems to be making a small cdn/image proxy, which we haven't had time to implement yet.
Bug description
Discord will cache images when produced from a URL, causing solar data images that can be days or weeks old.
Steps to reproduce
solar
Expected behaviour
Suspect serving an image the same way the svg images are gathered and producing with
attachment://
would suffice with a realtime image instead of a cached image from the URLHow did you download qrm?
Git (clone)
How are you running qrm?
Docker
What qrm version are you running?
v2.7.4
Environment
No response
Logs
No response
Additional context, screenshots, etc
No response
The text was updated successfully, but these errors were encountered: