Caching Images, Fixing HTTPS Warning, GDPR , at least skipp non-https images

  • Resolved Manni79

    (@manni79)


    5 years, 6 months ago

    Hello dear FEEDZY Feed Support,

    One of my old topics is closed now, but because some months are over now, I reach out to you and want to ask if you found ways to solve these big problems:

    https://www.ads-software.com/support/topic/caching-images-fixing-https-warning-gdpr-at-least-skipp-non-https-images/#post-10709351

    I think we had a discussion a few years ago. We talked already about a feature to cache the images from other blogs which FEEDZY show in the list when you used the FEEDZY image option. There are a bunch of problems, because FEEDZY is taking the original Link to the original image.

    First Problem are HTTPs Problems. Instead of Caching Images locally to get to fix the warnings which appears if a blog is not using httpS for his images, you could also implement a new option. New Option: “If the image is not httpS, then don’t use the post image but use the default image”
    That would be nice and easy, so we can activate showing images, also when some of the used blogs in the FEEDZY list have http without SSL and only the images without httpS will be skipped and showed as the default image.

    We don’t want to skip non-httpS posts, because some of them are important.

    Or you consider to implement to Cache the images, this could have some more advantages:
    – sometimes faster and more consistent if source page is slow.
    – you can convert the image directly in a size needed
    – I’am not sure you actual way is GDPR compliant. Do you know it? Because when asking for images on other pages, I think the IP will be transmitted. And this must be Opt-in as I know in GDPR. So perhaps redirect users to the original image source without the consent of the user, could be non GDPR complaint. But perhaps you know it better.

    Would be nice to hear something about your GDPR opinion.

    We need a change also to get rid of the “httpS warning” of the Browser, when having some blogs in FEEDZY lists which using non-httpS for their images. And if there is no way actually, would be nice to see my suggested feature to skip non-httpS images.

    best regards
    Manni

    • This topic was modified 5 years, 6 months ago by Manni79.
    • This topic was modified 5 years, 6 months ago by Manni79.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor contactashish13

    (@rozroz)

    @manni79 thank you for your relevant and detailed suggestions! We will consider adding a caching feature for images sometime in the future. Till then we have added an additional parameter to tackle the issue with HTTP images on HTTPS sites. If you take a look at the shortcode builder in the classic editor, you can see it as the last option in “Item Image Options”. Let me know if it works well for you.

    For GDPR, we don’t offer legal assistance and our scope is to build products that are GDPR compliant to match our users’ needs. In the case of Feedzy RSS, no data is transmitted because it’s merely an HTTP call like on a browser. We are transparent about how our products are built, and when personal data is collected, stored or processed the users are informed.

    My recommendation is to talk with a professional data privacy expert if something is not clear about GDPR, and I am happy to answer your questions about how the product works if you have specific questions.

    Thread Starter Manni79

    (@manni79)

    @rozroz Thank you for your answer! I will take a look about this new feature.

    But image caching would still be a great option. Also for Google Page Speed Ranking. The pics Feedzy needs are most of the time very small. But it used the main image of the Blog which is often a big picture. So Feedzy show 10-20 pictures (related hoe many blogs you show on one page) with often a very big image size and scales it down, where only a very small picture is needed.

    Would be nice to see this needed feature in the future. This feature is such great, I think you can offer it as paid additional feature in a paid version of Feedzy. I think it is a major advantage.

    Plugin Contributor contactashish13

    (@rozroz)

    @manni79 we will definitely consider your suggestion. Thank you for continuing to use the plugin and offer such valuable suggestions!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Caching Images, Fixing HTTPS Warning, GDPR , at least skipp non-https images’ is closed to new replies.