AW: serial numbers on standalones

[Richmond]

On 26/03/13 12:30, Tiemo Hollmann TB wrote:
> I know, that it is very unpopular to supply very strict and controlled
> licence models and rely on all the nice and lovely pirates to come back to
> me, but I can't confirm at all these models in my daily business.
> Perhaps it is related to my client base, I don't know. But I made the
> experience with two different licensing models in the last 15 years in the
> same target audience (partly even with the same customers) with our
> products. One product licence was very open and was based on "fairness and
> following our licence model" with very low piracy protection, the other
> product license is tied very strict to the hardware (wich actually has some
> painful sides, but for us it's the better choice).
> After having sold one or any number of licences of product 1to a dedicated
> target group, we never have sold a second licence in that group (e.g. all
> teachers of a school). After having sold licences of product 2 we are
> constantly selling additional licences within the same target group. And no,
> it doesn't depend on the product, I know that they all are using product 1
> too. As I said, perhaps this is a special behavior of our target group
> (teachers). In the last decades I never have met people who are less aware
> of law, piracy and licensing as teachers (sorry Richmond)

Don't be sorry; I know that is a fact.

Trying to explain to a parent of twins why she should pay for 2 copies 
of a student workbook, rather than just
one followed by a quick trip to the photocopy shop is an uphill, and 
unproductive exercise, that only serves
to convince people I am some sort of nutcase round these parts.

Mind you, here in Bulgaria about 95% of the population are either 100% 
unaware
of law, piracy and licensing, or, even if they are, couldn't care less.

I am becoming increasingly in favour of hardware tethering of software 
after trying to explain
what a site licence is and ending up with zero comprehension as the 
interlocutor cannot see why
they shouldn't just duplicate the individually licensed executable 
across as many machines as they require.

The only problem (as was pointed out on this list) is that many machines 
keep changing their Mac address
and I am unaware of any other, more permanent, hardware feature Livecode 
can grab hold of.

Richmond.

>
> Just my 2 cents
> Tiemo
>
>> -----Ursprüngliche Nachricht-----
>> Von: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] Im
> Auftrag
>> von Timothy Miller
>> Gesendet: Samstag, 16. März 2013 21:31
>> An: How to use LiveCode
>> Betreff: Re: serial numbers on standalones
>>
>> On Mar 16, 2013, at 12:00 PM, kee nethery <kee at kagi.com> wrote:
>>
>>> The people who make a lot of money selling software are those that focus
>> on how to get more people to use their software, not those who focus on
> how
>> to get less people to use their software.
>>> The "get more people" group occasionally will "crack" their software and
>> upload that crack to a crack site so that people can steal their software.
>> Having a crack shows that someone cared enough about the software to spend
>> time to crack it because of the street cred that would give them. No one
>> cracks lame software thus … this software must not be lame. In addition,
> no
>> one wants to be the second person to crack some software so other cracks
>> don't appear.
>>> Secondly, most people that pirate software don't really use it. And if
>> they do, you've just had someone experience your software and figure out
>> what it is good for. People like me who pay for software, ask for
>> recommendations, and I'm fairly certain that many of the recommendations
>> come from people who have pirated software. Pirates can be your
> advertising
>> channel.
>>> Finally, the crack if the pirate is still using the cracked software
>> after 6 months, they can be converted into a buyer. It has some weird bug
>> that pops up. The solution to that specific bug is to buy the upgrade. If
>> someone running a cracked version gets that error message, they are using
>> it for real and they will frequently pay for the upgrade.
>>> Kee Nethery
>> Wow! You really nailed it. I've read similar commentaries, but yours is
>> clear and concise.
>>
>> I'm working on a book, thinking about self-publishing, selling to the
>> public from a website, while taking care to maintain control of the
>> copyright, maybe going with a  commercial publisher later, if it's
>> successful. I've feared piracy, heard both sides of the debate.
>>
>> You've convinced me (unless someone later on this thread changes my mind).
>>
>> With software, it seems, one way to limit piracy damage is to upgrade
>> routinely. With literature, it might help to release periodic revisions,
> or
>> regularly add new material.
>>
>> Cheers,
>>
>>
>> Tim Miller
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode