Rongrong

> Thanks for the reply, Thanks for the wonderful plasmoid ;-) > Do you think an chart is useful for that ? Cause i think we can simply add it...

> * adding an warning message about the risk of granting read permission. (_cf. [platypusattack.com](https://platypusattack.com/)_) Working around the vulnerability is possible. IMO adding a random number to it should be...

> Ok so you think to have different update interval AND history amount for that particular chart ? Even with that i think the change could be too short or...

I consider that simply removing the option to keep comments is acceptable. Thanks for your work!

> I would suggest replacing all `` usages with ``, as that should be more semantically correct in this case. No, we can't do that, it's invalid to have nested...

For self-hosted instances, refer to #10874 for more available workarounds.

> > For self-hosted instances, refer to #10874 for more available workarounds. > > Sorry, I can't fully understand how to use "image_hotlink_template". Could you please explain it in detail?...

Ohh, I see. `sinaimg.cn` has been upgraded, it bans requests **from browsers** without `referer` set to `https://weibo.com`. However, the limit is only applied when the request is **from Mainland China**....

If you deploy https://github.com/Rongronggg9/rsstt-img-relay on Cloudflare, a referer is unnecessary as Cloudflare has no edges in Mainland China.

> > If you deploy https://github.com/Rongronggg9/rsstt-img-relay on Cloudflare, a referer is unnecessary as Cloudflare has no edges in Mainland China. > > 这个方法也失效了 https://github.com/DIYgod/RSSHub/issues/10874#issuecomment-1369647937