Adult Apps and an organisational idea

[Andy W]

Recent discussions about adult apps, censorship and the risk of it
potentially being applied to religious agendas has got me thinking.

My own position is not to censor adult apps, but somehow break them
off into a specific sub-group, both to make it easy to exclude them
from searches and listings if appropriate (and opting-in to such
listings would take an age-disclaimer, etc.), as well as avoid being
an arbiter of taste.

While I don’t want any device I give my child to be able to access
such apps, I don’t wish to stop any consenting adult ‘enjoying’ any
such material that is legal in their country. (And cross-country
considerations would have a huge bearing on any level of censorship,
of course.)

One possible solution is to sub-categorise domains in instances like
this. For example.

bum.xxx.app
hairybitch.xxx.app
redheadedsluts.xxx.app

as a pose to:

bum.social.app (homeless people)
hairybitch.animal.app (long-haired female dogs)
redheadedslats.diy.app (wooden slats tipped with veneers made from
redwood; yeah, struggling here…)

This would also instantly open up the namespace for repeats of semi-
generic names—one in each category—as well as circumventing very
generic registrations for things like ‘social’, ‘animal’ and ‘diy’,
which are the prime targets for squatters.

One could go further and include app platforms or company names in the
sub-domains where there is demand for it. Subdomains could even be
cheaper then ‘top-level’ domains, or have lesser demands on
eligibility.

Thoughts?

Andy W

[Daniel Mühlbachler]

IMO, your idea seens good but somehow it doesn't really make sense
regarding the purpose if a 'domain'. If I purchase a domain, I
normally want to purchase a 'top-level' one which makes also sense
when using an own mail server and dns server and subdomains. With
subdomains those parts will be harder to configure, doesn't really
look good or hard to maintain.
However, maybe it would be an option for individuals. I mean, cheap
subdomains with no features. A simple interface for configuring a
standard dns. Those individuals may use free hosting services for
theor website and very cheap subdomains would be a great enhancement
for them and would fit in the view of the rules.

[Andy Warwick]

I don’t know; I”m happy to purchase a ‘co.uk’ domain for my business,
which strictly speaking isn’t a top-level domain.

And a ‘gov.uk’ certainly isn’t open to me as either a company or individual.

I am seeing this proposal in a similar light, as well as being one
easy way to segregate adult domains that would then be trivial to
filter out.

Cheers

Andy W

2011/7/16 Daniel Mühlbachler <daniel.mueh...@gmail.com>:

--
Andy Warwick

[Daniel Mühlbachler]

OK, as I'm from Austria I haven't ever dealt with uk domains and their
purchase 'options' but I agree that this would be an easy way to
segregate those domains from 'normal' ones.
However, maybe it would be better to make a poll when we've reached a
huge amount of members b/c adult domains are always a case which
should be treat with merit (at least in the case of age
restrictions!).
However, I also agree that there are some apps that may lead to adult
content for some people (like the kamasutra apps) but imo they should
be allowed b/c they are even available in the Apple AppStore. In that
case I think xxx.app would be a good practice but to segregate in more
subdomains may be confising when searching an app or so because there
would be more apps with the same domain/name.

On 16 Jul., 22:09, Andy Warwick <andy.warw...@gmail.com> wrote:
> I don’t know; I”m happy to purchase a ‘co.uk’ domain for my business,
> which strictly speaking isn’t a top-level domain.
>
> And a ‘gov.uk’ certainly isn’t open to me as either a company or individual.
>
> I am seeing this proposal in a similar light, as well as being one
> easy way to segregate adult domains that would then be trivial to
> filter out.
>
> Cheers
>
> Andy W
>

> 2011/7/16 Daniel Mühlbachler <daniel.muehlbachlerd...@gmail.com>:

[Matthew Baxter-Reynolds]

Next week we should be in a position to present an interactive "policy database" on the site. This will contain three items:

a) Domains which are offensive in language will be not allowed.
b) Domains which incite or celebrate hatred will not be allowed.
c) Adult/pornographic domains will be located under their own .xxx.app subdomain.

I would propose that we stop the discussion on this forum as it is going round and round. That's not to say that it's not a useful contribution, but it is hard to turn this prosaic discussion into something that we can use as a basis of properly informed decisions.

The policy database will allow anyone to comment and allow anyone to up-vote or down-vote comments, as well as boost or reduce the importance of individual policy items.

PS: With regards to "a", no I don't know how to square words that are offensive in language "a" and not in language "b". Some thoughts on this would be appreciated.