Using https with embedded videos would solve the problem, except that the anonym.to redirection (which still uses http) would prevent the video being shown. Should we disable anonym.to for embedded videos? The purpose of anonym.to is to hide at which site the video is embedded (it does *not* hide the user IP like an anonymous proxy or something). I don't know how much youtube account owners can see, but looks like visitors can no longer see referrers at youtube anyway.Phuzzy4242 wrote:People should also be aware Firefox itself has added protections for sites that use https: but also have content sent by http: (for instance, embedding YouTube videos here). If you see the little shield in the address bar, [Image] you have to click it and select "Disable Protection On This Page. This was just added to Firefox recently and I haven't found a way to disable it. I don't really want to disable it, but being able to whitelist sites would be useful because it shows on every page with mixed http/https..