Andrew Cooke | Contents | Latest | RSS | Previous | Next


Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

[Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; Collaboration request; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life; [Link, Bike] Cheap Cycling Jerseys; [Link, Music] Music To Steal 2017; [Link, Future] Simulated Brain Drives Robot; [Link, Computing] Learned Index Structures; Solo Air Equalization; Update: Higher Pressures; Psychology; [Bike] Exercise And Fuel; Continental Race King 2.2; Removing Lowers; Mnesiacs; [Maths, Link] Dividing By Zero; [Book, Review] Ray Monk - Ludwig Wittgenstein: The Duty Of Genius; [Link, Bike, Computing] Evolving Lacing Patterns; [Jam] Strawberry and Orange Jam; [Chile, Privacy] Biometric Check During Mail Delivery; [Link, Chile, Spanish] Article on the Chilean Drought; [Bike] Extended Gear Ratios, Shimano XT M8000 (24/36 Chainring); [Link, Politics, USA] The Future Of American Democracy; Mass Hysteria; [Review, Books, Links] Kazuo Ishiguro - Never Let Me Go; [Link, Books] David Mitchell's Favourite Japanese Fiction; [Link, Bike] Rear Suspension Geometry; [Link, Cycling, Art] Strava Artwork; [Link, Computing] Useful gcc flags; [Link] Voynich Manuscript Decoded; [Bike] Notes on Servicing Suspension Forks

© 2006-2017 Andrew Cooke (site) / post authors (content).

Licensing Interpreted Code

From: andrew cooke <andrew@...>

Date: Fri, 4 Oct 2013 21:20:52 -0300

I've been thinking about how best to license software that is:
 - interpreted (so easy to modify)
 - low volume (and so fairly high price)
 - sold to a fairly small / closed community
 - useful (and so a free demo will help it "sell itself")

Given the above, the most obvious conclusion is that technical measures are
unlikely to work (at least, alone).  But since the market is a fairly
close-kint community "social cues" might work well.  So the general approach
would seem to be allow some kind of demo version to be run at no cost, but to
require a licence for "real use".

Consider the kind of person who might use this software.  They are probably
reasonably technical, but not in control of purchasing decisions.  They learn
about the software through word-of-mouth, install it, find it useful, and...
What happens next?

What I would like to happen is that I sell a licence to their employer.  How
do I get there?

There seem to be two routes.  First, they might contact whoever is responsible
for purchasing, or the software might be "noticed" by someone similar.  So I
need to encourage that kind of behaviour - for example, by displaying in the
user interface "Demo Use Only - Please Buy a Licence".

Second, I could make contact with the institutions that are using the
software.  But to do this, I need to know who the users are.  That suggests
some kind of "phone home" feature - perhaps registration or to retrieve

The scenario described doesn't rely on a (technically) restrictive licence.
In fact, it seems like a licence mechanism that limited functionality could do
more harm than good - people would modify the program to enable the
functionality, disabling the cues intended to push them towards purchase.

So what role does the licence play?  Is it just a file that disables the
"Please Pay" message?  That seems like it would be too easy to duplicate.
Trivial duplication could be blocked by having a signed, named user.  The
software would then either display "Licensed to XXX", whch would look bad if
XXX was another institution, or remain at "Please Pay" if the signature was

Of course, signature verification could be disabled by hacking the code.  But
two things mitigate against this.  First, as mentioned above, there's no other
motivation to modify the code (all functionality is available).  And second,
auto-updates (which would justify "phone home") could reset changes.

So we seem to be heading towards a self-consistent approach:
 - a "morally reasonable" message that says "Demo Only" or similar
 - a signed licence that replaces "Demo Only" with "Licensed to XXX"
 - auto-updates (and some kind of tracking of request IPs on the server)

This allows users to install and experiment with the software without any
problems.  It also gives them the social cues and support to request payment
by whoever controls purchasing.

My only real worry about this is that tracking downloads and update IP
requests seems a bit icky.  Is that OK?  Should it be more explicit?  If I
contacted an organisation saying "Hi, you seem to have demoes my software, are
you interested in buying a licence?" would that seem out of place?


PS The above still raises a bunch of technical issues: auto-update; persistent
config outside the auto-update; interface for loading a licence; crypto

Re: Licensing Interpreted Code

From: Michiel Buddingh <michiel@...>

Date: Sat, 05 Oct 2013 10:29:52 +0200

I'd be remiss not to point you at Patrick MacKenzie's blog.  He is a
programmer turned salesman, and his perspective can be refreshing, as
long as you take it in near-homeopathic dosages.

Particularly his advice on pricing may be relevant to your situation:

The users of your software are going to weigh the inconvenience of
working with the demo version against the inconvenience of having to
convince their manager/purchasing department to buy something they don't

So your options are limited to making the first inconvenience larger, or
making the second inconvenience smaller.

Some non-evil ways of doing the first:

     * Licensed version gets packaged updates for
       RedHat/Debian/Ubuntu/OpenSuSE.  Many system administrators I've
       talked to seem to consider this to be important, because it means
       the software will just fit into their existing infrastructure.

     * Offer support by telephone or email

A non-invasive way to get information about who is using your software,
would be to ask people to leave their email address before downloading
the software, or to encourage them to sign up for a mailing list that
sends notifications about software updates.


Comment on this post