Here's What ICANN Says is the .xxx Comments Deadline
 

Here's a copy/paste from ICANN --- rather than chance missing out, I think we all should have our comments in by the end of the day, Wednesday, Sep 22d. Why take the chance that the confirmation email from ICANN gets to you too late the morning of the 23d for confirming before the below ICANN deadline at 11:59 AM PDT?
-------------------------------------

The deadline is listed at the ICANN site as "11:59 a.m. Pacific Daylight time (18:59 UTC) on 23 September 2010".
----------------------------------
Also, since it has the ICANN posting link, AND the already-posted comments link, let me copy/paste here what I included in a thread/post a few days ago at http://www.gofuckyourself.com/showthread.php?t=988183

------------------------------------

"Is The Deck Being Stacked at the ICANN .xxx Comments Link?

Are all of the "supporters" at http://forum.icann.org/lists/xxx-revised-icm-agreement/ really true and direct stakeholders, or are the religious nuts or some other folks or entities stacking the deck against us?

Do you recognize specific .xxx supporters as being legitimate stakeholders from amongst us? If not, please tell ICANN ( and, comment one-way-or-the-other here), AND please post YOUR own comment against .xxx by sending an email to ICANN at [email protected] .

All the comments, both for or against .xxx can be viewed at http://forum.icann.org/lists/xxx-revised-icm-agreement/.

Please protect this Industry by voicing your comments against .xxx. The deadline is listed at the ICANN site as "11:59 a.m. Pacific Daylight time (18:59 UTC) on 23 September 2010". Please submit your BEFORE this coming Thursday.

The opening page at www.freespeechcoalition.com contains useful/helpful info.

OK?"

Take a moment and send in your comments.....Time is running out.

Hurry up, hurry up. Say NO today.... Last chance!

Morning Bump

Bump. Only few hours left

Bump for the next generation. It won't bug me either way ;)

email sent, bump to the top

Lunch Bump

Thanks-----It's appreciated!

to the top

Big bumps.

i lost count on how many i sent. so heres a 1:20pm bump.

only a handful of gfy`ers has send a objection

Big mouths on the boards, thats what most of these trolls spend their time with.

Fuck all those losers who are blind for this.

so send a few more, cause the list is pretty small.
Countless emails is more then 1000 in my world

I sent in my response. I think it's a waste of time at this point since ICANN's decision-making with regards to anything involving money has always been for money, and they stand to profit much on any new extension whether it's popular or not, whether it's detrimental to a particular industry or not. Whatever though...I guess similar to the iStockPhoto shit lately, it's an injustice and I'll always side with justice so may as well do my part whether it will affect me or not (which given shitty adult domain sales lately, probably won't).

Objection message sent and confirmed.

Maybe, just maybe, we'll drive a stake through the vampire's heart this time.

I can't say that I'm all that optimistic though.

Evening bump.

Bump to the top!

to the top.

Today is Thursday in the USA. Hopefully everyone commented.

Dave I want to thank you, as I've seen your threads on different boards, sadly I've been your only bumper on some of them.

Like you mentioned, some in this industry silently support .xxx

one last bump before the deadline is up

bump, historically segregation typically doesn't end up well for the party being segregated. Control and censorship are one in the same.

As of one minute before noon PDT today, ICANN will cut off comments --thanks to those who posted (you are the ones who REALLY have the best interests of everyone at heart).

Thanks for the "bumps" and the support!

I got mine in at the last minute. Sorry about the delay, I kept seeing it on my to do list and not getting it to done. ;)

To be sure that I am clear...the comments are sent by email, correct?

Good luck

Actually, my mail is bouncing. Have tried it twice, with the same results. I am using the same email address that I have used to make comments on this issue before.

Delivery to the following recipient failed permanently:

[email protected]

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 500 Remote server does not support TLS (state 6).