In the “How to Format” bar that shows when editing the body of a question or editing an answer, there is this example for how to format:

<a href="http://foo.com">foo</a>

There is a problem with this: foo.com is a site that is owned by someone currently and has links to a bunch of ads. It could be sold to a malicious company and is linked in the Network's guidance. Also, it is a bad example in another way: it's not on HTTPS and thus not secure.

It should be replaced with https://example.com, which is a site that is set aside exclusively for being used as a random example website in cases like this.

There is also a related problem: in the help linked to in the formatting bar, there are examples that use insecure HTTP in the links, not HTTPS. Sites like https://google.com and https://yahoo.com support secure HTTPS, and the examples should show this; they should set an, ahem, example for using HTTPS in links if possible.

  • @sonic codeblocks mess up screen readers. I used s bunch of tags to show the code as it looks, using a workaround with random HTML tags. – Stormblessed May 6 at 20:00
  • 2
    But said workaround is unsupported, and is likely to go wrong in case changes are made to the Markdown renderer; for instance, if the system decides to strip off things that it's currently not doing. (I'm using the SOUP user script, which warns you in case you're using unsupported HTML; it threw a warning for this post.) – Sonic the Anonymous WizHog May 6 at 20:02
  • "I used a bunch of tags to show the code as it looks" ... Then why not use code formatting directly? That text isn't indented to read directly anyway – muru May 7 at 9:02
  • Also discussed on SO Meta: meta.stackoverflow.com/questions/357855/… – m69 May 8 at 7:51
  • @JNat you can mark this status-completed :-) – Stormblessed Aug 14 at 4:07
  • I'm still making sure we're not missing any relevant place, as per Tim's answer, @Stormblessed, before doing that ;) – JNat Aug 14 at 8:00

Yes, we need to set a better example (I'm here all week).

This includes stuff found in:

  • Individual per-site settings
  • Transifex for the international sites
  • The help center (I believe a few have custom overrides we have to check)
  • Baked-in stuff, including posts

The guidance needs to be changed specifically to point to example.com, with guidance on using HTTPS.

I don't have a timeframe, but it's now on the backlog board of curation things that we've been doing a pretty good job of chipping away at monthly.

Will update when done. I coulda sworn we addressed this on a large scale previously some years back, but we never quite got out of discussing logistics about it. Anyway, we'll get it done.

  • By "Baked-in stuff, including posts", do you mean the How to Format bar? – Stormblessed May 11 at 17:30
  • Yes, that's what Tim meant :) – JNat Jul 3 at 12:26

"It is done" — Elspeth

It has been changed to https://example.com in the example

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .