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

  • Resolved Manni79

    (@manni79)


    6 years, 3 months ago

    Hello,

    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. Option: “If the image is not httpS, then don’t use the post image but use the default image”
    That would be nice, 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 of without httpS will be skipped.

    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.
    And also if I miss a way to get rid of the “httpS warining” 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 6 years, 3 months ago by Manni79.
Viewing 3 replies - 1 through 3 (of 3 total)

  • FWIW, in the meantime, you might want to try to limit your feeds to those which are httpS.

    Thread Starter Manni79

    (@manni79)

    Of course I could, but some of the sources are good so I want to have them active.

    Perhaps a first quick fix (quick change) to simply integrate a option to skip all none Http(s) images source (and choose the default image, same as the content has no image) would be enough and not hard to implement.

    A better solution later would be nice. Also because of other advantages as sizing the image, etc.

    Madalin

    (@madalin_themeisle)

    Hey there,

    Thank you for providing all these suggestions about our product’s improvement.?? I have just informed our developers about your ideas.

    Even though we always appreciate receiving feedback and suggestions from our customers (we encourage that) as it gives us the opportunity to improve our products, we can’t promise it will be added to the product for sure.

    ??I hope we’re still good and I hope you have a great day!

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.