In some respects, and I believe we are thinking of the same things, yes, I agree. However with regards the more 'pedestrian' issues facing internet users in terms of tracking and advertisements, we're way ahead of the game by virtue of being somewhat 'stuck in the past', in addition to this, not being beholden to people expecting the site to pay for itself in what is now considered the normal fashion. As a direct consequence I've been a loyal Pair customer for 1 year shy of my registration here (after first logging in I didn't come back for about a year). When registering I specifically mentioned I'd become a customer due to their support of perlmonks. The Troy Hunt article is interesting, compare the bandwidth used browsing the tabloid news page, using some DNS level blocking (thanks to pi hole) vs normal browsing:
"....I snapped the one without Pi-hole at 17.4 mins after I got sick of waiting. 2,663 requests (one of which was to Report URI, thank you very much!) and 57.6MB. To read the freakin' news. (Incidentally, in this image more than the others you can clearly see requests to domains such as fff.dailymail.co.uk failing as the Pi-hole prevents them from resolving.)"
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
