Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] [VOTE] vote for .box

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] [VOTE] vote for .box


Chronological Thread 
  • From: Dominique Rehborn <dominique AT boxnet.eu>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] [VOTE] vote for .box
  • Date: Tue, 16 Aug 2011 18:08:49 +0200
  • List-archive: <http://lists.darkdna.net/pipermail/discuss>
  • List-id: <discuss.lists.opennicproject.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 08/16/2011 05:45 PM, mike wrote:
> On 11-08-16 10:41 AM, mike wrote: [clip]
>> Prohibited contents and behavior
> [/clip]
>
> I guess in the larger picture, I have to ask myself, where does the
> responsibility for content censorship rest? If you where to ask me,
> I would answer that it rests primarily with the observer, it's just
> common sense, if it offends you, then don't look at it.
would you dare to official include things like child porn and rape to
your "don't look at it" statement?
common sense is a good point since not all, but the overall majority has
it, thus make law and rule based on what most people think is right, not
the individual for himself.
>
> However I don't want to digress into a whole philosophical discussion
> on content censorship, but simply put, I'm not entirely convinced
> that the NIC is the right place to be attempting to enforce content
> censorship in the first place.
i don't see why we shouldn't enforce policies. it's not censorship, it
is a restriction for the usage of a TLD. this would for example mean you
could do as a search engine requests/filter per TLD basis and know which
contents you can expect or even not.
again, if there is a huge market excluded, like porn, then there should
be a .porn TLD.
>
> --Mike _______________________________________________ discuss
> mailing list discuss AT lists.opennicproject.org
> http://lists.darkdna.net/mailman/listinfo/discuss

- --
Dominique Rehborn - dominique AT boxnet.eu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5KlhEACgkQLPJ0YA88bG4wVwCcDpYBhJVv6yx//yKgH2ZUEp2s
VhcAn2PMFq3e7/zq/su257wUp7Tz/DbT
=Id8l
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.19.

Top of Page