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
I am currently working on privacy options for the web frontend to block all external content that is not already removed by feed-io and HtmlSanitizer or only display it on demand.
This mainly affects images, as videos and audio files are generally only be loaded by pressing a start button.
The current plan is to offer several global user options where the different types of integration can be configured.
The consent buttons show the domain and, via tooltip, the link to the file, which can become confusing with srcset when there are many links.
Iframes consent buttons can show the title if available.
The current plan would therefore be to force preload="none" for video and audio in the article text so that these are also only loaded on demand, as is the case with media or enclosure.
Images via <enclosure type="image/\ *">, which have been ignored until now, can be displayed accordingly.
As shown above, the various sources can be controlled for images and iframes in the article text.
These would currently be <picture>, <img> and <iframe>.
If anyone has any suggestions or ideas for this feature, please feel free to write here.
In addition, feed examples with a lot of media content would be helpful for testing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I am currently working on privacy options for the web frontend to block all external content that is not already removed by feed-io and HtmlSanitizer or only display it on demand.
This mainly affects images, as videos and audio files are generally only be loaded by pressing a start button.
Related Topics:
#1659
#3212 (reply in thread)
The current plan is to offer several global user options where the different types of integration can be configured.
The consent buttons show the domain and, via tooltip, the link to the file, which can become confusing with
srcsetwhen there are many links.Iframes consent buttons can show the title if available.
The current plan would therefore be to force preload="none" for video and audio in the article text so that these are also only loaded on demand, as is the case with media or enclosure.
Images via
<enclosure type="image/\ *">, which have been ignored until now, can be displayed accordingly.As shown above, the various sources can be controlled for images and iframes in the article text.
These would currently be
<picture>,<img>and<iframe>.If anyone has any suggestions or ideas for this feature, please feel free to write here.
In addition, feed examples with a lot of media content would be helpful for testing.
All reactions