I have a different solution for you which I think is more respectful of the user and will probably result in more feedback for you. In your README file and at the bottom of the documentation include a request for feedback. Something like:

"If you like this software please send me a message at <your email> letting me know you are using it. Your feedback will help me in developing this and other modules in the following ways (list them). Inclusion of the following details would also assist me (list them). To make this easy for you I have included the script tell_me_you_care.sh which emails the following information (list again) to me. Thanks for using xxxx, Juerd."

This way you have let the users know you care about them, the security concerns are minimised, and you have given people who are installing the software on boxes that are not connected to the internet a way of reaching you as well. Personally I think this is a much more polite and respectful way of going about it, give people a reason to opt-in and I believe that they will. I can tell you that I never allow software packages to remote connect (if I get a choice) but I have registered postcard-ware software and sent "fan mail" to authors of software that I like.

--
Do not seek to follow in the footsteps of the wise. Seek what they sought. -Basho

In reply to Re: Gathering module usage statistics by greenFox
in thread Gathering module usage statistics by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.