Well I did (...)

You did indeed. My apologies for not phrasing carefully. I am convinced that opt-in does not work if the user has to do anything to opt-in, where reading documentation is considered doing something.

And it does not give the user any good reason to opt-in.

The only reason I can give is that I can with this information divide my time better. That is of no direct help to the users, but will eventually benefit them.

And it does not cater for boxes behind firewalls etc.

The thing will also only work if LWP is installed. That is not a problem. There is no way to have it all. There is a way to have much more than we have now, and that is what I want. For now, anyway :)

And it breaks standard automated builds.

It does not.

And it raises security concerns for people.

Good. Perhaps people will finally get rid of the false sense of security they apparently have now.

I think you need to stop thinking about what you want

No. What I want is the point. This time, I want something. I think that having put hundreds of hours into my open source work gives me the right to *want* something in return.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

In reply to Re: Re: Re: Re: Gathering module usage statistics by Juerd
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.