-
-
Notifications
You must be signed in to change notification settings - Fork 255
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable use of image proxies #1112
Comments
@iNtEgraIR2021 Thank you for the proposal! Adding it in the DownloadImageHandler would only work images that are dowloaded by the app itself
In the detail view images are downloaded by the WebView. In order to redirect them through an image proxy there are two options:
I'm not sure which one would have less sideeffects.. both options require that the image urls have proper file extensions to match against) (I personally like the first option better). In general from a privacy standpoint I agree that it makes sense to support proxies. However quite a few publishers use advertisement etc as well which can be used for tracking so I'm not sure how big the benefit will be in the end. |
thanks for looking into this 馃憤馃徏 Option 1 sounds promising to me. |
As a side note: I added |
Thanks for working on this so quickly 馃憤 |
Hi,
I love this great app. Also thumbs up 馃憤馃徏 for you fast reaction to the security incident fixed in the last release.
As to my personal understanding this app downloads images straight from their (external) sources it would be a great improvement in terms of UX to me personal to be able to use an image proxy. (say
images.weserv.nl
orexternal.duckduckgo.com
, or a self hosted server etc. ...).That would increase privacy and might also decrease bandwidth usage. (say by using
webp
output instead of originalpng
orjpg
).It should only take an additional user preference and a format string in
DownloadImageHandler.java
.The user would enter e.g.
https://weserv.images.nl?url=%s&output=webp
.Looking forward to your feedback.
Regards, Petra
The text was updated successfully, but these errors were encountered: