In the comments on this meta answer, a person said:
When I click on your link, Chrome says "Attackers might be trying to steal your information".
The link in question was from this quote:
Questions seeking an explanation of someone else's code are also off-topic.
"Questions must involve real code that you own or maintain. Pseudocode, hypothetical code, or stub code should be replaced by a concrete implementation. Questions seeking an explanation of someone else's code are also off-topic."
One problem should be obvious. The link goes to
which is an HTTP link. It should almost certainly go to
instead. Note that I made two changes:
- Added the missing
meta.codereviewis the old form. They swapped so that they could use a
*.meta.stackexchange.comcertificate for every meta site.
I'm guessing that this isn't the only malformed link in the custom close reasons. They should probably all be verified.
Since the site has moved to HTTPS only, we should make our custom close reasons comply. I believe this is something that only a moderator can do.