After Settlement, Gay Users Will Finally Be Able to Use ChristianMingle.com July 2, 2016

After Settlement, Gay Users Will Finally Be Able to Use ChristianMingle.com

Congratulations, gay Christians! You can finally meet each other. (Assuming you haven’t already moved on to every other dating website in the world.)

Under California law, all businesses must provide “full and equal accommodations” to customers no matter their sexual orientation… which was a problem for ChristianMingle.com since that site only gave users two options: Either you were a “man seeking a woman” or vice versa.

ChristianMingleOptions

Two gay plaintiffs sued the dating site’s parent company in 2013 and their settlement is now final. ChristianMingle.com promises to ask only if users are male or female — something Archive.com shows they’ve done since February of 2015, perhaps as a result of this case, though the parent company says they’ll continue to work on creating a more helpful site for gay customers. In addition, the website’s owners will pay the plaintiffs $9,000 each, in addition to forking over $450,000 to cover their legal fees.

“I am gratified that we were able to work with [parent company] Spark to help ensure that people can fully participate in all the diverse market places that make our country so special, regardless of their sexual orientation,” one of the lead plaintiffs’ attorneys, Vineet Dubey of Custodio & Dubey LLP, said in a statement.

A representative of Spark Networks said the company was “pleased to resolve this litigation.”

That means men will soon be able to wear this t-shirt without a hint of irony:

ra,unisex_tshirt,x3104,fafafa-ca443f4786,front-c,650,630,900,975-bg,f8f8f8

Thanks, Jesus!

(via Joe. My. God.)

"The way republican politics are going these days, that means the winner is worse than ..."

It’s Moving Day for the Friendly ..."
"It would have been more convincing if he used then rather than than."

It’s Moving Day for the Friendly ..."

Browse Our Archives

What Are Your Thoughts?leave a comment
error: Content is protected !!