Sure, there's ethical problems. Look up the horrible little flick called "Parts: the Clonus Horror" http://imdb.com/title/tt0078062/ summarized "Politicians scheme to clone themselves, assuring immortal life". They grow the bodies to optimum physical health then freeze them until the "original" needs a transplanted organ. Of course you've functionally killed a person with a complete personality to do it. Far worse than stem cell research in almost anybody's book.
There was a movie with almost this exact premise, I think it was called "Clonus". They cloned important people, grew their clones to the height of physical health then put them on ice until the original needed a body part, IE a heart, kidney etc. Then they would harvest the organ, for a perfect match and no immunological response. It was kinda bad sci-fi but got into the details of the ethical quagmire.
An adendum - I hit Submit too fast. MS-DNS works properly for full Class C DNS zones with all the tools, but for sub-Class C zones it breaks Dig. NSLookup and Host still work fine. I got into an argument with the AOL folks because I was able to do lookups all day long - using NSLookup. As soon as I tried Dig (which is apparently what AOL uses to do reverse lookups) I realized something was amiss. That's what I meant to say.
Actually, I just went through this with AOL last week. It can be a touch more complicated than checking that checkbox. I have 1/2 a Class C address space - and MS-DNS standard PTRs only work for NSLOOKUP and HOST requests. They do not work for DIG requests!
How did I find this out? Even though I had PTRs set up, AOL was still rejecting my mail. If one has less than a Class C then one must create subnetted PTRS, i.e. one must make a subfolder in the reverse DNS zone and put the PTRs there. This apparently must be done manually, the checkbox that creates the PTR for you doesn't do it automagically (unless I've missed something).
Once this is done, then Dig will work correctly and AOL will accept your mail.
MacDowells serving Big Mic's? yaho.com running a search engine? Revoke their business licences, or throw the creeps in jail. This isn't a bad practice of porn sites, this is a bad practice.
And yet the Supreme Court just ruled (I believe 8-1) in favor of Victor's Little Secret, a small "adult novelty" (ie sex toy) store which was sued by Victoria's Secret as diluting their trademark... does this go over the line as far as you're concerned?
Fascinating... I've used a product called Spamnet from Cloudmark, which uses the same methodology but for spam. So, being interested in such an addin I fell for the trick and went to tubgirl site, which I wouldn't recommend for anyone who has a weak stomach. Suffice to say, there is a girl and a tub, and it's disgusting to say the least. Thanks to technos for your outrageous demonstration of not-truly-deceptive site naming.
I am a proponent of free speech, and I tend to agree with the overall view that it would be nice if something could be done to control the situation without preventing anyone from excercising their free speech rights. I also agree unfortunately that there is no porposed solution that I've seen that is at all workable.
Of course, if everybody played nice in the sandbox, the concept of a.xxx or.sex TLD would work fine. I still think that "responsible" pr0n companies could voluntarily use such a TLD and gain some form of respectability or credibility from doing so.
Well, I for one hate to reinvent the wheel. In my previous incarnation I was a programmer who among other things did extensive customization to accounting software to meet the needs of my customers.
I used a product called Accountmate which is written in Visual FoxPro and offers a "source code license" should you want to modify the product. Check this link for their current license agreement:
http://www.accountmate.com/solutions/files/liscens e_agree.pdf
I haven't read it (not having dealt with coding for several years) but I think this might provide you a valuable point of reference to create your own terms.
This wouldn't fly, because it didn't in the past. As usual, there really aren't new ideas, just new consumers of the old ones. There was a brisk business in software rentals for some time, until the software industry shut it down because they couldn't control it.
The gist was that it violated the EULA, even though if it was done properly (i.e. the renter completely uninstalled the product and returned the entire package to the rental firm) then they would technically be complying with the transfer directives in the older EULAs.
Slashdot Mirror
Sure, there's ethical problems. Look up the horrible little flick called "Parts: the Clonus Horror" http://imdb.com/title/tt0078062/ summarized "Politicians scheme to clone themselves, assuring immortal life". They grow the bodies to optimum physical health then freeze them until the "original" needs a transplanted organ. Of course you've functionally killed a person with a complete personality to do it. Far worse than stem cell research in almost anybody's book.
There was a movie with almost this exact premise, I think it was called "Clonus". They cloned important people, grew their clones to the height of physical health then put them on ice until the original needed a body part, IE a heart, kidney etc. Then they would harvest the organ, for a perfect match and no immunological response. It was kinda bad sci-fi but got into the details of the ethical quagmire.
An adendum - I hit Submit too fast. MS-DNS works properly for full Class C DNS zones with all the tools, but for sub-Class C zones it breaks Dig. NSLookup and Host still work fine. I got into an argument with the AOL folks because I was able to do lookups all day long - using NSLookup. As soon as I tried Dig (which is apparently what AOL uses to do reverse lookups) I realized something was amiss. That's what I meant to say.
Actually, I just went through this with AOL last week. It can be a touch more complicated than checking that checkbox. I have 1/2 a Class C address space - and MS-DNS standard PTRs only work for NSLOOKUP and HOST requests. They do not work for DIG requests! How did I find this out? Even though I had PTRs set up, AOL was still rejecting my mail. If one has less than a Class C then one must create subnetted PTRS, i.e. one must make a subfolder in the reverse DNS zone and put the PTRs there. This apparently must be done manually, the checkbox that creates the PTR for you doesn't do it automagically (unless I've missed something). Once this is done, then Dig will work correctly and AOL will accept your mail.
Some games are for sale.... by the original companies or licensed agents.
MacDowells serving Big Mic's? yaho.com running a search engine? Revoke their business licences, or throw the creeps in jail. This isn't a bad practice of porn sites, this is a bad practice.
And yet the Supreme Court just ruled (I believe 8-1) in favor of Victor's Little Secret, a small "adult novelty" (ie sex toy) store which was sued by Victoria's Secret as diluting their trademark... does this go over the line as far as you're concerned?
Fascinating... I've used a product called Spamnet from Cloudmark, which uses the same methodology but for spam. So, being interested in such an addin I fell for the trick and went to tubgirl site, which I wouldn't recommend for anyone who has a weak stomach. Suffice to say, there is a girl and a tub, and it's disgusting to say the least. Thanks to technos for your outrageous demonstration of not-truly-deceptive site naming.
.xxx or .sex TLD would work fine. I still think that "responsible" pr0n companies could voluntarily use such a TLD and gain some form of respectability or credibility from doing so.
I am a proponent of free speech, and I tend to agree with the overall view that it would be nice if something could be done to control the situation without preventing anyone from excercising their free speech rights. I also agree unfortunately that there is no porposed solution that I've seen that is at all workable.
Of course, if everybody played nice in the sandbox, the concept of a
Well, I for one hate to reinvent the wheel. In my previous incarnation I was a programmer who among other things did extensive customization to accounting software to meet the needs of my customers. I used a product called Accountmate which is written in Visual FoxPro and offers a "source code license" should you want to modify the product. Check this link for their current license agreement: http://www.accountmate.com/solutions/files/liscens e_agree.pdf
I haven't read it (not having dealt with coding for several years) but I think this might provide you a valuable point of reference to create your own terms.
This wouldn't fly, because it didn't in the past. As usual, there really aren't new ideas, just new consumers of the old ones. There was a brisk business in software rentals for some time, until the software industry shut it down because they couldn't control it. The gist was that it violated the EULA, even though if it was done properly (i.e. the renter completely uninstalled the product and returned the entire package to the rental firm) then they would technically be complying with the transfer directives in the older EULAs.