Where do I adjust printing parameters for hardcopy printouts?

[Fairlight]

On Wed, Aug 15, 2007 at 05:27:03PM -0400, after drawing runes in goat's
blood, Walter Vaughan cast forth these immortal, mystical words:

> The only thing that I'd like to see is you using some sort of Creative
> Commons license ( http://creativecommons.org/licenses/by/3.0/ ) on your
> website.
>
> Golly, I really am becoming a license storm trooper.
>
> GPLv3 me with a stick... I'm done.

Non-lawyers -read- licenses?  :)

I really never figure it matters too much what license you slap on
something.  A lock only keeps an honest man out, and those that will try
to screw you aren't going to heed a collection of words saying what they
may or may not do.  It's in what they -can- do, within the bounds of their
own ethics combined with reasonably not getting caught--a fact the RIAA,
MPAA, and SPA refuse to acknowledge as reality because they all wear trendy
dollar-bill blinders.  Anyone that can't see the facts on how it plays out
in reality is deluding themselves and setting up their business model to
fail or fall behind technological advances...as per many companies
represented by the aforementioned groups.

How many people -actually- agree with >60% of sneakware licenses they
purport to agree with when installing/using software?  Tried returning
software in the lasr decade?  It's use it or you just wasted money, even if
you don't agree with what you couldn't see up-front prior to purchase.

The reality is that unless you deal in volume enough to be able to absorb
and sustain the cost of launching legal action for breach until you can
recover it (-if- you can recover it), it's 99% a matter of idealogy which
license you choose to place on your work.  So long as I'm getting roughly
properly compensated for my commercial work, I usually don't care under
what anything else is placed so long as I can hold non-exclusive rights to
my own material for reuse.  Getting burned occasionally is a cost of doing
business in this industry--and a license itself will not stop egregious
abuse unless backed by big money and lawyers.

Getting all jazzed about which license is used before there's substantive
material -to- license is like trying to write a good novel based on a
title.  It's putting the cart -way- before the horse, IMHO.

I'm not saying you shouldn't plan, I'm saying get priorities straight while
planning.  Some don't live and die by EULAs, even when they dev/pub.  I'd
be much more worried about usability in a functional sense than a licensing
sense.  If it's unusable or vaporware, what is the point in -having-
license to use the unusable?

mark->
-- 
The latest synth mixdown...
http://media.fairlite.com/Isolation_Voiceless_Cry_Mix.mp3