Camo for external images

[NemesisRE]

I was searching for an easy way to get full SSL compliance in TT-RSS, while I was searching I found out that Github ran into the very same problem (https://github.com/blog/743-sidejack-pr ... ied-assets) and so they developed Camo.

I thought this could be a great addition to the TT-RSS core (this https://github.com/willwashburn/Phpamo should help).

If you think it's not worth the afford or you don't have time at the moment, then I will try to build this as a Plugin.

And as always keep up the good work fox!

regards
NemesisRE

[JustAMacUser]

Can't one just turn on image caching to get full SSL?

[fox]

i recommend medication, op

call a doctor or something

[NemesisRE]

But image caching is only for stared articles, isn't it? Sure I can do that on my own for every feed I add but if I want force it for every user there is no way, right?

[JustAMacUser]

Image caching is for feeds, there is a plugin bundled with TT-RSS that will also, separately, cache images for starred articles. This plugin needs to be enabled as a system plugin in the config.php file.

If you want every feed for every user to cache every image, then you could do that with a plugin a few different ways. The most effective would be to hook the articles as they come in and cached the images regardless of the cache_image setting. You could, alternatively, change the database schema to make the cache_image setting default to true then setup a hook during house keeping that constantly resets it should the user change it. This is obviously less effective.

But to use a separate proxy that basically does what TT-RSS is natively capable of doing doesn't make sense.

[NemesisRE]

Image caching is for feeds, there is a plugin bundled with TT-RSS that will also, separately, cache images for starred articles. This plugin needs to be enabled as a system plugin in the config.php file.

If you want every feed for every user to cache every image, then you could do that with a plugin a few different ways. The most effective would be to hook the articles as they come in and cached the images regardless of the cache_image setting. You could, alternatively, change the database schema to make the cache_image setting default to true then setup a hook during house keeping that constantly resets it should the user change it. This is obviously less effective.

But to use a separate proxy that basically does what TT-RSS is natively capable of doing doesn't make sense.

You were right if i suggest a caching proxy but what I am suggesting is a passthrough proxy. This means less space on the hosting server but more traffic, this is because space costs me money but traffic not.

[JustAMacUser]

Your original post said you wanted full SSL, now you're saying you want a proxy. The net effect of what TT-RSS has built in is the same as what you propose so why re-invent the wheel? Except that now you say you can waste bandwidth but not storage.

You can easily write a plugin for this, it would take about 15 lines of code and most of that would be the bare class structure. But adding this feature to the core seems unnecessary... I'm sure fox agrees but I would recommend not asking him since you might not like his presentation style.

[fox]

no features for privacy freaks is my motto

[NemesisRE]

Well in my first post i redirected to the github blog to fingerpoint camo so I did say from the very beginning what kind of solution I try to achieve
I use TT-RSS from that time google said they will drop reader so I know fox's presentation style very good
I thought about a core plugin not a full core implementation because not everybody wants extra software to run, that was what I wasn't saying clearly.

And that I use SSL is more of security than privacy

I will try my luck on writing a TT-RSS/Camo plugin.

But again keep up the good work fox, still love TT-RSS!

[atrus]

In case people stumble across this thread, I believe the af_zz_imgproxy plugin is relevent here: viewtopic.php?t=4052