![]() |
Quote:
Mark . . . how many times are you going to say this, and how many times do I have to ask you what makes you think ASACP would even entertain the notion of doing something to "lobby" for the adult industry? That is not their job, it is not what they do. Why you think they have some obligation to us is beyond me. I suggest you have someone read and explain their mission statement to you as you obviously don't get it. |
Fuck .xxx!
Choker rules! |
Quote:
Tony . . . I have an agenda here, I will admit it. #1. We tell the advisory council to instruct Joan to contact FSC, because it is her position that she can't do it without being told to do so by them (even though she had no problem making the comment in the first place). #2. They do it, and Joan contacts the FSC and the retraction process begins, and we become avid supporters of ASACP. or #3. The ignore our request and then any support we may have had for ASACP goes right down the toilet, and they can say good-bye to any donations or support from the community . . . and I show you guys what I used to do for fun when I was kid. |
Quote:
thanks for playing. |
Quote:
|
The US government will require .xxx and it will stand up in court just as soon as those filthy romance novels you see in the grocery store all have plain red covers on them.
|
ASACP's support of .xxx angers me. I'll never contribute a dime to them at any time in the future, unless they lose their ignorant stance on the TLD.
|
Quote:
|
Quote:
Adult Sites Against Child Porn to Association of Sites Advocating Child Protection What? Are "adult sites" not "PC" enough for you? Fuck that! Don't expect our support if you're ashamed of us. Fuck you. |
bump for the night shift
|
50 people wating for a retraction
|
*waiting even
|
Throughout all of the discussions on dot XXX, there has been no proof brought to bear that such a domain would actually do anything to help protect children.
In order for ASACP to remain true to its goals and continue to uphold its mission of protecting children, I believe ASACP should make abundantly clear, by whatever means necessary, its position that dot XXX does nothing to further the advancement of protecting children from online adult material, despite whatever was initially claimed, and furthermore, should rescind any previous support, implied or overt, of dot XXX. |
Quote:
Al, this is why they are using Joan's applause as evidence of industry support. |
Quote:
:banana :GFYBand :banana |
Quote:
Thank you, and it was a pleasure seeing you again |
Quote:
nonono... thank you :thumbsup |
Quote:
People keep mentioning how we do need to police ourselves, and censor ourselves for many different reasons. If things keep coming up that will spilt up the adult industry into groups it will become a lot easier for the people against us to pick us apart. Sure we can police ourselves, but what does having a .com, .net, .jp, .co.uk or anything else have to do with it. I've said it once and now I am saying it twice. ASACP needs to make this situation right, they need to contact the FSC and anyone else needed and take a stance that this is not what is best for anyone. I would really also like someone to not only explain to me, but also convince me as to how having .xxx on my domains will help stop CP. If my site switches to .xxx that means Pedo's will be more scared to put CP on the net? Please explain this to me so I understand the real benefit. |
I don't think webmasters should support ASACP until they start supporting us.
The vast majority of people in this industry are against .xxx and if ASACP wants the financial support of that vast majority they should rescind any implied support for a .xxx TLD and join with the FSC in fighting against it. :2 cents: |
Quote:
|
If you support .xxx you are looking for trouble in your own business. It's simple as that. It doesn't fight CP and it's just a mean of censorship and possible source of profit for certain operations. I don't know many things about ASACP, I recognize their efforts, but I'm sceptical regarding their involvement. xxx domains can be the basis of several types of attacks against the adult industry and makes me wonder why some people haven't seen it yet.
|
Quote:
My point is the entire way the .xxx thing is going is incorrect. Yes yes... The ASACP should not have a fuck all to do with Protecting the industry and only concentrate on irradicating CP within it, thats fine. What the fuck ever dude... Regardless my point is organizations that are supposedly recieving monies from .xxx are not on a mission statement to protect our industry. THATS KINDA FUCKED UP IMHO. .XXX is a vote. Part of the money from that vote must go towards defending our industry. |
Quote:
what the hell does that mean? .xxx is a vote? |
Quote:
Buying a domain is "Support" towards our industry going into .xxx. Play it out in your head. Thats where everyone will end up going, by force without protections should .xxx go into effect. Every penny of it should goto preserving and protecting the industry, not wallets. |
Quote:
They used to be against illegal child porn, which was a good thing to be against. With the new direction, are they trying to be the morality police for the adult industry instead of spending their time fighting child porn? |
I can't remember. Did I bump this thread already? :banana
|
Quote:
ICANN oficially approved .xxx 10 days ago and entered now the final negotiations with their registry and .xxx is expected to go live in about 6-9 months :( |
Quote:
Please see my earlier post for full details. Here is a bit of back story. This is not just a theoretical concern. Back in 2000, before Lawley got involved as president, ICM Registry applied to run the .xxx domain. But ICANN shot down the proposal. It didn't take Congress long to get involved. At a hearing in February 2001, Rep. Fred Upton, R-Mich., demanded to know why ICANN didn't approve .xxx "as a means of protecting our kids from the awful, awful filth which is sometimes widespread on the Internet." Sen. Joseph Lieberman, D-Conn., griped to a federal commission that .xxx was necessary to force adult Webmasters to "abide by the same standard as the proprietor of an X-rated movie theater." |
too important to risk hitting page 2
|
.xxx is badddd
|
Quote:
|
Quote:
|
I think .xxx would be a good idea if done right.
But so far its not being done right at all. Its a money grab this time around like it has been before. I have a novel idea, how about an industry extension that preserves and protects this industries freedom of speech. .xxx would fuel those protections with a lobby and representation like every other normal industry instead of the line pockets of a mysterious group of people whom obvious do not give a mother fuck about this biz. |
Bump.
Because there are alot of fucken morons that do not give a fuck about this business and push this important thread down with the, "My cock is huge" is threads. Wake up dumb assholes our industry is on the line here. |
bump
along with a reminder... baddog's post is about urging ASACP to rescind any support of dot XXX it may have previously put forth. IMO, discussions on the merits of dot XXX deserve their own thread. |
Quote:
A round table needs to be made on how .xxx should be executed if at all. |
Quote:
Share with us the right way. :) |
Quote:
We really are a pathetic bunch. We sit with our thumbs up our asses for 9 months until the new 2257 regs are actually announced and then suddenly - mainly because there is no other option - most of us convince ourselves that FSC is going to solve all our problems. Hopefully that faith isn't misplaced, but in reality hardly anyone had even heard of FSC until a couple of weeks ago, knows anything about them, just how competent their team may be, or - except in the broadest terms - what are their aims. I have noticed that for an organization claiming to represent the whole adult industry and admitting they haven't paid much attention to the online sector in the past, FSC is still most noticeable by its almost complete absence from adult online community resources, such as boards like this. Still, if it all goes pear-shaped, it won't be our fault for failing to get organized. We backed FSC didn't we... And we are handling the XXX TLD issue the same way. It's not new, but we didn't even get around to posting a few messages on the boards until everything was all but signed and sealed. Oh except that like the Acacia issue, this one also has people sacrificing industry interests for their own short-term gain. And we look like we are shaping up to make ASCAP the scapegoat as we did Matrix Content in relation to Acacia, while turning a blind eye to all the industry "heroes" who behaved just as badly. Is that a banner advertising XXX pre-registration I see at the top of GFY? |
Anyone who knows me knows my position. At Cybernet Expo I publicily called for ASACP to rescind its support of .XXX and write a strongly worded letter of opposition. Other than for money, the organization has no business supporting .XXX because it does nothing to protect children. That should be the end of it, as far as ASACP is concerned. Like Mike expressed earlier, I also feel sorry for Joan because I don't think she made the final decision to send out that letter of support. And now that it's out there she's left defending it and trying to pretend that it's a "neutral" letter when clearly it is not neutral. I also know that if I was on the Advisory Council I would be absolutely PISSED about that letter, since I don't think the Council wanted a letter of support to be sent out... it looks like someone else made that decision and hoped to get away with it.
ASACP has a CLEAR opportunity here to do the right thing. We all heard Joan in San Diego say that if the Advisory Council tells her to write a letter of opposition then she will be required to do so. The Advisory Council should put that to the test.... give Joan the instruction she needs to do the right thing, and if she STILL doesn't do it or else writes some confusing and vague letter that can be read in 10 different ways then the members of the Council should think long and hard about why they are volunteering their time with this organization, and who is REALLY pulling the strings. I would like to be supportive of ASACP, but their position on .XXX and their failure to do the right thing here makes it difficult. |
i dont support .xxx
|
All times are GMT -7. The time now is 10:57 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc