# Two Click Rule **URL:** \ **Category:** About This Message Board\ **Created:** [September 12, 2008, 6:51pm UTC](https://boards.straightdope.com/t/two-click-rule/463319 "2008-09-12T18:51:56Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![SiXSwordS](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@SiXSwordS](https://boards.straightdope.com/u/SiXSwordS)\ **Post date:** [September 12, 2008, 6:51pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/1 "2008-09-12T18:51:56Z")
I’m not so much interested in the rule itself, but how to pull it off. Let’s say I want to post a picture and I’m not sure if it needs to follow the two click rule. Assuming I want to err on the side of caution, how would I follow this rule? Specifically, how do I make it so that one has to click the link then click again after seeing some type of warning? FTR, I would have searched for some answers if I could have. ---
**Author:** ![Duckster](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/duckster/32/1244_2.png) [@Duckster](https://boards.straightdope.com/u/Duckster)\ **Post date:** [September 12, 2008, 8:03pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/2 "2008-09-12T20:03:06Z")
If a two-click process is not possible, make sure you have an easily identifiable disclaimer warning in your post followed a broken link. Here’s an example not to do (using a safe image): “Oooo baby, check out this pussycat” —\> [http://www.catfacts.org/cat-mouth-full.jpg](http://www.catfacts.org/cat-mouth-full.jpg) In the above example, there was no warning and the link was direct. The better solution is to add in a warning and break the link. Like this: “Oooo baby, check out this pussycat” (NSFW Warning) —\> http:/ /www.catfacts.org/cat-mouth-full.jpg Notice the warning message and the broken link? Also, before you post, look at the **Additional Options** area on the page before you post. Under **Miscellaneous Options** uncheck the box marked, **Automatically parse links in text**. Do this for any NSFW link, images, web pages or whatever. And always, always, always, preview such a post before hitting the submit button. ---
**Author:** ![Gfactor](https://avatars.discourse-cdn.com/v4/letter/g/9de053/32.png) [@Gfactor](https://boards.straightdope.com/u/Gfactor)\ **Post date:** [September 12, 2008, 8:16pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/3 "2008-09-12T20:16:54Z")
> [@Duckster](#): > > Also, before you post, look at the **Additional Options** area on the page before you post. Under **Miscellaneous Options** uncheck the box marked, **Automatically parse links in text**. > > Do this for any NSFW link, images, web pages or whatever. And always, always, always, preview such a post before hitting the submit button. We generally accept this method. But there is a downside to it. Duckster posts an unparsed link: [http://www.patrobertson.com/](http://www.patrobertson.com/) unparsed continued in next post. ---
**Author:** ![Gfactor](https://avatars.discourse-cdn.com/v4/letter/g/9de053/32.png) [@Gfactor](https://boards.straightdope.com/u/Gfactor)\ **Post date:** [September 12, 2008, 8:21pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/4 "2008-09-12T20:21:17Z")
and I quote it: > [@Gfactor](#): > > We generally accept this method. But there is a downside to it. Duckster posts an unparsed link: [http://www.patrobertson.com/](http://www.patrobertson.com/) > > unparsed > > continued in next post. It turns into a live link. A good trick is to bold a portion of the link: bolded first letter ------\> **h** ttp://www.patrobertson.com/ continued on next post. ---
**Author:** ![SiXSwordS](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@SiXSwordS](https://boards.straightdope.com/u/SiXSwordS)\ **Post date:** [September 12, 2008, 8:24pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/5 "2008-09-12T20:24:04Z")
So [this](http:/ /media.ebaumsworld.com/picture/JacYodac/NastyChildren.png) would be okay because the link is broken? (SFW, but a little gross and possibly politically abrasive.) Same pic, but maybe a better way of breaking the link? [media.ebaumsworld.com/picture/JacYodac/NastyChildren.png](http://media.ebaumsworld.com/picture/JacYodac/NastyChildren.png) ---
**Author:** ![SiXSwordS](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@SiXSwordS](https://boards.straightdope.com/u/SiXSwordS)\ **Post date:** [September 12, 2008, 8:25pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/6 "2008-09-12T20:25:34Z")
What happened to **GFactors** reply? ---
**Author:** ![Gfactor](https://avatars.discourse-cdn.com/v4/letter/g/9de053/32.png) [@Gfactor](https://boards.straightdope.com/u/Gfactor)\ **Post date:** [September 12, 2008, 8:28pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/7 "2008-09-12T20:28:26Z")
> [@SiXSwordS](#): > > What happened to **GFactors** reply? I deleted it. ---
**Author:** ![SiXSwordS](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@SiXSwordS](https://boards.straightdope.com/u/SiXSwordS)\ **Post date:** [September 12, 2008, 8:31pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/8 "2008-09-12T20:31:23Z")
weird ---
**Author:** ![samclem](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@samclem](https://boards.straightdope.com/u/samclem)\ **Post date:** [September 12, 2008, 8:34pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/9 "2008-09-12T20:34:58Z")
> [@Gfactor](#): > > I deleted it. Killing it _once_ wasn’t enough? 🙂 ---
**Author:** ![Gfactor](https://avatars.discourse-cdn.com/v4/letter/g/9de053/32.png) [@Gfactor](https://boards.straightdope.com/u/Gfactor)\ **Post date:** [September 12, 2008, 8:36pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/10 "2008-09-12T20:36:42Z")
> [@SiXSwordS](#): > > So [this](http:/ /media.ebaumsworld.com/picture/JacYodac/NastyChildren.png) would be okay because the link is broken? (SFW, but a little gross and possibly politically abrasive.) > > Same pic, but maybe a better way of breaking the link? [media.ebaumsworld.com/picture/JacYodac/NastyChildren.png](http://media.ebaumsworld.com/picture/JacYodac/NastyChildren.png) Yes. Those are both acceptable. > [@](#): > > Killing it once wasn’t enough? It was spreading. ---
**Author:** ![rowrrbazzle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rowrrbazzle/32/414_2.png) [@rowrrbazzle](https://boards.straightdope.com/u/rowrrbazzle)\ **Post date:** [September 12, 2008, 9:18pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/11 "2008-09-12T21:18:16Z")
The new [noparse][noparse][/noparse] code can be used. Coding [noparse][noparse][http://www.google.com](http://www.google.com)[/n[/noparse]oparse] gives [noparse][http://www.google.com](http://www.google.com)[/noparse] ---
**Author:** ![Gfactor](https://avatars.discourse-cdn.com/v4/letter/g/9de053/32.png) [@Gfactor](https://boards.straightdope.com/u/Gfactor)\ **Post date:** [September 12, 2008, 9:35pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/12 "2008-09-12T21:35:55Z")
> [@rowrrbazzle](#): > > The new [noparse][noparse][/noparse] code can be used. > > Coding > [noparse][noparse][http://www.google.com](http://www.google.com)[/noparse][/noparse] > gives > [noparse][http://www.google.com](http://www.google.com)[/noparse] Cool. Thanks. ---
**Author:** ![SiXSwordS](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@SiXSwordS](https://boards.straightdope.com/u/SiXSwordS)\ **Post date:** [September 12, 2008, 9:37pm UTC](https://boards.straightdope.com/t/two-click-rule/463319/13 "2008-09-12T21:37:27Z")
[[noparse]How About this?[/noparse]](http://thewrongband.com/kewl.jpg) [noparse][http://thewrongband.com/kewl.jpg[/noparse]](http://thewrongband.com/kewl.jpg%5B/noparse%5D) ---
**Author:** ![Chronos](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chronos/32/134_2.png) [@Chronos](https://boards.straightdope.com/u/Chronos)\ **Post date:** [September 13, 2008, 2:35am UTC](https://boards.straightdope.com/t/two-click-rule/463319/14 "2008-09-13T02:35:53Z")
> [@rowrrbazzle](#): > > The new [noparse][noparse][/noparse] code can be used. > > Coding > [noparse][noparse][http://www.google.com](http://www.google.com)[/n[/noparse]oparse] > gives > [noparse][http://www.google.com](http://www.google.com)[/noparse] Let’s see, does that work for quoting?