Stan said:
Paul,
I am so sorry to have upset you.
I've deleted my macro-altered, JAR intact version of your program.
No offense was intended, I assure you. I believe that will become clear
to you over the course of this message.
In you message, you wrote that had I really wanted to contact you, I
would have posted to you website message board. To tell you the truth,
I've looked through you site for ways of contacting you and only found
the link to your bug report link. Perhaps that message board link was
always there for me to see. But the truth is that I never saw it (and
still can't see it).
It's on the primary, tier-one menu list on the Home Page. It's labeled
"Messages". It also is easily accessed with:
http:/
www.arachnoid.com/messages, and it is an address that is linked on
about 1/5 of all the pages at arachnoid.com.
You then suggested that I posted my message to a Usenet group that you
rarely read and did so for the purposes of receiving a non-reply and
taking that for permission. In fact, that's not what I intended.
Be that as it may, you need to remember that your intentions may not be
reflected in how your actions are perceived (the law of unintended
consequences). Always ask yourself how your decisions will look to others.
Next, I didn't really drop your copyright notice from my non-hacked
version of Arachnophila as you suggested I did.
Actually, as far as the average user is concerned, a user who never reads
help pages, the copyright notice is gone from your version. This sends a
clear signal. It's a signal that was reinforced in the content of your
deleted Web page -- that this is a "rewritten" Arachnophilia.
Yes, I did remove your
About button from the main toolbar, but I didn't remove your About
button from the Help menu or your copyright notice from your linked Help
file.
You need to realize that this just doesn't fly. Under copyright law, you
can't remove *any* copyright notices. The law on this issue can't be
interpreted to mean it's all right to remove all but one notice.
Yes, I posted and offered my macro-altered (something you encourage)
version of Arachnophilia to my website,
This is not correct. and I'll have to further clarify my instructions on
this point. A "macro-altered" version is the norm for end users, but should
not be distributed that way. For distribution, one must create separate
macros that do not overwrite the existing, standard macros.
but I did so in hopes that you
would download the macros and be impressed that I had devoted so much
time to working with your program. Since you're not impressed with my
work ...
No, that's a bit unfair. I never even looked at your work. I have been
focusing only on the legal issues here. Arachnophilia is so popular, so
widely distributed now, that I have to address any violation of the rules
to prevent a potentially serious "slippery-slope" effect.
I've been in the software business for three decades, and I think I may have
seen everything. I've seen any number of my programs stolen in various
ingenious ways, sometimes by lawyers, sometimes simply because I wasn't
careful enough.
Example. I get regular phone calls from companies who want to buy
Arachnophilia, and I just hang up on them. Some of the less intellectually
gifted end users think that, because Arachnophilia has no price, it must
have no value. But companies don't think that -- all they know is
Arachnophilia is (typically) better than the program they are trying to get
people to pay for. So they try to buy it, just to get it out of the way.
And if I was less experienced or less wealthy, I might listen to them for
thirty seconds. Speaking hypothetically.
My point is that I have to defend Arachnophilia just as though it were being
offered for sale, because it is (as valuable as/more valuable than) a bunch
of programs that are being offered for sale.
As for your statement that I should have asked for your permission
before starting my work on Arachnophilia's macro-structure (and
templates ... which you say one can do in your Tips of the Day file),
Yes, as an end user for personal use, not for distribution. I'll have to
make this distinction more clear in the next release. Released macro sets
should be kept separate from the standard ones.
< snip >