Add an alternative domain about idownvotedbecause

[tzachz]

I'm definitely steeling the suggested "idownvotedbecau.se/nodebugging (didn't downvote)" solution ;)

I comment without downvoting very often, and this issue (mismatch between domain and my actual action/intention) is the only reserve I've had from using this great little site (thanks!)

[NullDev]

---

"I'm not sure how this repo could support two different domains."

Jekyll does indeed not support multiple domains in the CNAME file.
There is a workaround with redirects:

http://rtest.nul.sh/

However, this is unmasked and will just redirect to idownvotedbecau.se
There is another way with masked redirects. But that's not recommended since it will embed the site in a frame. That means all URL's on that site will still point to idownvotedbecau.se/xyz

Example:

http://ltest.nul.sh/

If there's a better solution, I'd provide a domain. Just need some suggestions.

[WillSullivan]

Forum? Forum?? FORUM?!?!?!

I do agree in a way, as I often do the same thing... "idownvotedbecau.se/nodebugging (didn't downvote)" I'm not sure how this repo could support two different domains. But if someone wants to fork and set it up (buy the domain, set up the repo, etc) I'd be willing to help keep them both in sync.

[LindaLawton]

I have the same issue as @WillSullivan I often want to use this when close voting rather than down voting. I used to just leave them a comment, now I use this I feel I actually need to down vote them. I have actually down voted more questions over the last few weeks than i have in years. However when you check the rules I guess i am just to nice and should be down voting more.

However IDownVotedBecou.se just makes sense to me CommonForumMistak.es took me a few minutes to figure out what this meant. I think we can come up with a better non-downvote acronym.

IMayHaveDownVotedBecou.se ?
ImprovmentSugestios.info

I don't recommend redirects. You're just going to add an additional attack vector in the chain. If the domain is expired or hacked, an attacker can redirect users without the author's knowledge. Also, that's another SSL certificate you have to deal with.

I recommend using CloudFlare like I did in #51 with a "forwarding url" page rule. Incidentally, this will also solve your SSL problem.