Return to tldapps Forum - Message Thread - FAQ
Username: |
markusbaccus |
Date/Time: |
Tue, October 24, 2000 at 7:46 PM GMT |
Browser: |
Microsoft Internet Explorer V5.01 using Windows 95 |
Score: |
5 |
Subject: |
a voluntary association: ".kids" is ok, but a mandatory ".xxx" is not. |
Message: |
|
There is a strong distinction between a ".kids" and ".sex/.xxx"
TLD. Consider this example: You are a merchant who sells to children.
The town mayor comes to you and says: "Hey- we are opening up a new public mall which
caters to kids in the neighborhood, would you like some floorspace there? You
can use it to augment what you have built up here." Now imagine you are a merchant
who caters to adults as a member of the porn industry. (that's right- your
a porn king). The mayor comes to you and says: "You know we have this
new zoned area for adult bookstores and bars in the neighborhood, and we want you
to move your operation there. I know you have a lot of out-of-town customers
who have been coming here for five years, but the city council is considering making
this mandatory, so if I were you I would get a good spot in the adult zone while
you still can."In other words, a ".kids" TLD would be a voluntary association
with a group of speakers who meet minimal qualifications. For example, an educational
institution is not *required* to get a ".edu" domain, [as it could get a ".com",
".org" or ".net" domain], but the institution might *choose* a ".edu" domain in order
that others can find the site more easily. Similarly, anyone who is willing
to aim appropriate content at kids during saturday morning T.V. is free to do so
if they choose to do so. A ".kids" area is analogous to this choice.
It would be an area which many (of those who want to speak to children) would find
desirable to be involved in, merely because it would most likely create a "parent
approved", safe haven for children's content without the need for untrustworthy,
draconian content filters. It would empower parents to restrict their child's
access to a part of the web which they know meets certain minimum standards.
(Currently, those standards would include the recent U.S. law regarding marketing
to minors, as well as a ban on the usual suspects, such as pornography, drugs, etc.)
Different variants of the TLD could be used to resolve differences in national
child protection laws, such as ".uskid", ".ukkid", etc. On the other hand, a ".xxx/.sex"
TLD is a very dangerous idea. It would create a ghetto which many speakers
would be reluctant to relocate to because of the significant stigma associated with
the adult pornography business. Furthermore, many of those speakers would be
rightfully reluctant to be forced to abandon a ".com" which they have built up over
the last five years. Finally, there is the distinct possibility that different
governments would seek to make the scheme mandatory. Once tolerated, the
principle could readily spread to areas which were never intended, such as ".hate",
or ".politics", or ".satire". All in the name of saving the children from the
usual amorphous suspects: Incitors of Terrorist acts, Child porn, hate speech,
drug pushers, nuns who bet on sunday, etc. (Won't someone pleeeeze think of
the CHild-ren!!!) Perhaps one day you might recieve a nasty email, saying
in effect that you have drawn the great displeasure of his Excellency, the Potentate
of Kraplapistan, and that you must remove all discussion of your hemp-based fertilizer
from your site as it conflicts with the sovereign drug laws of the Republic of Kraplapistan
and impermissably burdens the budding Republic's number one export: hormone enhanced
bovine excrement. Or as here, someone writes a webmaster demanding that all
insulting or satirical posts be removed or else they will sue to force this entire
site into the ".satire" domain. This is just the latest example of ICANN
presenting ideas which are fundamentally dangerous to our freedom. No American
should cow-tow to some dictator's idea of what constitute's appropriate content,
let alone some agency of the Clinton Administration. Stop purveying these poorly
thought out "solutions" to non-existent problems, hire some decent constitutional
scholars to provide some expertise in the proper role and mechanisms of would-be
government, and leave the one-world socialism to Chairman Lenin's ghost.
|
| |
Message Thread:
- .biz, etc. Application by Abacus America, Inc. Moderator, October 7 @ 10:37 PM (50/100)
- Whatever happenned to the dot shops chrisn, December 16 @ 1:22 PM (0/0)
- ABACUS - Great Concept ak, November 6 @ 12:26 AM (0/0)
- USA families mikes, November 6 @ 12:00 AM (0/0)
- yes to FAM henry, November 5 @ 11:52 PM (0/0)
- .fam andyG, November 5 @ 11:44 PM (0/0)
- Out of 200 proposed TLDs only one is COOL kevinY , November 5 @ 11:29 PM (0/0)
- .cool kevinY , November 5 @ 11:20 PM (0/0)
- Family JamesZ , November 5 @ 11:14 PM (0/0)
- I Agree (.FAM and .XXX) tw, November 5 @ 10:36 PM (0/0)
- Families need .FAM sl, November 5 @ 10:22 PM (0/0)
- support for .COOL tn, November 5 @ 9:29 PM (1/1)
- .COOL great idea AFree , November 5 @ 9:21 PM (1/1)
- This is the only application that can reach profitability within the first month - HOW? griffiths, November 5 @ 6:07 PM (0/0)
- IOD issue useyourhead, November 5 @ 6:47 AM (0/0)
- .cool will just be a fad YankeeFan, November 3 @ 3:31 AM (2/2)
- .XXX a poor idea ipguy, November 3 @ 12:10 AM (0/0)
- Does Pedro work for Abacus? YankeeFan, November 1 @ 8:03 AM (3/8)
- Abacus got it right pedro, November 1 @ 4:26 AM (0/0)
- Yes to .FAM AndrewK , October 31 @ 9:42 PM (0/0)
- Why Abacus for .biz ChrisK , October 31 @ 9:00 PM (0/0)
- About dot .biz and .inc dimitrov@mailcity.com, October 31 @ 7:44 AM (0/0)
- MSNBC.com Pole domainking, October 31 @ 12:38 AM (0/0)
- .COOL domainking, October 30 @ 11:50 PM (0/0)
- Trying to be cool nickl, October 27 @ 10:01 PM (0/0)
- cool jamesh, October 27 @ 7:31 PM (1/1)
- .fam mikeS, October 27 @ 1:06 AM (0/0)
- It is very important for ICANN to be fair to the public alexj, October 26 @ 8:04 PM (0/0)
- To: saynotoabacus useyourhead, October 26 @ 5:44 AM (0/0)
- EXPERIENCE WITH ABACUS, INC. vldiaz, October 26 @ 3:07 AM (0/0)
- Abacus App peniel, October 25 @ 10:54 PM (0/0)
- I like .cool ChrisK , October 25 @ 8:10 PM (0/0)
- Different policies for ".biz" portion Josh Kyle, October 24 @ 6:57 PM (1/1)
- Anyone know who else has it ready to go? useyourhead, October 23 @ 5:58 AM (1/9)
- .xxx MikeS, October 22 @ 10:31 PM (2/2)
- .Sex TLD Satori, October 25 @ 8:46 PM (0/0)
- a voluntary association: ".kids" is ok, but a mandatory ".xxx" is not. markusbaccus, October 24 @ 7:46 PM (0/0)
- Young people nickl, October 22 @ 1:19 AM (0/0)
- I agree with jandl bizEXISTSalready, October 22 @ 1:05 AM (0/0)
- BID SYSTEM UNFAIR to UNRICH stokdoctor, October 21 @ 10:32 PM (2/2)
- Sorry for the excessive use of exclamation marks. My only intent was to draw your attention to SayNoToAbacus, October 21 @ 12:11 AM (1/1)
- WWW.NAMES4EVER.COM Domainking, October 20 @ 7:35 PM (2/2)
- To saynotoabacus use your head, October 20 @ 6:11 AM (0/0)
- .biz A. Kinney, October 19 @ 4:48 PM (1/1)
- Comments sjk, October 19 @ 7:26 AM (0/0)
- Way to go Abacus! use your head, October 19 @ 6:19 AM (1/4)
- Proposition to ICANN, Applicants & Internet Community Pistoff, October 18 @ 5:45 PM (0/0)
- Abacus is trying to BUY your support!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! SayNoToAbacus, October 17 @ 9:22 AM (1/1)
- We want to see your application emc2, October 17 @ 3:16 AM (0/0)
- .fam is needed dconder, October 16 @ 9:11 PM (1/10)
- Simply unworkable jandl, October 16 @ 12:41 AM (0/0)
- .BIZ applications korskarn, October 15 @ 4:43 PM (2/4)
- Where is your application? jandl, October 14 @ 7:55 PM (0/0)
Privacy Policy | Terms of Service | Cookies Policy